Skyfire uses signed tokens to carry identity and payment information between agents and services. These tokens are structured as JWTs and come in different forms depending on the action the agent needs to perform including:

• Creating an account
• Completing an ecommerce checkout
• Making a micropayment for a service
• Starting a subscription
• Accessing a protected website

Each token includes only the minimum necessary information for its intended use, enabling secure, verifiable, and privacy-preserving interactions across the agent economy.

All Skyfire-issued tokens conform to the open KYAPay protocol, an industry specification for identity-linked payment credentials purpose-built for autonomous systems. This protocol standardizes how identity and value are packaged and transmitted, ensuring interoperability across agents, services, and platforms that adopt the KYAPay protocol. See more at KYAPay.org

Token Overview

Tokens are created by a Buyer Agent for a specific Seller Service.
Buyers and sellers exchange tokens directly with each other. Skyfire is not involved in the token exchange.

Token Types

KYA

kya — Identity Token

kya tokens contain key-value pairs that specify the verified identity of the individual or business that owns the buyer agent.

Example use case:

• A seller may use the identity from a kya token to automatically create an account for the buyer agent.

PAY

pay — Payment Token

pay tokens contain the payment value that the buyer has committed to pay the seller upon delivery of a good, service, or tool. Sellers charge the pay token using a Skyfire API after the good/service/tool is provided.

Example use case:

• A seller may charge the pay token as part of an ecommerce checkout for an already logged in buyer agent.

KYA+PAY

kya+pay — Combined Identity + Payment Token

kya+pay tokens contain both the identity and payment value in a single token.

Example use case:

• Sellers can use a kya+pay token to enable a guest checkout experience for buyer agents.