Which API key does a charge need?

The seller key, not the buyer's. Charge Skyfire Token is a seller-side operation: the buyer creates the token and calls your service with it, you deliver, then you charge. A 401 means an invalid or expired token or the wrong key, and a 402 means the charge exceeded the token's value.

What is the difference between the three token types?

A KYA token identifies the agent, a PAY token authorises spend, and a KYA+PAY token does both in one. Lyro picks based on what the seller requires, and runs Introspect Skyfire Token before the call when there has been a delay, so an expired token does not waste the request.

Does Skyfire need to know where our requests come from?

It can. Set Agent Source IP Addresses registers the IP addresses an agent's requests originate from, and it is done before tokens are created rather than after a call is rejected. That allowlist is what keeps a leaked credential from being usable somewhere else.

How does Lyro prove a seller charged the agreed amount?

Get Skyfire Token Charges audits the charges made against a specific token, showing exactly what each seller took and when. Set against the token's authorised value, that answers the reconciliation question - a five dollar authorisation and what was actually drawn against it - from the record rather than an invoice.

Skyfire MCP integration

Browses the service directory, issues KYA and PAY tokens scoped to one purchase, audits what sellers charged, and collects payment seller-side.

Connect Skyfire See all integrations

16actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get directory service by ID
Lyro retrieves full details for a specific Skyfire service by ID. Agents can confirm service availability and pricing without navigating the dashboard.
Get services by tags
Lyro filters available Skyfire services by tags to find specific categories. Agents quickly discover relevant services matching customer needs.
List agent seller services
Lyro lists all services registered by the seller agent. Agents can inventory available offerings without manual checks.

See all 16 actions

How businesses use Skyfire + Lyro

Each card is one request a support team gets, and the Skyfire actions Lyro runs to close it.

Find a service worth paying for
Lyro narrows the directory by tag rather than browsing everything, then reads a candidate's terms of service, API specification, and integration URLs before any money is committed.
Get All Service TagsGet Services by TagsGet Skyfire Service Details
Issue a token scoped to one purchase
Lyro checks the buyer wallet balance first to avoid a decline, then issues a PAY token for spend alone or a KYA+PAY token that also identifies the agent to the seller.
Get Skyfire Buyer Wallet BalanceCreate Skyfire PAY TokenCreate Skyfire KYA+PAY Token
Reconcile what was actually charged
Lyro audits the charges made against a token, lists the buyer tokens outstanding, and introspects one to confirm it is still valid before a seller call is attempted.
Get Skyfire Token ChargesList Skyfire Buyer TokensIntrospect Skyfire Token
Collect payment as the seller
Lyro charges a buyer's token once the service has been delivered, lists the services registered under the seller agent, and registers the source IPs those requests come from.
Charge Skyfire TokenList Agent Seller ServicesSet Agent Source IP Addresses

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Skyfire actions it has and picks the ones a request needs.

01
Connect Skyfire
Authorize the Skyfire account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Skyfire actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Skyfire · Lyro

Everything else about Skyfire

Setup, permissions, and the limits of what Lyro can do inside Skyfire.

The seller key, not the buyer's. Charge Skyfire Token is a seller-side operation: the buyer creates the token and calls your service with it, you deliver, then you charge. A 401 means an invalid or expired token or the wrong key, and a 402 means the charge exceeded the token's value.

Every action available in Skyfire

All 16 actions your agent can call on Skyfire, straight from the live MCP connection.

Charge skyfire token
Charge a buyer's token (seller-side operation).
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 service tags
Fetch all service tags to discover filtering options.
Get skyfire buyer wallet balance
Retrieve buyer wallet balance.
Get directory service by ID
Get full details for a specific service in the Skyfire directory by its ID.
Get skyfire service details
Get full details for one service.
Get services by agent
Browse all services from one seller agent.
Get services by tags
Filter services by tags to find exactly what you need.
Get skyfire token charges
Audit charges for a specific token.
Introspect skyfire token
Check if a token is still valid before calling a seller service.
List agent seller services
List all services registered by the authenticated seller agent.
List skyfire buyer tokens
Inspect buyer tokens for observability.
List skyfire directory services
Browse Skyfire's service directory to obtain sellerServiceId for token creation.
Set agent source IP addresses
Register IP addresses as sources for Agent requests (PUT /api/v1/agents/source-ips).