ceven

Skyfire

Empowers your AI agents to autonomously discover services, issue payment tokens, and settle transactions without human intervention.

Try Skyfire in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Skyfire integration

    • Describe the outcome and Ceven picks the right Skyfire calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Skyfire data, across all 16 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Skyfire access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Skyfire, when, and on whose behalf.
    • The agent pauses and asks when Skyfire is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Skyfire.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Skyfire action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Skyfire, and when to use it.

Charge Skyfire Token
Use this when you have delivered a service and want to collect payment from a buyer token.
Create KYA PAY Token
Issue a combined KYA and PAY token to authorize both identity verification and payment.
Create KYA Token
Issue a KYA token specifically for identity and know your agent verification purposes.
Create PAY Token
Issue a payment token with a maximum amount to pay for a specific AI service.
Get Service Tags
Pull all available service tags to filter the directory for specific categories like scraping or LLMs.
Get Buyer Wallet Balance
Retrieve the current balance of the buyer wallet to ensure funds exist before creating tokens.
Get Service Details
Pull the full API specs, terms of service, and integration urls for a single service provider.
Get Services by Agent
List all services offered by a specific seller agent to explore their full catalog.
Get Services by Tags
Filter the service directory by tags to find providers that match specific technical needs.
Get Token Charges
Audit all charges against a specific token to see exactly how much a seller spent.
Introspect Token
Check the current validity and status of a token to prevent failed API calls to sellers.
List Buyer Tokens
Pull a list of all buyer tokens for observability and usage auditing.
List Directory Services
Browse the global directory to find the seller service ID needed for token creation.
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.

25 actions · scroll to see them all

Frequently asked questions

Skyfire uses a scoped token model where the buyer defines a maximum allowable charge at the moment of creation. When a Ceven agent creates a pay token, it sets a hard ceiling on the amount the seller can claim. The seller can only charge the actual amount used, which must be equal to or less than the maximum. If a seller attempts to charge more than the token limit, the transaction is rejected by the Skyfire network. This allows you to deploy agents with the confidence that they cannot accidentally drain your entire wallet balance on a single runaway process or an overpriced API call.
KYA tokens focus on Know Your Agent requirements, providing a layer of identity and verification so sellers know who is accessing their service. PAY tokens are purely for financial settlement and transferring value. In many professional workflows, a KYA PAY token is used because it combines both identity and payment into a single credential. This streamlined approach ensures the seller has both the funds to cover the service and the necessary identity data to comply with their own internal risk and compliance policies before the agent begins the actual work.
Yes. You can control spending by utilizing the directory search and tag system. Instead of giving an agent a blank check, you can build a Ceven workflow that first calls the get services by tags action to find approved vendors. The agent is then instructed to only create pay tokens for service IDs that appear in that filtered list. By combining this with strict wallet balance monitoring, you create a governed environment where agents can only transact with verified providers that meet your specific technical or budgetary criteria.
When you act as a seller, you receive a token from the buyer. Once your agent delivers the requested service, you use the charge skyfire token action to request the actual cost. You provide the token ID and the specific amount to be transferred. Skyfire handles the movement of funds from the buyer wallet to the seller wallet. Because this happens via API, your agent can trigger the charge the millisecond the data is delivered, ensuring you are paid in real time without needing to send manual invoices or wait for monthly billing cycles.
Yes. Skyfire imposes specific rate limits on token creation and directory queries to prevent network abuse. If your agent attempts to create hundreds of tokens in a few seconds, you will encounter a 429 too many requests error. To handle this, Ceven recommends implementing a slight delay between token requests or batching your service needs. This limit is particularly relevant when scaling large agent swarms that all need unique tokens simultaneously. Monitoring your response codes allows the agent to back off and retry without crashing the entire workflow.
Auditing is handled through a combination of the list buyer tokens and get token charges actions. You can create a daily reporting workflow in Ceven that lists every token created in the last twenty four hours and then iterates through those tokens to pull the exact charge history. This provides a granular view of which agents are using which services and exactly how much is being spent per task. This data can be pushed into a spreadsheet or a database for a full financial audit of your AI agent economy.
Tokens have a defined validity period to ensure security. If a token expires, any attempt by the seller to charge it will fail. This is why the introspect skyfire token action is critical. Before an agent makes a long running call to a seller, it should check if the token is still valid. If the token has expired, the agent can simply create a new one using the same parameters. This ensures that the payment channel remains open for the duration of the service delivery without requiring manual human intervention to refresh credentials.
While Skyfire is built for agent to agent commerce between different entities, you can use it for internal accounting. By setting up separate wallets or tracking tokens by agent ID, you can treat different parts of your AI organization as separate cost centers. One agent can pay another agent for a specialized task, and you can use the transaction logs to calculate the internal cost of a complex workflow. This provides a high level of transparency into which parts of your agentic system are the most expensive to operate.

Alternatives to Skyfire

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Coinbase logoCoinbasePayPal logoPayPalStripe logoStripe

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Skyfire and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free