{ "data": { "a": { "slug": "bitstamp", "name": "Bitstamp API", "vendor": "Bitstamp Ltd.", "vendorUrl": "https://www.bitstamp.net", "kind": "http-api", "category": "crypto-exchanges", "summary": "Bitstamp's HTTP API v2 for spot and derivatives trading, balances, deposits and withdrawals, with WebSocket and FIX feeds and a sandbox at sandbox.bitstamp.net. Bitstamp is a Robinhood company since June 2025.", "url": "https://www.anchorterminal.com/tools/bitstamp", "markdownUrl": "https://www.anchorterminal.com/tools/bitstamp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitstamp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitstamp.json", "dns": "bitstamp.grade.anchorterminal.com", "license": "Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API key and secret made in the Bitstamp account after a browser signup, sent as `X-Auth: BITSTAMP {key}` with an HMAC-SHA256 `X-Auth-Signature` over the verb, host, path, query, nonce, timestamp and body, a 36-character single-use nonce and a timestamp within 150 seconds. Keys carry per-endpoint permissions (error API0003 names a missing permission) and an IP allow-list (API0002), and `X-Auth-Subaccount-Id` targets a sub-account. `POST /api/v2/revoke_all_api_keys/` is a kill switch for every key. Responses carry an `X-Server-Auth-Signature` to verify (https://www.bitstamp.net/api/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API itself costs nothing. Trading fees are maker and taker by 30-day volume per the API's fees endpoints, but the fee schedule page at bitstamp.net/fee-schedule/ draws its table by script and loaded empty for our reader, so the rates are unchecked. Commercial use of exchange data needs a Data License Agreement through partners@bitstamp.net. The sandbox at sandbox.bitstamp.net needs no money (https://www.bitstamp.net/api/, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation (checked 2026-11-03). Fees are taken from the account; onboarding is a browser signup.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.bitstamp.net/api/", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "official", "hosted", "api-key", "sandbox", "status-page", "usage-priced", "eu", "uk" ], "lastRelease": "2026-08-28", "graded": true, "anchor": { "graded": true, "score": 50.4, "grade": "D", "agentReady": false, "rank": 1002, "ranked": true, "rankOf": 1349, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 28, "payments": 20, "reliability": 63, "schema": 51, "security": 60, "transparency": 53 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be read.", "bestFor": "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.", "strengths": [ "Rate limits with numbers (400 requests a second, 10,000 per 10 minutes) and named error codes for client and market limits", "Keys carry per-endpoint permissions and an IP allow-list, and one call revokes every key on the account", "A sandbox at sandbox.bitstamp.net with the same v2 paths, plus order-data endpoints to recover gaps after a dropped WebSocket", "A dated API changelog from 2023 to 28 August 2026 and a Statuspage feed with per-market incidents", "Signed responses (`X-Server-Auth-Signature`) let a client verify what the server returned" ], "weaknesses": [ "No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data", "Duplicate client order ids are allowed since November 2023, so a retried order can execute twice", "The fee schedule, terms of use, privacy policy, about page and FAQ load empty without a browser, so fees, retention and the bot clauses are unchecked", "A 3-hour withdrawal failure across 14 networks on 21 August 2026 and a 39-minute halt of all markets on 5 August 2026", "security.txt expired on 12 July 2026, and no SLA was found" ], "agentNotes": [ "Mint a key with only the endpoint permissions the task needs and an IP allow-list; keep `revoke_all_api_keys` in reach as a kill switch", "Treat `client_order_id` as a label, not a guard. On a timeout (500.016) fetch the order by client id before resending, because duplicates are accepted", "Use a fresh 36-character nonce and a timestamp within 150 seconds of server time on every request, or expect API0004 and API0017", "Stay under 400 requests a second and 10,000 per 10 minutes; 400.002 and 400.067 mean back off, and open-orders answers are cached for 10 seconds", "Start on sandbox.bitstamp.net with the same paths, and read the fee schedule in a browser before quoting costs, since it is unreadable to a plain fetch" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.4 } ], "editorialScores": { "ergonomics": 58, "maintenance": 28, "payments": 20, "reliability": 63, "schema": 51, "security": 60, "transparency": 16 }, "provenanceScore": 90, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://www.bitstamp.net/api/v2/ticker/btcusd/" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/bitstamp" }, "area": "payments", "provenance": { "legalEntity": "Bitstamp Ltd.", "domain": "bitstamp.net", "domainRegistered": "2011-07-04", "endpointOnVendorDomain": true, "terms": "https://www.bitstamp.net/terms-of-use/", "privacy": "https://www.bitstamp.net/privacy-policy/", "statusPage": "https://status.bitstamp.net", "changelog": "https://www.bitstamp.net/api/", "securityTxt": "expired", "checked": "2026-11-03", "notes": [ "Bitstamp Ltd. is named in Robinhood's newsroom post of 2 June 2025 on closing the acquisition; the terms of use and privacy policy pages loaded empty for our reader, so the entities they name are unconfirmed.", "RDAP gives bitstamp.net a registration date of 4 July 2011.", "https://www.bitstamp.net/.well-known/security.txt names HackerOne's Robinhood programme as Contact and Policy and expired on 12 July 2026.", "www.bitstamp.net/robots.txt allows /api/ itself and disallows /api/*, /account/, /trade/ and others; only /api/ was read under it. status.bitstamp.net disallows /api/ and /embed/, so the history feed was read. support.bitstamp.net did not resolve.", "The API changelog is a section of the API documentation page; there is no separate changelog URL." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bitstamp.json", "live": { "slug": "bitstamp", "vendorStatus": { "page": "https://status.bitstamp.net", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:04:41.953848408Z" }, "securityTxt": { "url": "https://bitstamp.net/.well-known/security.txt", "state": "expired", "expires": "2026-07-12T11:59:00.000Z", "checkedAt": "2026-11-04T15:53:31.314157297Z" }, "updatedAt": "2026-11-04T20:04:41.953848408Z" } }, "answer": "Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories. Bitstamp API leads on reliability.", "b": { "slug": "coinbase-advanced-trade", "name": "Coinbase Advanced Trade API", "vendor": "Coinbase, Inc.", "vendorUrl": "https://docs.cdp.coinbase.com/advanced-trade/docs/welcome", "kind": "http-api", "category": "crypto-exchanges", "summary": "Coinbase's Advanced Trade API is the trading API of a Coinbase account, with REST, WebSocket feeds and a static sandbox for spot, US futures and, since October 2026, perpetuals on a Deribit-based gateway, authenticated by CDP API keys.", "url": "https://www.anchorterminal.com/tools/coinbase-advanced-trade", "markdownUrl": "https://www.anchorterminal.com/tools/coinbase-advanced-trade.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/coinbase-advanced-trade.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/coinbase-advanced-trade.json", "dns": "coinbase-advanced-trade.grade.anchorterminal.com", "repo": "https://github.com/coinbase/coinbase-advanced-py", "license": "Proprietary hosted service under the Coinbase User Agreement, which answered a bot check and wasn't read. The official Python SDK coinbase-advanced-py is on GitHub", "transports": [], "packages": [ { "registry": "pypi", "name": "coinbase-advanced-py" } ], "auth": "mixed", "authNotes": "CDP secret API key made in the CDP portal, with view, trade and transfer permissions, a portfolio restriction and an optional IP allowlist. Each request carries a JWT signed with ECDSA (ES256) that expires after 2 minutes, so a new token is minted per call. Ed25519 keys are not accepted by Coinbase App APIs. The OpenAPI spec also lists OAuth2 with wallet:* scopes for acting on other people's accounts. Keys are regenerated or disabled in the portal. Six public market endpoints need no key (https://docs.cdp.coinbase.com/coinbase-app/authentication-authorization/api-key-authentication.md, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Trades carry Advanced Trade maker and taker fees by 30-day volume tier; the fee page at coinbase.com/advanced-fees and help.coinbase.com both answered our reader with 403 on 3 November 2026, so the lowest tier's rates are unread. The sandbox and the public market endpoints need no account.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Advanced Trade endpoints in the OpenAPI spec or docs (checked 2026-11-03). Coinbase's account MCP server, listed as coinbase-mcp, pays x402 resources as a buyer; that is a separate surface.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.cdp.coinbase.com/advanced-trade/docs/welcome", "llmsTxt": "https://docs.cdp.coinbase.com/llms.txt", "openapi": "https://docs.cdp.coinbase.com/api-reference/advanced-trade-api/rest-api/advanced-trade-spec.yaml", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "official", "closed-source", "api-key", "oauth", "openapi", "llms-txt", "sandbox", "status-page", "python", "usage-priced", "no-card", "bug-bounty" ], "lastRelease": "2026-10-01", "graded": true, "anchor": { "graded": true, "score": 61.7, "grade": "C", "agentReady": false, "rank": 493, "ranked": true, "rankOf": 1349, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 57, "payments": 20, "reliability": 58, "schema": 80, "security": 68, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Advanced Trade has a public OpenAPI spec, keys limited to view, trade or transfer and to one portfolio, and a keyless static sandbox. No REST rate limit is published, the fee schedule, user agreement and country list sit behind a bot check, and an agent that wants an MCP route uses the separate coinbase-mcp listing.", "bestFor": "An agent trading a person's or a treasury's Coinbase account with its own key, where the person wants sandbox tests and portfolio scoping.", "strengths": [ "Public OpenAPI 3.1 and AsyncAPI specs with typed enums, plus llms.txt and a Markdown twin of every docs page", "CDP keys carry view, trade and transfer permissions, a portfolio restriction and an IP allowlist, and signed JWTs expire after 2 minutes", "Keyless sandbox with static responses and header-driven error simulation for accounts and orders", "Six public market data endpoints need no key, and most WebSocket channels are open without authentication", "Dated retirement of INTX endpoints with a read-only grace period, announced in the docs" ], "weaknesses": [ "No REST rate limit numbers found; the old rate-limits page answers 404 and only the WebSocket limit of 8 per second per IP is published", "The fee schedule, user agreement, privacy policy and supported-countries pages answered a bot check and were not read", "No FIX connectivity is documented for Advanced Trade", "The OpenAPI spec documents only a default error response, with no 4xx or 429 shapes", "security.txt expired on 1 June 2024 and no status component exists for the Global Derivatives gateway" ], "agentNotes": [ "Mint a fresh ES256 JWT for every request; tokens expire after 2 minutes and Ed25519 keys are rejected", "Send a unique client_order_id on every order and reuse it on retry so a dropped connection does not place a second order", "Develop against api-sandbox.coinbase.com first; its responses are static, so do not read prices or fills from it", "Use a key with view only, or trade without transfer, and restrict it to a portfolio funded for the agent", "For perpetuals call the Global Derivatives JSON-RPC gateway at drb.coinbase.com; the /intx/* endpoints are retired" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.7 } ], "editorialScores": { "ergonomics": 73, "maintenance": 57, "payments": 20, "reliability": 58, "schema": 80, "security": 68, "transparency": 42 }, "provenanceScore": 92, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install coinbase-advanced-py", "http": "curl https://api.coinbase.com/api/v3/brokerage/market/products/BTC-USD/ticker?limit=1" }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/coinbase-advanced-trade" }, "sameCompany": [ "coinbase-mcp" ], "area": "payments", "provenance": { "legalEntity": "Coinbase, Inc.", "domain": "coinbase.com", "domainRegistered": "2011-07-02", "endpointOnVendorDomain": true, "terms": "https://www.coinbase.com/legal/user_agreement", "privacy": "https://www.coinbase.com/legal/privacy", "statusPage": "https://status.coinbase.com", "changelog": "https://docs.cdp.coinbase.com/get-started/changelog", "securityTxt": "expired", "checked": "2026-11-03", "notes": [ "The user agreement, privacy policy, fee schedule and help centre answered a bot check or 403 on 3 November 2026. The terms and privacy URLs are Coinbase's standard ones; Coinbase, Inc. is the entity named in the coinbase-cdp-agentkit and coinbase-mcp listings.", "Domain registration date per the RDAP read of 24 October 2026 for coinbase-mcp, not re-read.", "https://www.coinbase.com/.well-known/security.txt points to HackerOne and expired on 1 June 2024, re-read 3 November 2026.", "docs.cdp.coinbase.com/robots.txt disallows only /cdn-cgi/ and /_next/. help.coinbase.com answered 403 to robots.txt, so nothing on that host was requested further.", "The CDP changelog's newest entry is 23 October 2026; its only trading entries since August concern the agents MCP server (17 and 21 August)." ], "score": 92 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/coinbase-advanced-trade.json", "live": { "slug": "coinbase-advanced-trade", "vendorStatus": { "page": "https://status.coinbase.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-04T20:04:59.232209364Z" }, "versions": [ { "registry": "github", "name": "coinbase/coinbase-advanced-py", "version": "v1.8.4", "released": "2026-06-19", "seenAt": "2026-11-04T20:07:55.498790392Z" }, { "registry": "pypi", "name": "coinbase-advanced-py", "version": "1.8.4", "released": "2026-06-19", "seenAt": "2026-11-04T20:07:55.303074368Z" } ], "githubStars": 364, "pypiWeekly": 31348, "securityTxt": { "url": "https://coinbase.com/.well-known/security.txt", "state": "valid", "expires": "2024-06-01T00:00:00z", "checkedAt": "2026-11-04T15:52:53.816413711Z" }, "updatedAt": "2026-11-04T20:07:55.498790392Z" } }, "edges": [ { "by": 29, "category": "schema", "leads": "coinbase-advanced-trade", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "Public OpenAPI 3.1 spec (45 paths, 51 operations) and an AsyncAPI document (25). llms.txt and a Markdown twin of every docs page (10). Every operation has a summary and description, some one line, several with multi-sentence guidance for equities (14 of 20). Enums on product_type, granularity, order_status, time_in_forces, order_types, order_side and sort_by, with defaults (13 of 15). Examples in the docs and the sandbox's simulated errors, but the spec documents only a default error referencing grpc.gateway.runtime.Error, with no 4xx or 429 shapes (8 of 15). Paths carry /api/v3, the CDP changelog is dated, and the INTX retirement was announced with a date, but the spec's info.version is 0.1 and the October gateway change has no changelog entry (10 of 15). 25 + 10 + 14 + 13 + 8 + 10 = 80." }, "scores": { "a": 51, "b": 80 } }, { "by": 29, "category": "maintenance", "leads": "coinbase-advanced-trade", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed hosted service. The last change to the API itself is the Global Derivatives gateway and INTX retirement of 1 October 2026, 33 days before this check; the Python SDK's v2.0.0rc1 is from 30 September (20 of 30). Dated changes in 90 days are the 1 October migration and the agents entries of 17 and 21 August, which run through Advanced Trade (12 of 20). A public changelog and a CDP Discord; SDK issues not read (8 of 15). Official Python SDK current, the rest samples (12 of 15). SDK CI not read (5 of 10). 20 + 12 + 8 + 12 + 5 = 57." }, "scores": { "a": 28, "b": 57 } }, { "by": 15, "category": "ergonomics", "leads": "coinbase-advanced-trade", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Product lists filter by product_type and product_ids with limit and offset, candles take a granularity, but fields cannot be selected and the docs warn that product lists run to hundreds of entries (15 of 25). Cursor pagination with limit on orders and fills, filters by status, product and time (16 of 20). Error codes such as INSUFFICIENT_FUND, ORDER_NOT_FOUND and PERMISSION_DENIED are documented and can be simulated in the sandbox, though the spec gives no shapes (14 of 20). client_order_id on every order; no idempotency key on other writes (16 of 20). Few required fields, an official Python SDK and sample SDKs in three languages, but each request needs a freshly signed JWT (12 of 15). 15 + 16 + 14 + 16 + 12 = 73." }, "scores": { "a": 58, "b": 73 } }, { "by": 14, "category": "transparency", "leads": "coinbase-advanced-trade", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed service whose terms of use loaded empty for our reader, so the licence and clauses are unknown (8 of 30). The privacy policy loaded empty, so retention and data handling are unchecked (0 of 30). A 410.001 code marks deprecated endpoints and the changelog records replacements such as `trading-pairs-info` by `markets`, with no notice period stated (8 of 20). Subprocessors and data locations are in the unread privacy policy (0). 8 + 0 + 8 + 0 = 16.", "b": "The editorial half. A closed service whose user agreement answered a bot check; the OpenAPI spec is public and the Python SDK is open on GitHub (12 of 30). Privacy facts per the coinbase-cdp-agentkit check of 1 October 2026 (Coinbase, Inc., processing countries, retention tied to need without numbers), not re-read (10 of 30). INTX endpoints retired on 1 October 2026 with a dated notice and a read-only grace period (12 of 20). Processing countries and provider categories per the same earlier check, no subprocessor list (8 of 20). 12 + 10 + 12 + 8 = 42." }, "scores": { "a": 53, "b": 67 } }, { "by": 8, "category": "security", "leads": "coinbase-advanced-trade", "name": "Security \u0026 auth", "reasons": { "a": "Revocable HMAC-SHA256 keys with per-endpoint permissions, an IP allow-list, single-use nonces, a timestamp window, sub-account scoping and a one-call kill switch for every key; no key expiry found (24 of 30). Permissions are chosen per endpoint and withdrawals can need Travel Rule address verification, but whether a withdrawal address allow-list exists sits in the unread account settings and no confirmation step is documented for API withdrawals (14 of 20). The API returns exchange data, not third-party text (10). No per-key audit log found; the account's transaction history is the record (4 of 15). security.txt names HackerOne's Robinhood programme but expired on 12 July 2026; no certification page was readable (8 of 20). 24 + 14 + 10 + 4 + 8 = 60.", "b": "CDP keys with view, trade and transfer permissions, a portfolio restriction, an optional IP allowlist, revocation in the portal, ES256 JWTs that expire after 2 minutes, and OAuth2 with wallet:* scopes for other people's accounts; no key expiry (28 of 30). View-only keys and portfolio scoping limit an agent, and transfer is a separate permission, but no withdrawal address allow-list for API keys and no confirmation step were found (14 of 20). The API returns no untrusted content (10). key_permissions reports a key's scope and account activity shows in the app, but no per-call log was found (6 of 15). HackerOne bug bounty named in a security.txt that expired on 1 June 2024; certifications unread behind a bot check (10 of 20). 28 + 14 + 10 + 6 + 10 = 68." }, "scores": { "a": 60, "b": 68 } }, { "by": 5, "category": "reliability", "leads": "bitstamp", "name": "Reliability", "reasons": { "a": "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.", "b": "Read with the hosted lines. status.coinbase.com is a Statuspage site with Coinbase Advanced Trade, API, US Derivatives and International Derivatives components (20). The incidents feed we could read runs from 16 September to 3 November 2026. In it Advanced Trade was degraded for 25 minutes on 21 September, the website had a 3-minute major on 14 October, converts were down 1 hour 4 minutes on 26 October, and no incident named the API; 5 August to 15 September was beyond the feed, so minor only for the seven weeks read (15 of 30). No REST rate limit with numbers was found; the older rate-limits page answers 404 and llms.txt lists none, while the WebSocket page gives 8 connections and 8 unauthenticated messages per second per IP (5 of 15). Orders take a client_order_id, but no 429 or Retry-After guidance was found for Advanced Trade (8 of 15). No SLA (0). REST and WebSocket are generally available; the Global Derivatives gateway is a month old and not marked beta (10). 20 + 15 + 5 + 8 + 0 + 10 = 58." }, "scores": { "a": 63, "b": 58 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Bitstamp Ltd.", "b": "Coinbase, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load", "b": "Proprietary hosted service under the Coinbase User Agreement, which answered a bot check and wasn't read. The official Python SDK coinbase-advanced-py is on GitHub", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-28", "b": "2026-10-01", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-05-27", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories. Bitstamp API leads on reliability.", "question": "Which is better for AI agents, Bitstamp API or Coinbase Advanced Trade API?" }, { "answer": "Bitstamp API needs an API key. Coinbase Advanced Trade API takes an API key or an OAuth sign-in.", "question": "Do Bitstamp API and Coinbase Advanced Trade API need an API key?" }, { "answer": "No hosted endpoint is listed for Bitstamp API. No hosted endpoint is listed for Coinbase Advanced Trade API.", "question": "Can an agent call Bitstamp API and Coinbase Advanced Trade API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 63 against 58" ], "also": null, "goodFor": "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.", "slug": "bitstamp", "watchFor": "No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data" }, { "aheadOn": [ "Schema \u0026 documentation, 80 against 51", "Agent ergonomics, 73 against 58", "Security \u0026 auth, 68 against 60", "Maintenance \u0026 community, 57 against 28", "Transparency \u0026 trust, 67 against 53" ], "also": [ "Free to start without a card" ], "goodFor": "An agent trading a person's or a treasury's Coinbase account with its own key, where the person wants sandbox tests and portfolio scoping.", "slug": "coinbase-advanced-trade", "watchFor": "No REST rate limit numbers found; the old rate-limits page answers 404 and only the WebSocket limit of 8 per second per IP is published" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.json", "title": "Bitfinex API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.json", "title": "Bitfinex API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-bitstamp.json", "title": "Bitget vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bitget-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade.json", "title": "Bitget vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.json", "title": "Bithumb Open API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.json", "title": "Bithumb Open API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-bybit.json", "title": "Bitstamp API vs Bybit", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.json", "title": "Bitstamp API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.json", "title": "Bitstamp API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-deribit.json", "title": "Bitstamp API vs Deribit", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-dydx.json", "title": "Bitstamp API vs dYdX", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.json", "title": "Bitstamp API vs Gate", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.json", "title": "Bitstamp API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-htx.json", "title": "Bitstamp API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.json", "title": "Bitstamp API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken.json", "title": "Bitstamp API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.json", "title": "Bitstamp API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-mexc.json", "title": "Bitstamp API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-okx.json", "title": "Bitstamp API vs OKX API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.json", "title": "Bitstamp API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit.json", "title": "Bitstamp API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.json", "title": "Bybit vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitstamp.json", "title": "Binance API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.json", "title": "Binance API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp.json", "title": "Coinbase Advanced Trade API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange.json", "title": "Coinbase Advanced Trade API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit.json", "title": "Coinbase Advanced Trade API vs Deribit", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gate-io.json", "title": "Coinbase Advanced Trade API vs Gate", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange.json", "title": "Coinbase Advanced Trade API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.json", "title": "Coinbase Advanced Trade API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid.json", "title": "Coinbase Advanced Trade API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken.json", "title": "Coinbase Advanced Trade API vs Kraken API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin.json", "title": "Coinbase Advanced Trade API vs KuCoin", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc.json", "title": "Coinbase Advanced Trade API vs MEXC API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx.json", "title": "Coinbase Advanced Trade API vs OKX API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap.json", "title": "Coinbase Advanced Trade API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.json", "title": "Coinbase Advanced Trade API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx.json", "title": "Coinbase Advanced Trade API vs dYdX", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx" } ], "panel": null, "scores": [ { "bitstamp": 63, "by": 5, "coinbase-advanced-trade": 58, "edge": "bitstamp", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bitstamp": 51, "by": 29, "coinbase-advanced-trade": 80, "edge": "coinbase-advanced-trade", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bitstamp": 58, "by": 15, "coinbase-advanced-trade": 73, "edge": "coinbase-advanced-trade", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bitstamp": 60, "by": 8, "coinbase-advanced-trade": 68, "edge": "coinbase-advanced-trade", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bitstamp": 20, "by": 0, "coinbase-advanced-trade": 20, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bitstamp": 28, "by": 29, "coinbase-advanced-trade": 57, "edge": "coinbase-advanced-trade", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bitstamp": 53, "by": 14, "coinbase-advanced-trade": 67, "edge": "coinbase-advanced-trade", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories. Bitstamp API leads on reliability. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "bitstamp": "Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be read.", "coinbase-advanced-trade": "Advanced Trade has a public OpenAPI spec, keys limited to view, trade or transfer and to one portfolio, and a keyless static sandbox. No REST rate limit is published, the fee schedule, user agreement and country list sit behind a bot check, and an agent that wants an MCP route uses the separate coinbase-mcp listing." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade", "json": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.min.md" }, "markdown": "Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories. Bitstamp API leads on reliability. Both do exchange market data.\n\n- Bitstamp API: grade D, 50.4/100, rank #1002 of 1349. Markdown https://www.anchorterminal.com/tools/bitstamp.md · JSON https://www.anchorterminal.com/api/v1/tools/bitstamp.json\n- Coinbase Advanced Trade API: grade C, 61.7/100, rank #493 of 1349. Markdown https://www.anchorterminal.com/tools/coinbase-advanced-trade.md · JSON https://www.anchorterminal.com/api/v1/tools/coinbase-advanced-trade.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Which one, for what\n\n### Bitstamp API (D)\n\nGood 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.\n\nAhead on:\n- Reliability, 63 against 58\n\nWatch for: No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data\n\n### Coinbase Advanced Trade API (C)\n\nGood for: An agent trading a person's or a treasury's Coinbase account with its own key, where the person wants sandbox tests and portfolio scoping.\n\nAhead on:\n- Schema \u0026 documentation, 80 against 51\n- Agent ergonomics, 73 against 58\n- Security \u0026 auth, 68 against 60\n- Maintenance \u0026 community, 57 against 28\n- Transparency \u0026 trust, 67 against 53\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No REST rate limit numbers found; the old rate-limits page answers 404 and only the WebSocket limit of 8 per second per IP is published\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Coinbase Advanced Trade API +29\n\n- 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.\n- Coinbase Advanced Trade API (80): Public OpenAPI 3.1 spec (45 paths, 51 operations) and an AsyncAPI document (25). llms.txt and a Markdown twin of every docs page (10). Every operation has a summary and description, some one line, several with multi-sentence guidance for equities (14 of 20). Enums on product_type, granularity, order_status, time_in_forces, order_types, order_side and sort_by, with defaults (13 of 15). Examples in the docs and the sandbox's simulated errors, but the spec documents only a default error referencing grpc.gateway.runtime.Error, with no 4xx or 429 shapes (8 of 15). Paths carry /api/v3, the CDP changelog is dated, and the INTX retirement was announced with a date, but the spec's info.version is 0.1 and the October gateway change has no changelog entry (10 of 15). 25 + 10 + 14 + 13 + 8 + 10 = 80.\n\n### Maintenance \u0026 community: Coinbase Advanced Trade API +29\n\n- 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.\n- Coinbase Advanced Trade API (57): Read as a closed hosted service. The last change to the API itself is the Global Derivatives gateway and INTX retirement of 1 October 2026, 33 days before this check; the Python SDK's v2.0.0rc1 is from 30 September (20 of 30). Dated changes in 90 days are the 1 October migration and the agents entries of 17 and 21 August, which run through Advanced Trade (12 of 20). A public changelog and a CDP Discord; SDK issues not read (8 of 15). Official Python SDK current, the rest samples (12 of 15). SDK CI not read (5 of 10). 20 + 12 + 8 + 12 + 5 = 57.\n\n### Agent ergonomics: Coinbase Advanced Trade API +15\n\n- 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.\n- Coinbase Advanced Trade API (73): Product lists filter by product_type and product_ids with limit and offset, candles take a granularity, but fields cannot be selected and the docs warn that product lists run to hundreds of entries (15 of 25). Cursor pagination with limit on orders and fills, filters by status, product and time (16 of 20). Error codes such as INSUFFICIENT_FUND, ORDER_NOT_FOUND and PERMISSION_DENIED are documented and can be simulated in the sandbox, though the spec gives no shapes (14 of 20). client_order_id on every order; no idempotency key on other writes (16 of 20). Few required fields, an official Python SDK and sample SDKs in three languages, but each request needs a freshly signed JWT (12 of 15). 15 + 16 + 14 + 16 + 12 = 73.\n\n### Transparency \u0026 trust: Coinbase Advanced Trade API +14\n\n- Bitstamp API (53): The editorial half. A closed service whose terms of use loaded empty for our reader, so the licence and clauses are unknown (8 of 30). The privacy policy loaded empty, so retention and data handling are unchecked (0 of 30). A 410.001 code marks deprecated endpoints and the changelog records replacements such as `trading-pairs-info` by `markets`, with no notice period stated (8 of 20). Subprocessors and data locations are in the unread privacy policy (0). 8 + 0 + 8 + 0 = 16.\n- Coinbase Advanced Trade API (67): The editorial half. A closed service whose user agreement answered a bot check; the OpenAPI spec is public and the Python SDK is open on GitHub (12 of 30). Privacy facts per the coinbase-cdp-agentkit check of 1 October 2026 (Coinbase, Inc., processing countries, retention tied to need without numbers), not re-read (10 of 30). INTX endpoints retired on 1 October 2026 with a dated notice and a read-only grace period (12 of 20). Processing countries and provider categories per the same earlier check, no subprocessor list (8 of 20). 12 + 10 + 12 + 8 = 42.\n\n### Security \u0026 auth: Coinbase Advanced Trade API +8\n\n- Bitstamp API (60): Revocable HMAC-SHA256 keys with per-endpoint permissions, an IP allow-list, single-use nonces, a timestamp window, sub-account scoping and a one-call kill switch for every key; no key expiry found (24 of 30). Permissions are chosen per endpoint and withdrawals can need Travel Rule address verification, but whether a withdrawal address allow-list exists sits in the unread account settings and no confirmation step is documented for API withdrawals (14 of 20). The API returns exchange data, not third-party text (10). No per-key audit log found; the account's transaction history is the record (4 of 15). security.txt names HackerOne's Robinhood programme but expired on 12 July 2026; no certification page was readable (8 of 20). 24 + 14 + 10 + 4 + 8 = 60.\n- Coinbase Advanced Trade API (68): CDP keys with view, trade and transfer permissions, a portfolio restriction, an optional IP allowlist, revocation in the portal, ES256 JWTs that expire after 2 minutes, and OAuth2 with wallet:* scopes for other people's accounts; no key expiry (28 of 30). View-only keys and portfolio scoping limit an agent, and transfer is a separate permission, but no withdrawal address allow-list for API keys and no confirmation step were found (14 of 20). The API returns no untrusted content (10). key_permissions reports a key's scope and account activity shows in the app, but no per-call log was found (6 of 15). HackerOne bug bounty named in a security.txt that expired on 1 June 2024; certifications unread behind a bot check (10 of 20). 28 + 14 + 10 + 6 + 10 = 68.\n\n### Reliability: Bitstamp API +5\n\n- 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.\n- Coinbase Advanced Trade API (58): Read with the hosted lines. status.coinbase.com is a Statuspage site with Coinbase Advanced Trade, API, US Derivatives and International Derivatives components (20). The incidents feed we could read runs from 16 September to 3 November 2026. In it Advanced Trade was degraded for 25 minutes on 21 September, the website had a 3-minute major on 14 October, converts were down 1 hour 4 minutes on 26 October, and no incident named the API; 5 August to 15 September was beyond the feed, so minor only for the seven weeks read (15 of 30). No REST rate limit with numbers was found; the older rate-limits page answers 404 and llms.txt lists none, while the WebSocket page gives 8 connections and 8 unauthenticated messages per second per IP (5 of 15). Orders take a client_order_id, but no 429 or Retry-After guidance was found for Advanced Trade (8 of 15). No SLA (0). REST and WebSocket are generally available; the Global Derivatives gateway is a month old and not marked beta (10). 20 + 15 + 5 + 8 + 0 + 10 = 58.\n\n## Score by category\n\n| Category | Weight | Bitstamp API | Coinbase Advanced Trade API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 58 | Bitstamp API +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 51 | 80 | Coinbase Advanced Trade API +29 |\n| Agent ergonomics | 13% (16.2 this run) | 58 | 73 | Coinbase Advanced Trade API +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 68 | Coinbase Advanced Trade API +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 57 | Coinbase Advanced Trade API +29 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 53 | 67 | Coinbase Advanced Trade API +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.4 · D** | **61.7 · C** | |\n\n## Facts side by side\n\n| Fact | Bitstamp API | Coinbase Advanced Trade API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bitstamp Ltd. | Coinbase, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load | Proprietary hosted service under the Coinbase User Agreement, which answered a bot check and wasn't read. The official Python SDK coinbase-advanced-py is on GitHub |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2026-08-28 | 2026-10-01 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | 2026-05-27 |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n\n## Verdicts\n\n**Bitstamp API.** Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be read.\n\n**Coinbase Advanced Trade API.** Advanced Trade has a public OpenAPI spec, keys limited to view, trade or transfer and to one portfolio, and a keyless static sandbox. No REST rate limit is published, the fee schedule, user agreement and country list sit behind a bot check, and an agent that wants an MCP route uses the separate coinbase-mcp listing.\n\n## Before you call either\n\n### Bitstamp API\n\n1. Mint a key with only the endpoint permissions the task needs and an IP allow-list; keep `revoke_all_api_keys` in reach as a kill switch\n2. Treat `client_order_id` as a label, not a guard. On a timeout (500.016) fetch the order by client id before resending, because duplicates are accepted\n3. Use a fresh 36-character nonce and a timestamp within 150 seconds of server time on every request, or expect API0004 and API0017\n4. Stay under 400 requests a second and 10,000 per 10 minutes; 400.002 and 400.067 mean back off, and open-orders answers are cached for 10 seconds\n5. Start on sandbox.bitstamp.net with the same paths, and read the fee schedule in a browser before quoting costs, since it is unreadable to a plain fetch\n\n### Coinbase Advanced Trade API\n\n1. Mint a fresh ES256 JWT for every request; tokens expire after 2 minutes and Ed25519 keys are rejected\n2. Send a unique client_order_id on every order and reuse it on retry so a dropped connection does not place a second order\n3. Develop against api-sandbox.coinbase.com first; its responses are static, so do not read prices or fills from it\n4. Use a key with view only, or trade without transfer, and restrict it to a portfolio funded for the agent\n5. For perpetuals call the Global Derivatives JSON-RPC gateway at drb.coinbase.com; the /intx/* endpoints are retired\n\n## Questions\n\n### Which is better for AI agents, Bitstamp API or Coinbase Advanced Trade API?\n\nCoinbase Advanced Trade API scores 61.7 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories. Bitstamp API leads on reliability.\n\n### Do Bitstamp API and Coinbase Advanced Trade API need an API key?\n\nBitstamp API needs an API key. Coinbase Advanced Trade API takes an API key or an OAuth sign-in.\n\n### Can an agent call Bitstamp API and Coinbase Advanced Trade API without installing anything?\n\nNo hosted endpoint is listed for Bitstamp API. No hosted endpoint is listed for Coinbase Advanced Trade API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitstamp\", \"b\": \"coinbase-advanced-trade\"}`. From a terminal: `anchor compare bitstamp coinbase-advanced-trade`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitstamp.json and https://www.anchorterminal.com/api/v1/tools/coinbase-advanced-trade.json\n\n## Other comparisons with Bitstamp API or Coinbase Advanced Trade API\n\n- [Bitfinex API vs Bitstamp API](https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.md)\n- [Bitfinex API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.md)\n- [Bitget vs Bitstamp API](https://www.anchorterminal.com/compare/bitget-vs-bitstamp.md)\n- [Bitget vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade.md)\n- [Bithumb Open API vs Bitstamp API](https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.md)\n- [Bithumb Open API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-advanced-trade.md)\n- [Bitstamp API vs Bybit](https://www.anchorterminal.com/compare/bitstamp-vs-bybit.md)\n- [Bitstamp API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.md)\n- [Bitstamp API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.md)\n- [Bitstamp API vs Deribit](https://www.anchorterminal.com/compare/bitstamp-vs-deribit.md)\n- [Bitstamp API vs dYdX](https://www.anchorterminal.com/compare/bitstamp-vs-dydx.md)\n- [Bitstamp API vs Gate](https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.md)\n- [Bitstamp API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.md)\n- [Bitstamp API vs HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md)\n- [Bitstamp API vs Hyperliquid](https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.md)\n- [Bitstamp API vs Kraken API](https://www.anchorterminal.com/compare/bitstamp-vs-kraken.md)\n- [Bitstamp API vs KuCoin](https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.md)\n- [Bitstamp API vs MEXC API](https://www.anchorterminal.com/compare/bitstamp-vs-mexc.md)\n- [Bitstamp API vs OKX API](https://www.anchorterminal.com/compare/bitstamp-vs-okx.md)\n- [Bitstamp API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.md)\n- [Bitstamp API vs Upbit Open API](https://www.anchorterminal.com/compare/bitstamp-vs-upbit.md)\n- [Bybit vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.md)\n- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.md)\n- [Binance API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.md)\n- [Coinbase Advanced Trade API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp.md)\n- [Coinbase Advanced Trade API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange.md)\n- [Coinbase Advanced Trade API vs Deribit](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit.md)\n- [Coinbase Advanced Trade API vs Gate](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gate-io.md)\n- [Coinbase Advanced Trade API vs Gemini Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gemini-exchange.md)\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md)\n- [Coinbase Advanced Trade API vs Hyperliquid](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-hyperliquid.md)\n- [Coinbase Advanced Trade API vs Kraken API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kraken.md)\n- [Coinbase Advanced Trade API vs KuCoin](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin.md)\n- [Coinbase Advanced Trade API vs MEXC API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc.md)\n- [Coinbase Advanced Trade API vs OKX API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-okx.md)\n- [Coinbase Advanced Trade API vs Uniswap Trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap.md)\n- [Coinbase Advanced Trade API vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.md)\n- [Coinbase Advanced Trade API vs dYdX](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Bitstamp API vs Coinbase Advanced Trade API", "url": "" } ], "description": "Coinbase Advanced Trade scores 61.7 (C) to Bitstamp's 50.4 (D) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bitstamp API D 50.4", "Coinbase Advanced Trade API C 61.7", "scores" ], "h1": "Bitstamp API vs Coinbase Advanced Trade API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bitstamp-vs-coinbase-advanced-trade", "published": "2026-10-01", "section": "tools", "title": "Bitstamp vs Coinbase Advanced Trade for AI agents (2026)", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade" }, "tokens": { "markdown": 5350, "slim": 2930 }, "version": 1 }