Skyfire

Agents pay for and call outside services. The Skyfire Directory lists approved seller services (MCP servers, APIs, webpages and Fetch.ai agents) with their endpoints, prices and identity requirements.

An agent finds them through the MCP server's find-sellers tool, creates a token and calls the service with it, and the live implementations run Dappier, BuildShip and Apify this way. Card backed tokens run on Visa and Mastercard, wallets fund in USDC on Base, and guides add token enforcement at the edge on Cloudflare and AWS. The homepage logo wall names partners without documenting integrations.

SourceSkyfire, docs.skyfire.xyz (Service Discovery, Using the Skyfire MCP Server, Live Implementations, Building an Agentic Checkout, the KYA access control guide)read 2026-09-25

No workflow model. Skyfire issues tokens and settles charges for work agents do elsewhere. The charge lifecycle (create, verify, deliver, charge, settle, with partial and repeated charges and a 24 hour grace period) is a payment lifecycle, not multi step agent execution. The MCP server page says it orchestrates agent commerce workflows, but its example shows the customer's own agent chaining Skyfire and Dappier tools.

SourceSkyfire, docs.skyfire.xyz (Payments and Settlement, Using the Skyfire MCP Server)read 2026-09-25

No retrieval over the customer's content. Skyfire stores verified identity fields, agent accounts and wallet balances, and its Directory lists seller services, but none of it is a corpus an agent queries for answers.

SourceSkyfire, docs.skyfire.xyz (Platform Structure, Service Discovery)read 2026-09-25

A per purchase approval that Skyfire hosts. In the purchase authorization flow, which the Payments React SDK renders in an iframe inside the agent platform's app, the cardholder selects an enrolled card and authorizes the exact amount with a passkey, and nothing proceeds until they do. The resulting pay or kya-pay token caps what the merchant can charge. Around that approval, the card management flow locks or removes a card, sellers set identity requirements and a maximum token lifetime, and token creation fails when a buyer is not verified to the level a service requires.

SourceSkyfire, docs.skyfire.xyz (Building an Agentic Checkout, Agentic Commerce with Payment Cards, Know Your Agent)read 2026-09-25

Both access controls and compliance are documented. Organizations get ADMIN and MEMBER roles, and an Organization Admin key creates, activates and deactivates users (MEMBER and agent keys are refused on those endpoints).

Every buyer and seller agent holds its own API keys, which the dashboard creates, rotates and deactivates, and agents can register the source IP ranges their tokens carry. For compliance, the Organization Guide states Skyfire is a PCI DSS Level 2 service provider, with personal data encrypted in transit and at rest and decrypted only inside a trusted execution environment. No attestation report is published, and trust.skyfire.xyz does not resolve.

SourceSkyfire, docs.skyfire.xyz (Organization Guide, API Authentication, Create Organization User, Buyer Guide, Seller Guide)read 2026-09-25

A charge record, not a run trace. The dashboard lists every token a buyer agent created and every charge against them (amounts, timestamps, seller service IDs), and sellers see each deposit with the buyer agent ID. Get Token Charges returns charges with settlement time and network, and every kya token carries the human, agent and platform identity plus the IP it was created from. That answers who paid whom and when, one charge at a time. Nothing ties an agent's steps into a run, and no cross protocol ledger, activity stream or webhook is documented.

SourceSkyfire, docs.skyfire.xyz (Buyer Guide, Seller Guide, Get Token Charges, KYA Token)read 2026-09-25

No agent memory. A user's verified identity, which its agents inherit, and each wallet's balance persist, but that is account and ledger state the platform applies, not context an agent reads to decide. A kya token lets a seller create an account for the agent, and the agent then stores the seller's credentials itself.

SourceSkyfire, docs.skyfire.xyz (Platform Structure, Know Your Agent, Token Interaction Flows)read 2026-09-25

A cloud service with no deployment options. Skyfire runs Production and Sandbox environments, each with its own dashboard, API base URL and token issuer, but separate environments are not a deployment choice, and no region, residency choice or customer environment is documented. Stablecoin settlement is a payment choice, not a deployment option.

SourceSkyfire, docs.skyfire.xyz (Environments)read 2026-09-25

No prebuilt agents. The reference implementations (a Next.js chat UI with a shopping agent, a headless browser checkout agent, a news crawler) are starting points in repositories the customer runs, the checkout ones private and available on request. The Directory lists other vendors' services.

SourceSkyfire, docs.skyfire.xyz (Building an Agentic Checkout, Reference Implementations, Service Discovery)read 2026-09-25

Caller invoked. A token is created when a buyer agent calls Create Token or the MCP server, and a charge happens when the seller calls Charge Token. No schedule, webhook or event starts agent work. In the buy later model a purchase waits for a condition the cardholder set, such as a price drop, but the agent platform does the waiting, not Skyfire.

SourceSkyfire, docs.skyfire.xyz (Token Interaction Flows, Agentic Commerce with Payment Cards)read 2026-09-25

No model choice. Skyfire runs no models; it issues identity and payment tokens for requests agents make elsewhere. The product page lists paying for LLMs among things an agent can buy, but a model bought from a seller is the seller's model, not a choice Skyfire routes.

SourceSkyfire, docs.skyfire.xyz (Introduction) and skyfire.xyz (product)read 2026-09-25

A documented public API for Skyfire's own platform. REST endpoints with OpenAPI definitions create, introspect and charge tokens, manage seller services, read wallet balances and manage organization users, authenticated by the skyfire-api-key header, with Production and Sandbox base URLs. The Skyfire MCP server has a published endpoint, the same auth header and enumerated tools (find-sellers, create-kya-token, create-pay-token, create-kya-payment-token) that create the platform's core objects. Its npm SDKs cover the Credits Wallet embed and the Payments React SDK.

SourceSkyfire, docs.skyfire.xyz (Create Token, API Authentication, Using the Skyfire MCP Server, Credits Wallet Embed SDK)read 2026-09-25

No evaluation surface. The Sandbox environment and the dashboard Playground let a developer try token creation and charging without moving real funds, which tests the customer's integration, not agent behavior. Skyfire reviews each seller service before approval to confirm it works, which checks the service, not an agent.

SourceSkyfire, docs.skyfire.xyz (Environments, Buyer Guide, How Seller Services Work)read 2026-09-25

Skyfire does not drive a browser. Its tokens ride on requests the agent makes, and sites or bot managers read them at the edge. The homepage's Buy for Me card has no documentation, and the headless browser search and checkout agent in the checkout starting points is a private reference implementation the customer adopts and runs, so the customer's agent navigates.

SourceSkyfire, skyfire.xyz (home) and docs.skyfire.xyz (Building an Agentic Checkout)read 2026-09-25