Skyfire
Skyfire is the open identity and payments layer for AI agents. It lets AI agents securely create accounts, verify a real-world identity (Know Your Agent, KYA), and autonomously pay for digital services using token-based authentication and stablecoin settlement. Developers use Skyfire to monetize APIs, tools, MCP servers, and content directly to agents. The platform issues three signed, interoperable KYAPay token types — kya (identity), pay (payment), and kya-pay (combined) — that buyer agents present to seller services over a simple REST API and a hosted MCP server. Sellers validate and charge tokens, discover services, and manage seller-service lifecycles, while enterprises manage users and agents through admin APIs. Skyfire is backed by DCVC, Lightspeed Venture Partners, and Trinity Ventures.
Skyfire publishes 6 API contracts indexed on the APIs.io network, including Agents API, Auth API, Directory API, and 3 more. Tagged areas include Company, AI Agents, Agentic Payments, Identity, and Payments.
The Skyfire catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
Skyfire’s developer surface includes engineering blog, documentation, API reference, getting-started guide, signup flow, support, authentication, and 30 more developer resources.
What this lets a business do 1
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Agent Skills (SKILL.md packages) | undeclared | - | - | 1 |
| Stablecoins and Tokenization (stablecoin issuers, tokenized assets) | undeclared | - | - | 1 |
| x402 Micropayments & Agentic Pay-per-Call | undeclared | - | - | 1 |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 3
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
Skyfire API
REST API for AI-agent identity and payments. Buyer agents create kya, pay, and kya-pay tokens; seller agents introspect and charge tokens and manage seller services; enterprises...
Skyfire Agents API
The Agents API from Skyfire — 6 operation(s) for agents.
Skyfire Auth API
The Auth API from Skyfire — 1 operation(s) for auth.
Skyfire Directory API
The Directory API from Skyfire — 5 operation(s) for directory.
Skyfire Organizations API
The Organizations API from Skyfire — 10 operation(s) for organizations.
Skyfire Tokens API
The Tokens API from Skyfire — 4 operation(s) for tokens.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Agent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Skyfire Context
JSON-LDSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
Skyfire API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions for this provider's data models.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll for all 10
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Skyfire API — frequently asked questions
Does Skyfire have an API?
Yes. APIs.io lists 6 APIs from Skyfire, including Skyfire API, Skyfire Agents API and Skyfire Auth API, and 3 more.
Is there an OpenAPI specification for the Skyfire API?
Yes. APIs.io indexes 5 OpenAPI specifications for Skyfire, each linked for download from this page.
How do I authenticate with the Skyfire API?
Skyfire uses bearer-token authentication (apiKey · 2 schemes). The details are profiled on APIs.io as Skyfire Authentication.
Does Skyfire have an MCP server?
Yes. APIs.io lists 1 MCP server for Skyfire: Remote MCP server at mcp.skyfire.xyz over HTTP.
Is the Skyfire API ready for AI agents?
Skyfire has a Kin Score of 46.0 out of 100 (developing) and an Agent Readiness score of 37.4 (agent-ready), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.