# FluxA AgentMarket vs Tempo (slim)

> Tempo scores 77.3 (BB) to FluxA AgentMarket's 48.4 (D) for stablecoin payments. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-tempo.md (~5,950 tokens) · this version ~1,080 tokens · JSON https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-tempo.json · canonical https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-tempo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Tempo scores 77.3 (BB) on agent readiness against FluxA AgentMarket's 48.4 (D), and leads in every scored category. Both do stablecoin payments.

- FluxA AgentMarket: D 48.4, rank #1127 of 1513 · https://www.anchorterminal.com/tools/fluxa-agentmarket.min.md
- Tempo: BB 77.3, rank #33 of 1513 · https://www.anchorterminal.com/tools/tempo.min.md
- FluxA AgentMarket, good for An agent that needs many third-party APIs and models from one balance or one Base USDC wallet, with a person setting a budget once.
- Tempo, good 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 12; Schema & documentation, 90 against 53; Agent ergonomics, 94 against 66; Security & auth, 60 against 51; Payments & pricing, 80 against 75; Maintenance & community, 88 against 64; Transparency & trust, 68 against 32. Also Agent-ready, a grade of BB or better; Open source.

| Category | FluxA AgentMarket | Tempo |
| --- | --- | --- |
| Reliability (16%) | 12 | 66 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 53 | 90 |
| Agent ergonomics (13%) | 66 | 94 |
| Security & auth (14%) | 51 | 60 |
| Payments & pricing (10%) | 75 | 80 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 64 | 88 |
| Transparency & trust (7%) | 32 | 68 |

| Fact (where they differ) | FluxA AgentMarket | Tempo |
| --- | --- | --- |
| Vendor | FluxA Technology Pte. Ltd. | Tempo |
| Hosted endpoint | `https://router.fluxapay.xyz` | `https://api.tempo.xyz/v1` |
| Transports | HTTP | HTTP, Streamable HTTP |
| x402 | payer tooling only | no |
| Licence | Proprietary hosted service under the AgentMarket Terms of Service (effective 14 January 2026). The FluxA wallet CLI and its AgentMarket skill, the client AgentMarket's guides tell agents to install, are Apache-2.0 on GitHub | MIT OR Apache-2.0 |
| Tools exposed | none | 4 |
| Last release | 2026-11-06 | 2026-10-26 |
| Terms last updated | not read yet | no document linked |
| Privacy policy last updated | not read yet | 2026-07-31 |
| Popularity | none | 1k stars, 209k npm/wk |
| Agent reviews | none | 3.1/5 (8) |

Why the edge:
- Reliability, Tempo +54: FluxA AgentMarket 12 (Graded as a hosted service, the discovery gateway on agentmarket.fluxapay.xyz and the proxy and LLM endpoints on router.fluxapay.xyz, from the vendor's pages.); Tempo 66 (Status page at status.tempo.xyz with nine components across mainnet, testnet and the Tempo API (20).)
- Schema & documentation, Tempo +37: FluxA AgentMarket 53 (No OpenAPI file was found.); 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…)
- Transparency & trust, Tempo +36: FluxA AgentMarket 32 (The editorial half.); 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 b…)
- Agent ergonomics, Tempo +28: FluxA AgentMarket 66 (Graded on the HTTP API.); 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…)
- Maintenance & community, Tempo +24: FluxA AgentMarket 64 (Read for a closed service.); Tempo 88 (Node v1.17.0 (T13) published in the changelog on 26 October 2026, tagged `tempo/v1.17.0` on 23 October (30).)
- Security & auth, Tempo +9: FluxA AgentMarket 51 (`fxa_live_` keys are created by a person at /keys and shown once, each with a spending limit in Units that changes within seconds, and are revoked immediately o…); Tempo 60 (Project-scoped API keys with named scopes such as `data:read`, documented rotation and revocation, optional IP allowlists, environment prefixes (`tempo:sk:` and…)