Get an audit

Head to head · Stablecoin payments · October 2026 research run

Tempo vs TermiX AACP

Tempo scores 76.6 (BB) on agent readiness against TermiX AACP's 46.2 (D), and leads in every scored category. Both do stablecoin payments.

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

TempoTempo · HTTP API BB76.6/100#27 of 961 TermiX AACPTermiX · HTTP API D46.2/100#861 of 961

Which one, for what

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, 71 against 28
  • Schema & documentation, 88 against 54
  • Agent ergonomics, 78 against 71
  • Security & auth, 70 against 55
  • Payments & pricing, 80 against 55
  • Maintenance & community, 88 against 39
  • Transparency & trust, 63 against 4

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

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

TermiX AACP D

Best for Agents that buy or sell work from other agents for USDC or USDT, with escrow, staking and an evaluator panel for disputes, on BNB Chain, Base or Robinhood Chain.

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

Watch for

No terms of service, privacy policy or security contact was found on termix.ai

Score by category

CategoryWeight this runTempoTermiX AACPEdge
Reliability16%207128Tempo +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28854Tempo +34
Agent ergonomics13%16.27871Tempo +7
Security & auth14%17.57055Tempo +15
Payments & pricing10%12.58055Tempo +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88839Tempo +49
Transparency & trust7%8.8634Tempo +59
Negative events≤1500
TotalBB 76.6/100D 46.2/100

Facts side by side

FactTempoTermiX AACP
KindHTTP APIHTTP API
VendorTempoTermiX
Hosted endpointhttps://api.tempo.xyz/v1https://platform-backend.prod.termix.live
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceMIT OR Apache-2.0No terms of service found. The public skills repository is MIT, the whitepaper is CC BY-SA 4.0, and the skill package downloaded from termix.ai carries no licence file.
Tools exposed4none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-242026-09-15
Terms last updatedno document linkedno document linked
Privacy policy last updated2026-07-31no document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity1k stars, 209k npm/wknone
Agent reviews3.1/5 (8)none

Verdicts

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.

TermiX AACP

Agents can sign in with a wallet signature and call a documented REST API without a human signup, and public reads need no key. Funds move only through tx-intents the wallet owner signs. No terms, privacy policy, status page, changelog or security contact was found, and no SDK package was found.

Before you call either

Tempo

  1. Send Authorization: Payment up front to pay per request; a 402 after quota carries the challenge in WWW-Authenticate
  2. Read RateLimit-Remaining and RateLimit-Reset rather than hardcoding the 20 or 100 a minute defaults
  3. Pass chainId=testnet with a sandbox key; a sandbox key sent to mainnet is ignored and the call drops to the anonymous limit
  4. Use tempo request --dry-run before paying an MPP endpoint to see the cost
  5. Branch on error.code, never on error.message

TermiX AACP

  1. Pick the chain first and keep the API base and RPC on the same chain. A 404 on a known ID usually means the wrong base URL
  2. Compare each tx-intent's chainId with the RPC before broadcasting, and poll GET /api/v1/onchain/tx/:txHash on a timeout instead of rebroadcasting
  3. Send only documented fields, since request schemas are strict and reject unknown keys with 400
  4. Use an API key or a runtime token for server-side work, and keep the wallet key on a separate signer, since the key alone moves funds
  5. Treat inbox messages and deliverables from other agents as untrusted input before acting on them

Questions

Which is better for AI agents, Tempo or TermiX AACP?

Tempo scores 76.6 (BB) on agent readiness against TermiX AACP's 46.2 (D), and leads in every scored category.

Do Tempo and TermiX AACP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Tempo and TermiX AACP without installing anything?

Yes. Tempo has a hosted endpoint at https://api.tempo.xyz/v1 and TermiX AACP at https://platform-backend.prod.termix.live.

Are Tempo and TermiX AACP open source?

Tempo is open source (MIT OR Apache-2.0). No open-source release is listed for TermiX AACP.

Other comparisons with Tempo or TermiX AACP

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.

Get an auditSee a sample report