Skyfire enables AI agents to autonomously transact and pay for services, creating a seamless payment infrastructure for AI applications.
Skyfire enables AI agents to autonomously transact and pay for services, creating a seamless payment infrastructure for AI applications. On Nagent, Skyfire is exposed as a fully-configurable ai agents integration that any agent can call — 16 actions, and API key authentication. No code is required to wire Skyfire into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Skyfire to automate the kinds of tasks ai agents teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Skyfire into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Skyfire, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SKYFIRE_CHARGE_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, you provide the service, then call this endpoint to collect payment. Flow: Buyer creates token → Buyer calls your service with token → You validate token → You provide service → You call this to charge. Common errors: - 401: Invalid/expired token OR wrong API key (must use seller key) - 402: Charge amount exceeds token value
Input parameters
The JWT token string the buyer sent you (not the tokenId)
Amount to charge (must be <= token's max amount)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_CREATE_KYA_PAY_TOKENIssue a Skyfire KYA+PAY token (POST /api/v1/tokens with type=kya+pay).
Input parameters
Optional tag for buyer-side tracking
Unix timestamp (seconds) when token expires
Maximum amount the seller may charge (as decimal string)
UUID of the seller service to call
Optional list of identity permission scopes required by seller (e.g., \['email', 'name'\])
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_CREATE_KYA_TOKENIssue a Skyfire KYA token (POST /api/v1/tokens with type=kya).
Input parameters
Optional tag for buyer-side tracking
Unix timestamp (seconds) when token expires
UUID of the seller service to call
Optional list of identity permission scopes if required by seller (e.g., \['email', 'name'\]). Check service's buyerIdentityRequirement to see what permissions may be needed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_CREATE_PAY_TOKENIssue a Skyfire PAY token (POST /api/v1/tokens with type=pay).
Input parameters
Your internal reference for tracking - appears in transaction history. Use for matching tokens to your workflows
Unix timestamp when this token becomes invalid. Set short (5-10 min) for one-time use, longer for recurring calls. Max 24 hours
Maximum USD the seller can charge. Use decimal string to avoid float precision issues. The seller decides actual charge up to this limit
The service ID you got from ListDirectoryServices - this binds the payment to a specific seller service
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_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').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_GET_BUYER_WALLET_BALANCERetrieve buyer wallet balance. Chain before token creation to prevent declines.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_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.
Input parameters
ID of the service to retrieve. Must be a valid UUID format.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_GET_SERVICEGet full details for one service. More detailed than ListDirectoryServices - shows terms of service, API specs, and integration URLs. Use before creating expensive tokens.
Input parameters
Seller service ID (get from ListDirectoryServices)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_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.
Input parameters
Max services to return
Seller agent ID (get this from service listings or previous transactions)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_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.
Input parameters
Max services to return
Comma-separated tags to filter services. Use GetAllServiceTags to discover available tags.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_GET_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?"
Input parameters
Token ID to check charges for (get from ListBuyerTokens)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_INTROSPECT_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 debugging payment issues.
Input parameters
The JWT token string to validate (get this from CreatePayToken/CreateKyaToken/CreateKyaPayToken)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_LIST_BUYER_TOKENSInspect buyer tokens for observability. Chain with transactions to audit usage.
Input parameters
Number of tokens per page (1-100, default: 20)
Pagination cursor from previous response's next_cursor field
Filter by token status: VALUE_RESERVED (active payment tokens), INFORMATIONAL (identity-only tokens), CONSUMED, EXPIRED
ISO 8601 timestamp for earliest tokens to return (default: 7 days ago). Example: 2026-01-20T00:00:00Z
ISO 8601 timestamp for latest tokens to return (default: now). Example: 2026-01-27T23:59:59Z
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_LIST_DIRECTORY_SERVICESBrowse Skyfire's service directory to obtain `sellerServiceId` for token creation. Chain this with CreatePayToken or CreateKyaPayToken.
Input parameters
Filter by service tags like 'ai,llm' or 'productivity'. Comma-separated, no spaces
How many services to fetch per page. Start with 20, increase if you need to browse more
Search for services by name or description. Try 'chat', 'image', 'analysis' etc
Got more results? Pass the next_cursor from previous response to get the next page
Browse by category like 'AI', 'Data', 'Communication'. Check directory for available categories
Only show services costing at least this much per call. Useful to find premium services
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SKYFIRE_SET_AGENT_SOURCE_IPSRegister IP addresses as sources for Agent requests (PUT /api/v1/agents/source-ips). Use before creating tokens to whitelist agent IPs.
Input parameters
List of IP addresses to register as agent sources (e.g., \['192.168.1.1', '10.0.0.1'\]). These will be included in tokens created for the agent.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 55 agents privately built on Nagent that already use Skyfire.
Build on Nagent
Connect Skyfire to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Skyfire, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Skyfire is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Skyfire is connected, you configure its 16 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Skyfire steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Skyfire event fires, the agent kicks off automatically.
Every Skyfire action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Skyfire ships with 16 pre-built ai agents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Skyfire together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Skyfire-based workflows tailored to your business.