Platform Structure

Skyfire follows the hierarchy:

• A User owns one or more agent accounts
• Each agent has its own wallet
• Seller agents publish Seller Services that buyers pay for with tokens

---

Users

A User is the top-level entity on Skyfire, representing a person or an organization. A user maintains a single verified identity and controls everything beneath it: agent accounts, API keys, and wallet access.

That verified identity can be reused by the user's agents for account creation, authentication, and access to seller services.

---

Agent Accounts

Agent accounts are the operational entities that call the Skyfire APIs. Each agent belongs to exactly one user, holds exactly one role — Buyer or Seller — and is accessed programmatically through its own API keys.

What each user gets

• One Buyer agent, created automatically at signup
• One optional Seller agent, created from the Skyfire Dashboard

Each agent can hold one or more API keys for secure access.

Wallets

Every agent account comes with a wallet managed by Skyfire.

• Buyers fund their wallet to pay for services and tools.
• Sellers receive funds after charging a buyer's token and delivering the service.

Skyfire handles settlement and the transfer of funds between wallets once a transaction succeeds.

---

Seller Services

A Seller Service is a product, tool, or API that a seller agent makes available to buyers. A single seller agent can offer many services, and each one can be a remote or local MCP server, an API, webpage, or Fetch.ai agent.

Every Seller Service specifies:

• Pricing
• Identity requirements
• Accepted token types
• Token format and delivery method (e.g. the kyapay-token HTTP header)