# Bitstamp API vs Uniswap Trading API (slim)

> Uniswap Trading scores 63.3 (B) to Bitstamp's 50.4 (D) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.md (~4,650 tokens) · this version ~2,330 tokens · JSON https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.json · canonical https://www.anchorterminal.com/compare/bitstamp-vs-uniswap
- 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-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Uniswap Trading API scores 63.3 (B) on agent readiness against Bitstamp API's 50.4 (D), and leads in 6 of 7 scored categories. Bitstamp API leads on reliability. Both do exchange market data.

- Bitstamp API: D 50.4, rank #948 of 1349 · https://www.anchorterminal.com/tools/bitstamp.min.md
- Uniswap Trading API: B 63.3, rank #470 of 1349 · https://www.anchorterminal.com/tools/uniswap.min.md
- Bitstamp API, good for An agent that needs a long-running regulated spot venue in the EU, UK and US with a sandbox and per-endpoint key permissions, and can do its own signing. Ahead on Reliability, 63 against 42.
- Uniswap Trading API, good for An agent swapping or bridging tokens from its own wallet on 21 EVM chains, or managing liquidity positions, with routing done for it. Ahead on Schema & documentation, 90 against 51; Agent ergonomics, 72 against 58; Payments & pricing, 40 against 20; Maintenance & community, 88 against 28. Also Free to start without a card.

| Category | Bitstamp API | Uniswap Trading API |
| --- | --- | --- |
| Reliability (16%) | 63 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 51 | 90 |
| Agent ergonomics (13%) | 58 | 72 |
| Security & auth (14%) | 60 | 63 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 28 | 88 |
| Transparency & trust (7%) | 53 | 55 |

| Fact (where they differ) | Bitstamp API | Uniswap Trading API |
| --- | --- | --- |
| Vendor | Bitstamp Ltd. | Uniswap Labs |
| Pricing | Pay per use | Free |
| Licence | Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load | The Trading API is a proprietary hosted service under Uniswap Labs' API Terms of Use, which we couldn't read; the SDKs and the uniswap-ai skills are MIT. Swaps execute on the open-source Uniswap protocol contracts on chain |
| Tools exposed | none | 0 |
| llms.txt | no | yes |
| Last release | 2026-08-28 | 2026-10-22 |
| Privacy policy last updated | couldn't be read | no document linked |
| Popularity | none | 236 stars, 154k npm/wk |

Why the edge:
- Maintenance & community, Uniswap Trading API +60: Bitstamp API 28 (Read as a closed service. The last dated API change is 28 August 2026, 67 days before the check (20). Only one dated entry in the last 90 days, after 1 July and 12 June (0). No public repository or issue tracker, support pages did not load and support.bitstamp.net did not resolve; a changelog exists (8 of 25). No official SDKs and no MCP registry presence of Bitstamp's own (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28.); Uniswap Trading API 88 (Read as a closed hosted service. The newest changelog notice is dated 22 October 2026 (30). Notices of 20 August, 21 September and 22 October 2026, three in 90 days (20). A help form for developer support that says it won't debug integrators' code, and uniswap-ai with 6 open issues and a push on 26 October (14 of 25). Official TypeScript SDKs current (@uniswap/v4-sdk 2.4.4 with provenance) and the uniswap-ai skills, though no client for the API itself; no MCP registry entry (15). Trusted publishing with provenance on npm, CI and lint hooks on uniswap-ai (9 of 10). Total 88.)
- Schema & documentation, Uniswap Trading API +39: Bitstamp API 51 (No OpenAPI or other machine-readable contract was found on the API page or elsewhere (0). No llms.txt or Markdown docs (0). The single documentation page describes each endpoint's purpose and parameters, with notes such as the 10-second cache on open orders and the Travel Rule fields, but not when to use one endpoint over another (14 of 20). Parameters are typed with enumerations (margin mode CROSS or ISOLATED, margin multiplier 1 to 25, order types) and required fields marked (11 of 15). Signing examples in Python, Java and C++, and error families with numbered codes and explanations (13 of 15). Version v2 in the path and header, a dated changelog from 7 April 2023 to 28 August 2026, and a 410.001 code for deprecated endpoints, with no stated notice period (13 of 15). 0 + 0 + 14 + 11 + 13 + 13 = 51.); Uniswap Trading API 90 (OpenAPI 3.0 file (Token Trading 1.0.0) for the Trading and LP APIs, about 33 paths with `x-internal` markers on the margin and 4337 operations (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation summaries are one line, but the guides say which routing types go to `/swap`, `/order` and `/plan`, when UniswapX quotes are returned and when a 404 means change the request (14 of 20). Enums for routing types, urgency and position statuses, required fields and bounded integers such as `limit` 1 to 20 (12 of 15). Examples on every guide page and error schemas for 400, 401, 404 and 429 with a stable `errorCode` enum and per-code retry advice (14 of 15). A /v1 path, a changelog with posted and effective dates and a 30-day minimum sunset policy (15). Total 90.)
- Reliability, Bitstamp API +21: Bitstamp API 63 (Read with the hosted lines on the HTTP API v2 at www.bitstamp.net/api/v2/. status.bitstamp.net is a Statuspage site with component history (20). Its feed for 5 August to 3 November 2026 has 17 entries, among them withdrawals failing on 14 networks for about 3 hours on 21 August, database maintenance with login failures and intermittent trading interruptions for about 1 hour 44 minutes on 23 September, a 39-minute halt of all markets on 5 August, and delistings and single-asset suspensions. One major (10). Rate limits with numbers, 400 a second and 10,000 per 10 minutes (15). Limit errors are named (400.002, 400.067, 400.068) but there is no Retry-After or backoff guidance, duplicate client order ids are allowed, and the only retry guidance is to check the order after a 500.016 timeout (8 of 15). No SLA found (0). Generally available (10). 20 + 10 + 15 + 8 + 0 + 10 = 63.); Uniswap Trading API 42 (Read with the hosted lines on the Trading API. status.uniswap.org redirects to the swap app and the docs link no status page (0). No readable history (5). Rate limit documented as 6 requests a second per key (15). The errors page says to pause all requests from the key on 429, retry 500 and 503 with backoff and refresh quotes after 30 seconds; swaps are signed transactions, so idempotency rests on the chain nonce (12 of 15). No SLA (0). The API is generally available; Guidestar routing is a beta notice (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.)
- Payments & pricing, Uniswap Trading API +20: Bitstamp API 20 (No machine payment protocol (0). The fee schedule page loaded empty, the API's fee endpoints need a key, and no rate could be read, so fees are scored as not published (0, unchecked). The API is free, public endpoints need no key and the sandbox needs no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 0 + 20 + 0 = 20.); Uniswap Trading API 40 (No machine payment protocol on the API's endpoints; the `pay-with-any-token` skill lets an agent pay other services' 402 challenges by swapping, which earns nothing here (0). The API is free, stated in the FAQ and the 16 April 2026 post, and integrator fees are capped at 500 bips (20). No card and no plan (20). A person creates an account in the dashboard to get a key (0). Total 40.)
- Agent ergonomics, Uniswap Trading API +14: Bitstamp API 58 (Graded on the REST API. Order book grouping and transaction time windows size responses, but there is no field selection and no MCP surface (15 of 25). Offset, limit, since and sort on transaction history, `until_id` windows on order-data replay (14 of 20). `response_code` and `response_explanation` name the failure, such as 400.009 insufficient balance, 403.004 trading blocked and 500.025 insufficient liquidity (16 of 20). No idempotency, since `client_order_id` duplicates are allowed since November 2023 and the docs say only to check the order id after a timeout; the kill switch limits damage (8 of 20). Few required parameters, but no official SDK in any language (5 of 15). 15 + 14 + 16 + 8 + 5 = 58.); Uniswap Trading API 72 (An API, read for response sizing. Quotes and calldata are compact and `/tokens` takes a limit; the quote can carry the swap calldata to save a call (20 of 25). `GET /orders` and `GET /swaps` poll status by id, `/swappable_tokens` and `/tokens` filter by chain and sort, with little pagination elsewhere (12 of 20). Stable `errorCode` values with a `detail` string and a `requestId`, and the docs say which codes to retry (18 of 20). No idempotency key; a swap is a signed transaction whose nonce prevents a double spend, and the docs warn about nonce collisions with pending transactions (12 of 20). Few required fields on `/quote`, defaults for slippage and urgency, but no official client library for the API and signing needs ethers.js, viem or web3.js (10 of 15). Total 72.)