Seller Guide

What is a seller?

A seller is an agent account that lets a user publish and monetize services, tools, or APIs, and accept payment from buyer agents. Unlike buyer agents, which are created automatically at signup, a seller agent must be created explicitly from the Skyfire Dashboard.

A seller agent:

• Belongs to exactly one user and always has the Seller role
• Registers one or more seller services (the products, APIs, websites, or MCP servers it offers)
• Defines the identity and payment requirements for buyer requests
• Verifies incoming tokens using standard JWKS libraries to authenticate the buyer (kya) and charge them (pay or kya-pay)
• Has its own wallet that receives funds after a service is delivered and its token is charged
• Is accessed programmatically through its own API keys

For how sellers fit into the wider platform, see Platform Structure.

1. Create a seller account

From the Skyfire Dashboard, start a seller account in either of two ways:

• Click the Create Seller Account checklist prompt, or
• Toggle your account type to Seller using the switch in the upper-left corner of the console.

You'll be asked to enter a Display Name. This is the name shown publicly in the Skyfire directory for your seller services.

Skyfire then automatically:

• Generates a seller account
• Creates an associated wallet
• Guides you through the Seller Service Setup flow

You're now a seller on Skyfire! Next, create your first service.

2. Create a seller service

Click Create Service to publish your first monetizable API or digital offering to agents. You'll be asked to provide:

3. Set identity requirements (optional)

Skyfire supports flexible identity enforcement through KYA. You can require buyer agents to include verified identity in their kya or kya-pay tokens, and choose which buyers to accept:

• Individuals
• Organizations
• Both

Each buyer agent represents either an individual or an organization, never both. Your service should validate only the fields relevant to the buyer's verification type.

This step is optional. If you don't set any KYA requirements, any buyer with funds can transact with your service. See Identity Fields for the fields you can request, and Identity Verification (KYA) for how verification works.

4. Accept and charge tokens

Your seller service must be able to accept and validate incoming Skyfire tokens, and, when payment is required, charge them:

• Verify each token using standard JWKS libraries.
• For paid services, use your seller API key to call the Charge Token API after you deliver.
• You can make partial charges, so a token does not need to be fully consumed in one call.

Full mechanics: Verify and Extract Data from Tokens, Charge Token, and Payments & Settlement.

5. Submit for approval

After you submit a seller service, Skyfire reviews it to make sure functional services are available in the directory. This typically takes 24 to 48 hours. Once approved, your service becomes discoverable to agents in the Skyfire Directory.

Managing your seller agent

Your dashboard organizes seller activity into two tabs.

API Keys

• Generate API keys to authenticate your service
• View, rotate, and deactivate keys as needed

These keys are required when charging pay or kya-pay tokens sent by buyer agents. For more, see API Authentication.

Charges

The Charges tab shows every successful payment made to your service:

• Token used
• Buyer agent ID
• Amount charged
• Timestamp and transaction status

Once your service is live, buyer agents can discover it in the Skyfire directory, send tokens, and begin transacting, all without human intervention.