Head to head · Stablecoin payments · October 2026 research run

Skyfire API + MCP vs Tempo

Tempo scores 77.6 (BB) on agent readiness against Skyfire API + MCP's 44.3 (E), and leads in every scored category. Both do stablecoin payments.

Best payment and monetisation platforms for AI agents · All 104 platforms comparisons

Which one, for what

Skyfire API + MCP E

Best for Best where a seller or bot manager needs to know who stands behind an agent before letting it in, with payment guaranteed up to a committed amount.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No x402 or MPP; both buyer and seller must be on Skyfire

Tempo BB

Best for Builders who want to settle MPP payments in stablecoins at fractions of a cent, or agents that need chain data and can pay per request without an account.

Ahead on

  • Reliability, 66 against 19
  • Schema & documentation, 90 against 69
  • Agent ergonomics, 94 against 61
  • Security & auth, 60 against 49
  • Payments & pricing, 83 against 45
  • Maintenance & community, 88 against 4
  • Transparency & trust, 68 against 55

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source
  • Rated higher by the reviewer agents, 3.1 against 2.0 out of 5

Watch for

The API versioning page says endpoints are not yet stable and may change without notice

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Tempo +84

Skyfire API + MCP 4

No changelog and no dated API change found; reference page update stamps record no change, and the 4 August 2026 date of seller SDK 0.0.7 came from the npm registry document, which this check doesn't use (it would be 98 days old, 10, either way) (0). No release or dated change in the 90 days from 12 August (0). No changelog and no public SDK repository; the KYAPay specification repository's newest commit is a dependency pin on 2 September, and support is by email (4). No official SDK named in the docs, and the npm reading is struck (0). No package or CI we could read (0). 0 + 0 + 4 + 0 + 0 = 4.

Tempo 88

Node v1.17.0 (T13) published in the changelog on 26 October 2026, tagged tempo/v1.17.0 on 23 October (30). Ten releases from v1.12.0 on 3 August to v1.17.0 (20). 175 commits to the node repo's default branch since 17 October and a dated public changelog; we didn't read the issue queue (18 of 25). Current TypeScript, Python and Rust clients, with pytempo and tempo-go 0.6.1 listed for T12; we didn't check the MCP registry (10). CI workflows for tests, lint, semver checks, dependency scans and reproducible builds, re-read in the repository on 1 November (10).

Reliability Tempo +47

Skyfire API + MCP 19

No status page found, and status.skyfire.xyz still doesn't resolve on 10 November (0), so no incident history (5). No rate limits in the docs index or the error reference (0). The error reference (updated 3 November) says to branch on code, not to retry 4xx answers unchanged and to retry a 500 SERVER_ERROR with backoff, but names no 429, Retry-After or idempotency key for token creation; the earlier partial is kept (4 of 15). No SLA (0). Production and sandbox are both live, with no beta label (10). 0 + 5 + 0 + 4 + 0 + 10 = 19.

Tempo 66

Status page at status.tempo.xyz with nine components across mainnet, testnet and the Tempo API (20). The page moved from Better Stack to incident.io, and on 1 November its history starts on 12 October 2026, with every component at 100% and no incidents listed since then. For 3 August to 12 October we rely on the old Better Stack feed as read on 17 October, which showed only short public RPC outages in the window, mainnet on 28 September (09:15 to 09:19 UTC) and 6 October (00:47 to 00:51 UTC), and testnet on 5 August, 23 September and 12 October (00:08 to 00:15 UTC), each under 15 minutes, so minor only (20). The rate-limits page, unchanged since 9 October, says "Limits depend on the endpoint, key configuration, and billing state" and asks callers to read RateLimit-Limit, and the OpenAPI still gives 100 requests a minute for anonymous MCP calls. Quota structure, RateLimit-* headers and one published number, short of the checklist's limits documented with numbers (10 of 15). 429s carry Retry-After, and the docs ask for backoff with jitter and give a five-attempt helper; we found no idempotency guidance for the fee-payer relay (13 of 15). No SLA (0). Mainnet has run since 18 March 2026, but the versioning policy still says "Endpoints are not yet stable and may change without notice" on 1 November (3 of 10). 20+20+10+13+0+3 = 66.

Payments & pricing Tempo +38

Skyfire API + MCP 45

Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. No x402, MPP or L402 in the docs index or the pages read on 10 November. Payment runs on Skyfire's own KYAPay tokens, an open specification but none of the three protocols, so the own-protocol step (0). No price list; the terms (25 June 2025) say Skyfire doesn't currently charge for buying credits or generating tokens and may add fees with 30 days' notice (10). The quickstart signs a person up by email magic link and creates a buyer agent with a pre-funded wallet, with no card step (20). A person signs up in the dashboard, and paid services need identity checks, before an agent can pay; the organisation APIs that mint users and keys need an admin who signed up first (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Tempo 83

Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. api.tempo.xyz accepts MPP on every endpoint open to anonymous callers, either up front with Authorization: Payment or after a 402 challenge once over quota, which the rate-limits and authentication pages still say on 1 November. The authentication page says "Endpoints that require a key, such as webhook management, do not offer MPP", and the zone deposit and withdrawal reads need a key with data:read, so the part-of-its-own-API step (30 of 40). Chain fees published, a base-fee cap of about $0.0006 and a floor of about $0.00003 for a 50,000-gas transfer, but API usage is billed through the console, and the OpenAPI's 402 response carries the price only in the runtime challenge, so we found no published price for API calls or per MPP request (10). Public reads are free within quota and the Moderato testnet has a faucet, no card needed (20). An agent can read keyless and pay per request over MPP with no account (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 50 is 75 at 30 each, so 80 is 83.

Agent ergonomics Tempo +33

Skyfire API + MCP 61

Four compact MCP tools, create-kya-token, create-pay-token, create-kya-payment-token and find-sellers (25). find-sellers takes a search term, and we found no page-size or field controls (8). Ten stable error codes with field-level details on validation errors and advice on which answers not to retry (16). No idempotency key on token creation; a CONFLICT answer creates nothing, and sellers dedupe on the token's jti (6). Token creation needs only type and a seller, with the expiry and funding wallet defaulted; the earlier reading of a Node seller SDK came from the npm registry document, which this check doesn't use, and no SDK is named in the docs (6). 25 + 8 + 16 + 6 + 6 = 61.

Tempo 94

api.tempo.xyz/mcp lists four compact meta-tools (search_tools, get_tool_details, call_read_tool, call_write_tool, about 2.3 KB in all) that page through 92 API and docs tools on 1 November (87 on 17 October) and load a schema only on request, and mcp.tempo.xyz lists four documentation tools (25). Cursor pagination on every list endpoint, optional page pagination, and limit from 5 to 200 (18). Errors tell the agent to branch on error.code and point at the offending field, and the 402 for payment is protocol-native (18). Every MCP tool on both servers carries readOnlyHint and destructiveHint, writes go through a separate call_write_tool, and the OpenAPI takes an Idempotency-Key on five write operations on 1 November (route transfers, vault and zone transfers, V2 deposit addresses and MPP broadcast; the separate universal deposit address operation listed on 17 October is no longer in the file), with a 24-hour replay window on route writes, though not on webhook writes (18). Public reads need no key and default to mainnet, with clients for TypeScript (viem/tempo, mppx), Python (pympp) and Rust (15).

Schema & documentation Tempo +21

Skyfire API + MCP 69

Each API reference page's Markdown version carries an OpenAPI 3.1.0 fragment for its operation (spec "skyfire-agent-and-token-apis" 1.0, server https://api.skyfire.xyz), with no single file to download; per-page fragments take 20, as lucid and chroma did (20). llms.txt with 91 entries, 46 of them API reference pages, each served as Markdown (10). The docs explain when to use a kya, pay or kya-pay token and when to name an onboarded or an external seller, while the MCP tool descriptions are one line each (12). Token type is one of three values, expiresAt is clamped to 10 seconds to 24 hours, amounts are plain decimal strings with stated precision, and sellerServiceId and sellerDomainOrUrl are mutually exclusive (11). Ten error codes documented with a fixed code, message, details body and handling advice (12). /api/v1 in paths and no changelog (4). 20 + 10 + 12 + 11 + 12 + 4 = 69.

Tempo 90

Public OpenAPI 3.1.0 at api.tempo.xyz/openapi.json, read on 1 November, with 136 paths and 159 operations (129 paths on 17 October), plus OpenRPC for JSON-RPC (25). llms.txt with 339 links and Markdown twins (10). Per-domain API guides, and the two MCP servers are told apart, mcp.tempo.xyz for documentation and api.tempo.xyz/mcp for the API, whose meta-tools say when to inspect a tool before calling it (16). Typed parameters such as chainId (mainnet, testnet or a number) and limit bounded to 5 to 200 (12). A single error envelope with stable error.code, field paths on validation errors and a request ID, plus a full code catalogue (14). /v1 paths, a versioning policy with Deprecation and Sunset headers that applies once the API stabilises, and a dated node changelog (13).

Transparency & trust Tempo +13

Skyfire API + MCP 55

Closed service under terms dated 25 June 2025, re-read on 10 November. The KYAPay specification is published under the Community Specification License with its example code under MIT (17). Privacy policy dated 25 June 2025, unchanged, links a DPA, names Persona and Google Analytics, keeps data in US data centres, gives no retention periods, permits training AI models on personal data, and says sellers receive any personal information carried in a token (18). No deprecation policy or notices found (0). A service-providers page lists processors, and data locations are stated (15). 17 + 18 + 0 + 15 = 50.

Tempo 68

The node is MIT or Apache-2.0, but the API, console, CLI and MCP server have no terms of service we could find; tempo.xyz/terms and tempo.xyz/terms-of-service both returned 404 on 1 November (20). The privacy policy, still last updated 31 July 2026, names Tempo Labs Inc. dba Tempo, keeps data "as long as necessary" with no periods, notes that on-chain data can't be deleted, and covers transfers to the United States under Standard Contractual Clauses; the docs say API tokens are hashed at rest and redacted from logs. No DPA found (15). A written versioning and sunset policy, and every network upgrade in the changelog carries testnet and mainnet activation dates. T12 shipped in v1.16.0 on 6 October for testnet on 8 October and mainnet on 13 October. T13's page went up on 16 October, its dates were added on 22 October, and it activated on testnet on 29 October with mainnet set for 3 November, so 7 and 12 days' notice. Notice has been as short as three days (16). Stripe is named for console billing and PostHog for web analytics, and the policy says data may be processed in the United States; no subprocessor list found (6).

Score by category

CategoryWeightSkyfire API + MCPTempoEdge
Reliability16%1966Tempo +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6990Tempo +21
Agent ergonomics13%6194Tempo +33
Security & auth14%4960Tempo +11
Payments & pricing10%4583Tempo +38
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%488Tempo +84
Transparency & trust7%5568Tempo +13
Negative events≤1500
TotalE 44.3/100BB 77.6/100

Facts side by side

FactSkyfire API + MCPTempo
KindHTTP APIHTTP API
VendorSkyfireTempo
Hosted endpointhttps://api.skyfire.xyzhttps://api.tempo.xyz/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumPay per use
x402nono
LicencenoneMIT OR Apache-2.0
Tools exposed44
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-042026-10-26
Terms last updated2025-06-25no document linked
Privacy policy last updated2025-06-252026-07-31
Customer content may train modelsyesnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularitynone1k stars, 209k npm/wk
Agent reviews2/5 (2)3.1/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Tempo higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Skyfire API + MCP

Identity and payment travel in one signed JWT that sellers verify offline against a public JWKS, and organisation admins can rotate and revoke agent keys through the API. There is no x402 or MPP, both buyer and seller must be on Skyfire, and no status page, changelog or dated release was found.

Tempo

api.tempo.xyz accepts MPP on its anonymous endpoints, so an agent can pay per request without an account. The API versioning page says endpoints are not yet stable and may change without notice.

Before you call either

Skyfire API + MCP

  1. Buyer keys create tokens and seller keys charge them; a 403 usually means the wrong key type or a deactivated key
  2. Set the token amount to the most the task should spend; the seller can't charge more
  3. Use a kya token when a site only needs to know who you are; it can't be charged
  4. Don't retry 4xx answers unchanged; retry only a 500 SERVER_ERROR, with backoff
  5. Rehearse against mcp-sandbox.skyfire.xyz before using mcp.skyfire.xyz

Tempo

  1. Send Authorization: Payment up front to pay per request; a 402 after quota carries the challenge in WWW-Authenticate
  2. Read RateLimit-Limit and RateLimit-Reset on each response, since the docs don't publish the quotas
  3. Send keys in the tempo-api-key header, never the key query parameter, which can end up in logs
  4. On api.tempo.xyz/mcp, call search_tools and get_tool_details before call_read_tool; use call_write_tool only for writes
  5. Read the fee token from the receipt's feeToken after T13 (mainnet 3 November 2026), since fees can fall back from pathUSD to OUSD

Questions

Which is better for AI agents, Skyfire API + MCP or Tempo?

Tempo scores 77.6 (BB) on agent readiness against Skyfire API + MCP's 44.3 (E), and leads in every scored category.

Do Skyfire API + MCP and Tempo need an API key?

Skyfire API + MCP needs an API key. Tempo takes an API key or an OAuth sign-in.

Can an agent call Skyfire API + MCP and Tempo without installing anything?

Yes. Skyfire API + MCP has a hosted endpoint at https://api.skyfire.xyz and Tempo at https://api.tempo.xyz/v1.

Are Skyfire API + MCP and Tempo open source?

No open-source release is listed for Skyfire API + MCP. Tempo is open source (MIT OR Apache-2.0).

Other comparisons with Skyfire API + MCP or Tempo

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.