Skyfire
Skyfire enables AI agents to autonomously transact and pay for services, creating a seamless payment infrastructure for AI applications.
Verdict
Common use cases
- Pay external APIs per request without invoices
- Charge clients for AI services your team delivers
- Check wallet balance before expensive operations
- Discover paid services by tag or seller
- Issue time-limited payment tokens for contractors
Integration
- Vendor
- Skyfire
- Category
- other
- Auth
- API_KEY
- Tools
- 13
- Composio slug
skyfire
Tools
- Charge Skyfire Token
Charge a buyer's token (seller-side operation). use when you've delivered a service and want to collect payment. the buyer created a token with max amount, you charge actual amount used.
- Create Skyfire KYA+PAY Token
Issue a skyfire kya+pay token (post /api/v1/tokens with type=kya+pay).
- Create Skyfire KYA Token
Issue a skyfire kya token (post /api/v1/tokens with type=kya).
- Create Skyfire PAY Token
Issue a skyfire pay token (post /api/v1/tokens with type=pay).
- Get All Skyfire Service Tags
Fetch 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 Skyfire Buyer Wallet Balance
Retrieve buyer wallet balance. chain before token creation to prevent declines.
- Get Skyfire Service Details
Get full details for one service. more detailed than listdirectoryservices - shows terms of service, api specs, and integration urls. use before creating expensive tokens.
- Get Skyfire Services by Agent
Browse 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 Skyfire Services by Tags
Filter 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 Charges
Audit 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 Token
Check 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 debugging payment issues.
- List Skyfire Buyer Tokens
Inspect buyer tokens for observability. chain with transactions to audit usage.
- List Skyfire Directory Services
Browse skyfire's service directory to obtain `sellerserviceid` for token creation. chain this with createpaytoken or createkyapaytoken.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations → Add MCP Server and select Skyfire. 2. You'll be prompted for an API key — generate one from your Skyfire dashboard under API Access. 3. Paste the key into Switchy and click Connect. 4. Switchy will verify the key and list available tools (token creation, charging, balance checks, service directory). 5. To test, open any Space and type '@Skyfire check my buyer wallet balance' — if the MCP returns a balance, the connection works. 6. Before creating tokens, confirm your Skyfire wallet is funded (you'll see a balance in USD or the configured currency). 7. To invoke a tool, @mention @Skyfire in a message and describe the task ('create a PAY token for $5', 'charge token abc123 for $2.50', 'list AI services tagged scraping').
What teammates see: by default, memories from Skyfire are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Wallet Balance
@Skyfire check my buyer wallet balance and tell me if I have enough to create a $10 token.Open in a Space →
Create Payment Token
@Skyfire create a PAY token for $25 with a 7-day expiration. I'm giving this to a freelancer for data scraping.Open in a Space →
Charge Delivered Service
@Skyfire charge token xyz789 for $3.50. I just delivered a summarization job and the buyer pre-authorized up to $5.Open in a Space →
Browse AI Services
@Skyfire list all services tagged 'mcp' and 'ai'. I want to see what paid integrations are available for our workspace.Open in a Space →
Inspect Service Details
@Skyfire get details for service ID svc_abc123. I need to review the terms of service and integration URL before we buy.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@skyfire check my wallet balance and show me all AI services under $5 per call
Your Skyfire buyer wallet holds $247.83 USDC. I found 12 AI services tagged 'ai' with per-call costs under $5: three GPT-4 wrappers ($0.02–$1.50/call), four image-generation endpoints ($0.80–$3.20/call), two sentiment-analysis APIs ($0.10–$0.45/call), and three summarization services ($0.25–$2.00/call). The lowest-cost option is 'FastSummary' at $0.25/call from agent 'TextLabs'. Would you like full details on any of these before I create a payment token?
This example chains wallet-balance retrieval with service discovery by tag and price filter. Skyfire's directory returns pricing metadata, but actual costs depend on the seller's current terms. Always check wallet balance before issuing tokens to avoid declined transactions.
@skyfire create a KYA+PAY token for the 'DataScraper Pro' service, max $50, and get the integration URL
I've issued a KYA+PAY token (ID: tok_kya_pay_8x7f2a) for 'DataScraper Pro' with a $50.00 spending cap. This token bundles Know-Your-Agent verification with payment authorization, so the seller can confirm your identity and charge per scrape. Integration URL: https://api.skyfire.xyz/services/datascraper-pro/v2. The token expires in 30 days or when the cap is reached. You'll need to pass this token in the Authorization header when calling the service.
KYA+PAY tokens combine identity attestation and payment in one credential. This example shows the seller-side workflow: you create the token, the seller charges it as they deliver the service. Skyfire enforces the spending cap on-chain, so overcharges are impossible. Requires your Skyfire account to hold sufficient USDC.
@skyfire I just delivered 3 API calls to buyer token tok_pay_9m4n1b—charge $4.50 and summarize the transaction
Charged $4.50 to buyer token tok_pay_9m4n1b (transaction ID: txn_5k8p2r). The buyer's token had a $20.00 cap; $15.50 remains available. This charge covers 3 API calls at your published rate of $1.50/call. Settlement to your seller wallet will complete within 2 minutes. The buyer will see 'API Usage – 3 calls' in their Skyfire transaction log. No further action needed unless the buyer disputes the charge within 7 days.
This is the seller-side charge operation: you've already done the work, now you collect payment by posting the actual amount to the buyer's pre-authorized token. Skyfire's on-chain escrow ensures the buyer can't revoke payment after service delivery, but you must charge within the token's validity window (typically 30 days).
Use-case deep-dives
When Skyfire handles pay-per-use agent transactions
A 3-person dev shop builds custom AI agents for clients and wants to monetize API access without running Stripe infrastructure. Skyfire wins here if you're selling to other agents or developers who already hold crypto wallets—the KYA+PAY token flow lets buyers pre-authorize a spend cap, you deliver the service (a batch of embeddings, a scraping job), then charge the actual amount used. The wallet balance check prevents declines before you spin up compute. This breaks down if your buyers are non-technical end users who don't want to manage wallets, or if you need fiat invoicing for enterprise procurement. If 80% of your revenue comes from other AI tooling companies, Skyfire's agent-to-agent rails are faster than building your own payment stack.
Skyfire's directory for finding paywalled AI tools
A solo founder prototyping a research assistant needs to chain together scraping, OCR, and summarization without pre-negotiating contracts with each vendor. Skyfire's service directory and tagging system let you browse 'ai' or 'mcp' tagged services, check terms and pricing upfront, then issue a PAY token scoped to one transaction. This works when you're experimenting with 5-10 different APIs in a week and want one wallet to rule them all. It's overkill if you're only using OpenAI and Anthropic (just use their native billing), or if you need SLAs and support contracts (Skyfire's marketplace is optimized for permissionless access, not enterprise guarantees). Best fit: rapid prototyping across fragmented paywalled APIs where you value discovery speed over vendor relationships.
When you're the API vendor collecting from agents
A 2-person team runs a specialized web scraping API and wants to let AI agents pay per request without human invoicing. You issue KYA tokens so buyers prove wallet ownership, they create PAY tokens with a $50 cap, you charge $0.03 per scrape as jobs complete. The 'Charge Skyfire Token' tool automates the debit—no monthly reconciliation, no failed credit cards. This assumes your customers are developers or agents comfortable with crypto rails; if you're selling to marketing teams or enterprises that need POs and ACH, Skyfire's friction is higher than a Stripe checkout. The threshold: if you're doing under 100 transactions a month, manual invoicing is simpler. Above that, and your buyers already use wallets, Skyfire's automation pays for itself in saved accounting hours.
Frequently asked
What does the Skyfire MCP do in Switchy?
It lets your AI agents handle payments for API services without human approval loops. Your agent can check wallet balances, create payment tokens (KYA, PAY, or KYA+PAY), charge tokens after delivering a service, and browse Skyfire's service directory to find providers. Think of it as giving your agent a corporate card with programmable spending rules.
Do I need a Skyfire account to use this MCP?
Yes. You need a Skyfire API key, which means you must register as either a buyer (to pay for services) or a seller (to collect payment). The MCP authenticates via API_KEY, so whoever connects it in Switchy needs access to your organisation's Skyfire credentials. No OAuth dance — just paste the key.
Can the MCP automatically pay for third-party APIs my agent calls?
Only if those APIs are listed in Skyfire's service directory and accept Skyfire tokens. The MCP can create tokens with spending caps and charge them post-delivery, but it won't magically integrate with arbitrary payment processors. If the service you want isn't in Skyfire's directory, this won't help.
How is this different from just calling Skyfire's API directly?
The MCP wraps Skyfire's REST API so your agent can invoke payment operations via natural language instead of writing HTTP requests. You get the same functionality — token creation, charging, directory browsing — but the agent decides when to call it based on context. If you're already scripting Skyfire calls in code, you don't need this.
Who on my team should connect the Skyfire MCP?
Whoever manages your Skyfire wallet and is comfortable with agents spending money. This isn't a read-only integration — agents can create tokens and charge payments. If your team uses Skyfire for agent-to-agent commerce, the person who holds the API key (likely finance or ops) should own the connection in Switchy.