Skyfire for AI agents
Agents read Skyfire at once. Changes and sends are held for a person's approval by default.
About Skyfire
Skyfire enables AI agents to autonomously transact and pay for services, creating a seamless payment infrastructure for AI applications.
What an agent can do in Skyfire
Every Skyfire action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Skyfire without asking first. 11 actions.
- Get Skyfire Buyer Wallet BalanceRetrieve buyer wallet balance. Chain before token creation to prevent declines.
- List Skyfire Directory ServicesBrowse Skyfire's service directory to obtain `sellerServiceId` for token creation. Chain this with CreatePayToken or CreateKyaPayToken.
- Get All Service TagsFetch all service tags to discover filtering options. Chain with ListDirectoryServices using tags parameter to find specific types of services (e.g., 'ai', 'mcp', 'scraping').
- Get Directory Service By IDTool to get full details for a specific service in the Skyfire directory by its ID. Use when you need complete information about a service including pricing, requirements, and seller details.
- Get Skyfire Service DetailsGet full details for one service. More detailed than ListDirectoryServices - shows terms of service, API specs, and integration URLs. Use before creating expensive tokens.
- Get Services by AgentBrowse all services from one seller agent. Useful when you trust a seller and want to see their full catalog, or when tracking down who provides a specific type of service.
- Get Services by TagsFilter services by tags to find exactly what you need. More efficient than browsing all services when you know the category. Chain: GetAllServiceTags → GetServicesByTags → CreatePayToken.
- Get Skyfire Token ChargesAudit charges for a specific token. Shows exactly what sellers charged against your token and when. Use for reconciliation: "I authorized $5 max, what did they actually charge?"
- Introspect Skyfire TokenCheck if a token is still valid before calling a seller service. Prevents wasted API calls with expired tokens. Use after creating tokens if there's a delay before calling the seller, or when debuggin
- List Agent Seller ServicesList all services registered by the authenticated seller agent. Use when you need to view or manage your own services as a seller.
- List Skyfire Buyer TokensInspect buyer tokens for observability. Chain with transactions to audit usage.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 5 actions.
- Create Skyfire KYA+PAY TokenIssue a Skyfire KYA+PAY token (POST /api/v1/tokens with type=kya+pay).
- Create Skyfire PAY TokenIssue a Skyfire PAY token (POST /api/v1/tokens with type=pay).
- Charge Skyfire TokenCharge a buyer's token (seller-side operation). REQUIRES SELLER API KEY: This action requires your seller agent API key, not the buyer's key. The buyer creates and sends you a pay/kya+pay token JWT, y
- Create Skyfire KYA TokenIssue a Skyfire KYA token (POST /api/v1/tokens with type=kya).
- Set Agent Source IP AddressesRegister IP addresses as sources for Agent requests (PUT /api/v1/agents/source-ips). Use before creating tokens to whitelist agent IPs.
Changes wait in Needs you
Changes and sends in Skyfire are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Skyfire questions
Can an agent change data in Skyfire on its own?
Not by default. Changes and sends in Skyfire are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Skyfire?
This connector lists 11 read actions. Reads run at once, without waiting for approval.
How does Skyfire connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.