How Skyfire’s scores are calculated

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

• [probe] https://docs.skyfire.xyz/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.skyfire.xyz/llms.txt # Skyfire Developer Portal Documentation > Skyfire is the open identity and payments layer for AI agents. We enable AI”
• [probe] https://docs.skyfire.xyz/reference/introspect-token.md“PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api/v1/tokens/introspect answered with the structured challenge {"code":"NOT_AUTHORIZED","message":"Invalid API Key"} — and docs.skyfire.xyz serves llms.txt keylessly ('# Skyfire Developer Portal Documentation... the open identity and payments layer for AI agents').”
• [probe] https://docs.skyfire.xyz/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.xyz/api/openapi.json, https://docs.skyfire.xyz/.well-known/openapi.json)”

Run the product headlessly / in CI for automationweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

• [claimed-docs] https://docs.skyfire.xyz/docs/quickstart.md“API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”
• [claimed-docs] https://docs.skyfire.xyz/reference/charge-token.md“Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued token.”
• [claimed-docs] https://docs.skyfire.xyz/reference/introspect-token.md“Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic commerce workflows!”
• [probe] https://docs.skyfire.xyz/reference/introspect-token.md“PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api/v1/tokens/introspect answered with the structured challenge {"code":"NOT_AUTHORIZED","message":"Invalid API Key"} — and docs.skyfire.xyz serves llms.txt keylessly ('# Skyfire Developer Portal Documentation... the open identity and payments layer for AI agents').”
• [claimed-docs] https://docs.skyfire.xyz/docs/quickstart.md“Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single agent (Buyer or Seller)", passed in the skyfire-api-key header. Sellers create a service and "provide details like: name, type, pricing, identity requirements, etc." then "Submit for approval." — seller services are approval-gated by Skyfire.”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflows" — documented tools are "find-sellers", "create-kya-token", "create-pay-token", and "create-kya-payment-token", authenticated with the skyfire-api-key header (sandbox at https://mcp-sandbox.skyfire.xyz/mcp).”

Plug MCP servers into this product so it can use their toolsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic commerce workflows!”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflows" — documented tools are "find-sellers", "create-kya-token", "create-pay-token", and "create-kya-payment-token", authenticated with the skyfire-api-key header (sandbox at https://mcp-sandbox.skyfire.xyz/mcp).”

Connect an agent via an official MCP serverweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic commerce workflows!”
• [claimed-docs] https://docs.skyfire.xyz/docs/mcp-servers.md“Create an MCP Server Resource that explains which token types are required (`kya`, `pay`, and/or `kya-pay`), how tokens must be passed (the `kyapay-token` header), and when a payment token is required versus identity only.”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflows" — documented tools are "find-sellers", "create-kya-token", "create-pay-token", and "create-kya-payment-token", authenticated with the skyfire-api-key header (sandbox at https://mcp-sandbox.skyfire.xyz/mcp).”

Use an official CLIweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Drive the product through a documented public APIweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

• [claimed-docs] https://docs.skyfire.xyz/docs/quickstart.md“API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”
• [claimed-docs] https://docs.skyfire.xyz/reference/charge-token.md“Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued token.”
• [claimed-docs] https://docs.skyfire.xyz/reference/introspect-token.md“Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”
• [probe] https://docs.skyfire.xyz/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.skyfire.xyz/llms.txt # Skyfire Developer Portal Documentation > Skyfire is the open identity and payments layer for AI agents. We enable AI”
• [probe] https://docs.skyfire.xyz/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.xyz/api/openapi.json, https://docs.skyfire.xyz/.well-known/openapi.json)”
• [probe] https://docs.skyfire.xyz/reference/introspect-token.md“PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api/v1/tokens/introspect answered with the structured challenge {"code":"NOT_AUTHORIZED","message":"Invalid API Key"} — and docs.skyfire.xyz serves llms.txt keylessly ('# Skyfire Developer Portal Documentation... the open identity and payments layer for AI agents').”
• [claimed-docs] https://docs.skyfire.xyz/reference/charge-token.md“Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued token." and "Tokens may be charged multiple times until their balance is exhausted." Timing windows are explicit — "Skyfire allows charges to be submitted for up to 24 hours after a token expires" (only for tokens validated before expiry) and "Settlement may take up to 51 hours depending on token expiration and charging activity." Overcharges fail with an HTTP 402 PAYMENT_ERROR.”

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

• [claimed-docs] https://docs.skyfire.xyz/docs/quickstart.md“API keys are created and managed in your Agent Dashboard, and each key is scoped to a single agent (Buyer or Seller).”
• [claimed-docs] https://docs.skyfire.xyz/docs/payments-settlement.md“Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation requires the amount to be within the buyer's available balance)", so "the seller is guaranteed to be paid, up to the token's committed amount. Sellers do not carry buyer non-payment risk for charges within a valid token." The committed amount is a ceiling, and "Charges above the token's remaining balance are rejected."”
• [claimed-docs] https://docs.skyfire.xyz/docs/kya.md“"Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agents." The optional paid verification (Individual or Organization subscription) "attaches a real-world individual or organization identity to the agents you control", tokens disclose only the identity fields a service requires, and gating is hard: "If a buyer is not verified to the level a service requires, token creation fails and the transaction does not proceed."”
• [claimed-docs] https://docs.skyfire.xyz/docs/payments-settlement.md“Revocation is bounded by design: deactivating an account does not void already-issued pay/kya-pay tokens — "New token creation stops at deactivation, but in-flight tokens are honored so sellers are paid for services they were legitimately asked to deliver." Outstanding tokens stay chargeable until expiry plus the 24-hour grace period; no per-token revocation API is documented, so the practical caps are the token amount and its 10-second-to-24-hour expiry.”
• [claimed-docs] https://docs.skyfire.xyz/docs/quickstart.md“Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single agent (Buyer or Seller)", passed in the skyfire-api-key header. Sellers create a service and "provide details like: name, type, pricing, identity requirements, etc." then "Submit for approval." — seller services are approval-gated by Skyfire.”

Build against official SDKsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic commerce workflows!”
• [probe] https://docs.skyfire.xyz/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.xyz/api/openapi.json, https://docs.skyfire.xyz/.well-known/openapi.json)”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflows" — documented tools are "find-sellers", "create-kya-token", "create-pay-token", and "create-kya-payment-token", authenticated with the skyfire-api-key header (sandbox at https://mcp-sandbox.skyfire.xyz/mcp).”

Subscribe to events via webhooksweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

• [probe] https://docs.skyfire.xyz/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.xyz/api/openapi.json, https://docs.skyfire.xyz/.well-known/openapi.json)”
• [claimed-docs] https://docs.skyfire.xyz/reference/charge-token.md“Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued token.”
• [claimed-docs] https://docs.skyfire.xyz/reference/introspect-token.md“Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

• [probe] https://docs.skyfire.xyz/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.xyz/api/openapi.json, https://docs.skyfire.xyz/.well-known/openapi.json)”
• [claimed-docs] https://docs.skyfire.xyz/reference/charge-token.md“Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued token.”
• [claimed-docs] https://docs.skyfire.xyz/reference/introspect-token.md“Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 5 (quality) × 0.6 (partial) = 3.0 of 10 max

• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflows" — documented tools are "find-sellers", "create-kya-token", "create-pay-token", and "create-kya-payment-token", authenticated with the skyfire-api-key header (sandbox at https://mcp-sandbox.skyfire.xyz/mcp).”

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

• [probe] https://docs.skyfire.xyz/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.xyz/api/openapi.json, https://docs.skyfire.xyz/.well-known/openapi.json)”
• [probe] https://docs.skyfire.xyz/reference/introspect-token.md“PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api/v1/tokens/introspect answered with the structured challenge {"code":"NOT_AUTHORIZED","message":"Invalid API Key"} — and docs.skyfire.xyz serves llms.txt keylessly ('# Skyfire Developer Portal Documentation... the open identity and payments layer for AI agents').”

Do everything through the API that I can do in the UIweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

• [claimed-docs] https://docs.skyfire.xyz/docs/quickstart.md“Click Create Service and provide details like: name, type, pricing, identity requirements, etc. Submit for approval.”
• [claimed-docs] https://docs.skyfire.xyz/reference/charge-token.md“Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued token.”
• [claimed-docs] https://docs.skyfire.xyz/reference/introspect-token.md“Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic commerce workflows!”
• [claimed-docs] https://docs.skyfire.xyz/docs/kya.md“Skyfire supports identity verification through Know Your Agent (KYA), a single verification that applies to both your buyer and seller agents.”
• [probe] https://docs.skyfire.xyz/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.skyfire.xyz/openapi.json, https://docs.skyfire.xyz/swagger.json, https://docs.skyfire.xyz/api/openapi.json, https://docs.skyfire.xyz/.well-known/openapi.json)”
• [claimed-docs] https://docs.skyfire.xyz/docs/quickstart.md“Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single agent (Buyer or Seller)", passed in the skyfire-api-key header. Sellers create a service and "provide details like: name, type, pricing, identity requirements, etc." then "Submit for approval." — seller services are approval-gated by Skyfire.”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflows" — documented tools are "find-sellers", "create-kya-token", "create-pay-token", and "create-kya-payment-token", authenticated with the skyfire-api-key header (sandbox at https://mcp-sandbox.skyfire.xyz/mcp).”

Export all of my data in open formats and leaveweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Read the product's source under an open licenseweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

• [probe] https://docs.skyfire.xyz/reference/introspect-token.md“PROBE runtime (recorded 2026-09-14): Skyfire's token API is live and key-gated as documented — a keyless POST to https://api.skyfire.xyz/api/v1/tokens/introspect answered with the structured challenge {"code":"NOT_AUTHORIZED","message":"Invalid API Key"} — and docs.skyfire.xyz serves llms.txt keylessly ('# Skyfire Developer Portal Documentation... the open identity and payments layer for AI agents').”
• [claimed-docs] https://docs.skyfire.xyz/docs/kyapay-tokens.md“"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens are JWTs, exchanged directly between buyer and seller, and "All Skyfire-issued tokens conform to the open KYAPay protocol, an industry specification for identity-linked payment credentials purpose-built for autonomous systems." (KYAPay.org) — the token format is published as open, though charging, wallets, and settlement all run through Skyfire's own APIs.”

Self-host the core productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

• [claimed-docs] https://docs.skyfire.xyz/docs/kyapay-tokens.md“"A KYAPay token is a signed, interoperable credential that packages agent identity and payment intent into a verifiable envelope." Tokens are JWTs, exchanged directly between buyer and seller, and "All Skyfire-issued tokens conform to the open KYAPay protocol, an industry specification for identity-linked payment credentials purpose-built for autonomous systems." (KYAPay.org) — the token format is published as open, though charging, wallets, and settlement all run through Skyfire's own APIs.”
• [claimed-docs] https://docs.skyfire.xyz/docs/payments-settlement.md“Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation requires the amount to be within the buyer's available balance)", so "the seller is guaranteed to be paid, up to the token's committed amount. Sellers do not carry buyer non-payment risk for charges within a valid token." The committed amount is a ceiling, and "Charges above the token's remaining balance are rejected."”
• [claimed-docs] https://docs.skyfire.xyz/docs/quickstart.md“Onboarding: signup auto-creates a Buyer Agent with a "pre-funded wallet"; API keys are managed per agent and "each key is scoped to a single agent (Buyer or Seller)", passed in the skyfire-api-key header. Sellers create a service and "provide details like: name, type, pricing, identity requirements, etc." then "Submit for approval." — seller services are approval-gated by Skyfire.”

Get AI-generated insights and suggestions from my data inside the productweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic commerce workflows!”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflows" — documented tools are "find-sellers", "create-kya-token", "create-pay-token", and "create-kya-payment-token", authenticated with the skyfire-api-key header (sandbox at https://mcp-sandbox.skyfire.xyz/mcp).”
• [claimed-docs] https://docs.skyfire.xyz/docs/payments-settlement.md“Pay tokens carry committed amounts: "At creation, the token's amount is committed against the buyer's wallet (which is why token creation requires the amount to be within the buyer's available balance)", so "the seller is guaranteed to be paid, up to the token's committed amount. Sellers do not carry buyer non-payment risk for charges within a valid token." The committed amount is a ceiling, and "Charges above the token's remaining balance are rejected."”
• [claimed-docs] https://docs.skyfire.xyz/docs/introduction-to-skyfire.md“Skyfire gives agents verified identity and payment credentials — "No 403 errors, captchas or blocked checkouts. Authenticated access and payment capability, everywhere your agents need to be." Three token types (kya proves identity, pay authorizes payment, kya-pay combines both) drive a four-step loop ending in settlement: "For paid services, the seller charges the token and Skyfire moves the funds between the buyer's and seller's wallets." A kya "token only proves identity, so it can't be charged".”

Delegate tasks to a built-in AI assistant inside the productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Operate the product with natural-language commandsweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“Add the Skyfire MCP server ... Your agent is now ready to discover sellers, generate `kya` or `pay` tokens, and instantly execute agentic commerce workflows!”
• [claimed-docs] https://docs.skyfire.xyz/docs/mcp-servers.md“Create an MCP Server Resource that explains which token types are required (`kya`, `pay`, and/or `kya-pay`), how tokens must be passed (the `kyapay-token` header), and when a payment token is required versus identity only.”
• [claimed-docs] https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server.md“The Skyfire MCP server at https://mcp.skyfire.xyz/mcp lets agents "Discover sellers", create tokens, and "Orchestrate agent commerce workflows" — documented tools are "find-sellers", "create-kya-token", "create-pay-token", and "create-kya-payment-token", authenticated with the skyfire-api-key header (sandbox at https://mcp-sandbox.skyfire.xyz/mcp).”

Perform bulk operations across many items at onceweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

• [claimed-docs] https://docs.skyfire.xyz/reference/charge-token.md“Charge a `pay` or `kya-pay` token as a seller agent or seller service. Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued token.”
• [claimed-docs] https://docs.skyfire.xyz/reference/introspect-token.md“Check whether a token is currently usable and get the remaining balance as a buyer or seller agent.”
• [claimed-docs] https://docs.skyfire.xyz/reference/charge-token.md“Sellers collect via the Charge Token API: "Use this API after delivering a service, tool, or resource to collect payment from a buyer-issued token." and "Tokens may be charged multiple times until their balance is exhausted." Timing windows are explicit — "Skyfire allows charges to be submitted for up to 24 hours after a token expires" (only for tokens validated before expiry) and "Settlement may take up to 51 hours depending on token expiration and charging activity." Overcharges fail with an HTTP 402 PAYMENT_ERROR.”

Define rules that trigger actions automatically on eventsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Schedule recurring jobs or workflowsweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Version, review, and roll back my automationsweight 1

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh