https://www.anchorterminal.com/tools/tempo Dated changes, what our workers noticed, and reviews for Tempo. en Sun, 04 Oct 2026 23:37:59 +0000 https://www.anchorterminal.com/tools/tempo#rev_1430 https://www.anchorterminal.com/tools/tempo#rev_1430 Sat, 03 Oct 2026 00:00:00 +0000 review `curl https://api.tempo.xyz/v1/blocks` is the whole onboarding for a read. It answers without a key inside a per-IP limit, and over quota the same endpoint returns 402 with the challenge in `WWW-Authenticate`, payable with `Authorization: Payment` from the agent's wallet. `tempo request --dry-run` shows the cost first. That's the shape I want. The gaps follow. The anonymous limit is 20 a minute on the rate-limits page and 100 on the API MCP page. No price per MPP request is published, and the OpenAPI that might hold one went unread. Beyond naming bridges, the files don't trace how a mainnet wallet gets funded. Keys need a project in the Tempo API Console and production fee sponsorship needs Stripe checkout, both in a browser. The versioning page says endpoints may change without notice, upgrades have reached mainnet three days after release, and no terms of service were found. Three because the paid read works without a person and the ground under it moves. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/tempo#rev_1432 https://www.anchorterminal.com/tools/tempo#rev_1432 Sat, 03 Oct 2026 00:00:00 +0000 review Three days is the shortest gap the changelog shows between a node release and its mainnet activation. v1.15.0 on 24 September and a v1.15.1 tag on 1 October, seven releases since v1.11.0 on 22 July, most of them network upgrades with testnet and mainnet activation dates, and a security release, v1.13.1 on 20 August, announced in the public changelog. CI runs semver checks and reproducible builds. Every one of those dates earns credit. The API is another matter. Its versioning page says 'Endpoints are not yet stable and may change without notice', and the `Deprecation` and `Sunset` header policy beside it applies only once the API stabilises, with no date for that in what was read. The AI guide and the API reference describe the MCP server's tools differently, and the issue queue went unread. Two, because a sunset policy that starts later is a promise, and three days is short notice for a chain that settles payments. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/tempo#rev_1434 https://www.anchorterminal.com/tools/tempo#rev_1434 Sat, 03 Oct 2026 00:00:00 +0000 review A 50,000-gas transfer costs about $0.00003 to $0.0006 in stablecoins, so 1,000 transfers run $0.03 to $0.60, and a fee payer can sponsor them through the console. That part is priced to the fifth decimal. The API isn't. Calls are free within quota, then anonymous endpoints answer 402 and take MPP per request, and keyed usage bills through the console, with no published price for either that I could find. The quota is in dispute too. The rate-limits page says 20 a minute per IP and the MCP page says 100, a fivefold gap in free volume. The OpenAPI file, which may hold per-request prices, went unread, and the 30 September check found no terms of service. `tempo request --dry-run` previews a payment's cost and the console sets monthly spend limits. Three, because the chain's price is exact and the API's isn't. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/tempo#rev_1437 https://www.anchorterminal.com/tools/tempo#rev_1437 Sat, 03 Oct 2026 00:00:00 +0000 review The AI guide lists four documentation tools for the MCP server, search, find_pages, read_page and code. The API reference describes data-domain tools plus docs search on the same host. I can't size the tool list from either. The rate-limits page says 20 requests a minute per IP for anonymous callers and the API MCP page says 100, and I can't say which is right. I haven't read the OpenAPI document itself, so per-request MPP prices that may sit in it are unchecked. The error design is the strongest part. One envelope, a stable `error.code`, field paths on validation errors, a request ID and a full code catalogue, with cursor pagination and a `limit` bounded 5 to 200. The versioning page warns "Endpoints are not yet stable and may change without notice". Three because the errors are written for a model and the docs around them contradict each other. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/tempo#rev_1438 https://www.anchorterminal.com/tools/tempo#rev_1438 Sat, 03 Oct 2026 00:00:00 +0000 review Over 200 pages in llms.txt, a public OpenAPI, OpenRPC for JSON-RPC and one error envelope with a full code catalogue. It looks complete, and in two places it disagrees with itself. The rate-limits page gives anonymous callers 20 requests a minute per IP, and the API MCP page says 100. The AI guide lists four documentation tools on mcp.tempo.xyz, while the API reference describes data-domain tools on the same host. The versioning page adds that 'Endpoints are not yet stable and may change without notice'. The OpenAPI document went unread, refused by the research run's own rate limit, and no terms of service were found. Chain data such as token names and memos is attacker-controlled, and no prompt-injection guidance turned up. The data itself sits on a public ledger with keyless reads. Three, because an answer can be checked against the chain, and the docs can't be relied on to agree about how to ask. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/tempo#rev_1439 https://www.anchorterminal.com/tools/tempo#rev_1439 Sat, 03 Oct 2026 00:00:00 +0000 review The anonymous limit is 20 requests a minute per IP on the rate-limits page and 100 on the API MCP page, and the research run couldn't settle which. Keys get 100 a minute per scope. Clients read `RateLimit-*` headers, a 429 carries `Retry-After`, the docs ask for backoff with jitter, and over quota an anonymous endpoint answers 402 with an MPP challenge. No idempotency guidance for the fee-payer relay. The status page at status.tempo.xyz shows one incident in 90 days, the mainnet public RPC down on 28 September, with that component at 99.996% for 30 days. No SLA, and JSON-RPC is described as best-effort. The API versioning page says endpoints are not yet stable and may change without notice, and network upgrades have gone live with notice as short as three days. No latency published, and Anchor hasn't measured it. Three because the 429 handling is written down, the limit contradicts itself and nothing is guaranteed. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/tempo#rev_0777 https://www.anchorterminal.com/tools/tempo#rev_0777 Thu, 01 Oct 2026 00:00:00 +0000 review No human steps for a read or an MPP-paid call on the open endpoints, and one for a key. The docs say the public RPC and most read endpoints on api.tempo.xyz answer without a key within a per-IP limit, and accept an `Authorization` Payment credential instead, up front or after a 402 once over quota. No account, no card. The agent hands over a payment signed by its own wallet. Testnet funds come from a faucet, and the files don't say where mainnet funds come from. A person is needed for keys, by creating a project in the Tempo API Console, and for production fee sponsorship, which needs a payment method through Stripe checkout. The anonymous limit is 20 a minute in one place and 100 in another, and no price per paid request is listed. Five because the door is a 402 an agent can pay (MPP, not x402), and the CLI's dry run shows the cost first. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/tempo#rev_0778 https://www.anchorterminal.com/tools/tempo#rev_0778 Thu, 01 Oct 2026 00:00:00 +0000 review Mainnet has carried MPP settlement since 18 March 2026, and the node README still says the chain is undergoing audit with no active bug bounty. A security release, v1.13.1 on 20 August 2026, was announced in the public changelog. No security.txt, and no terms of service found for the API, console, CLI or MCP server. The API key design is careful. Project-scoped keys with named scopes such as `data:read`, rotation, revocation, optional IP allowlists, environment prefixes, sandbox keys that can't touch mainnet, and only a hash stored at rest. MPP payment credentials stay separate from keys. Payments are signed by the agent's own wallet with no approval step on Tempo's side, so spending control lives in that wallet and in the console's monthly spend and fee-sponsorship limits. Token names and memos are attacker-controlled, with no injection guidance. Three, because the keys are tight and the chain they sit on hasn't finished its audit. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/tempo https://www.anchorterminal.com/tools/tempo#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing A payments-first Layer 1 chain incubated by Stripe and Paradigm, live on mainnet since 2026-03-18.