{ "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": 942, "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": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-04T21:25:16.463949619Z" }, "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-04T21:25:16.463949619Z" } }, "answer": "Gate scores 56.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 4 of 7 scored categories. Bitstamp API leads on reliability.", "b": { "slug": "gate-io", "name": "Gate", "vendor": "Gate", "vendorUrl": "https://www.gate.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Gate is a centralised crypto exchange for spot, margin, futures, options, earn and tokenised stocks, reached through its REST and WebSocket API v4, official SDKs, a CLI, and hosted and local MCP servers under its Gate for AI programme.", "url": "https://www.anchorterminal.com/tools/gate-io", "markdownUrl": "https://www.anchorterminal.com/tools/gate-io.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/gate-io.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/gate-io.json", "dns": "gate-io.grade.anchorterminal.com", "repo": "https://github.com/gate/gate-mcp", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://api.gatemcp.ai/mcp", "packages": [ { "registry": "npm", "name": "gate-mcp" } ], "auth": "mixed", "authNotes": "The API v4 takes an API key and secret minted on the APIv4 Keys page after a browser sign-up, signed per request with HMAC-SHA512 in the KEY, Timestamp and SIGN headers, with a 60 second timestamp window. Each key carries a permission per product group (spot and margin, perpetual, delivery, wallet, withdrawal and others) set to disabled, read-only or read-write, an IP allow-list of up to 20 addresses, and changes take up to 5 minutes. The hosted MCP trading endpoint uses Gate OAuth 2 at www.gate.com/apiw/v2/mcp/oauth with scopes base, read, asset, spot_trade, futures_trade, earn, cfd and stock, revocable on the API management page; the public market-data endpoints need no credential; the local `gate-mcp` package takes GATE_API_KEY and GATE_API_SECRET (https://www.gate.com/docs/developers/apiv4/en/, https://api.gatemcp.ai/.well-known/oauth-protected-resource/mcp/exchange and https://www.gate.com/docs/developers/agent/en/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API and the MCP servers cost nothing; trades carry Gate's fees. The fee page shows its tier table only after login. Gate's help centre gives the VIP 0 spot taker rate as 0.1 per cent and its learn articles give 0.1 per cent maker and taker with GT payment lowering it to 0.09 per cent; VIP tiers run from 0 to 16. The VIP 0 futures rate was not readable (https://www.gate.com/help/trade/spot/41629 and https://www.gate.com/fee, checked 2026-11-03).", "priceSummary": "0.1% fee", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API v4 docs, the agent guide, the gate-mcp README or the fee pages (checked 2026-11-03).", "endpoints": [] }, "toolCount": 58, "popularity": { "githubStars": 44, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.gate.com/docs/developers/apiv4/en/", "registryName": "io.github.gateio-dev/gate-mcp", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "closed-source", "api-key", "oauth", "usage-priced", "sandbox", "no-status-page", "mcp", "remote-mcp", "mcp-registry", "official", "read-only-mode", "agent-skills", "cli", "python", "typescript", "go", "java", "php", "dotnet" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 56.4, "grade": "C", "agentReady": false, "rank": 741, "ranked": true, "rankOf": 1349, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 77, "payments": 35, "reliability": 42, "schema": 70, "security": 60, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Gate runs official hosted MCP servers with keyless market data and OAuth-scoped trading, a local stdio server with a read-only switch, per-endpoint rate limits with headers and a futures testnet. There is no status page, SLA or OpenAPI file, the fee table needs a login, the MCP host is a separate domain, and the terms name no company.", "bestFor": "An agent trading spot, futures and earn products in a person's Gate account outside the 35 restricted locations, with a keyless MCP for research and an OAuth MCP or scoped key for trading.", "strengths": [ "Hosted MCP at api.gatemcp.ai split by purpose, 58 market-data tools with no credential and trading tools behind Gate OAuth 2 with eight scopes, in the official MCP registry", "API keys with a disabled, read-only or read-write setting per product group, a withdrawal group of its own and an IP allow-list of up to 20 addresses", "Per-endpoint rate limits with X-Gate-RateLimit-Limit, X-Gate-RateLimit-Requests-Remain and X-Gate-RateLimit-Reset-Timestamp headers and a labelled error body", "Futures TestNet at api-testnet.gateapi.io with its own keys, and the complete REST and WebSocket docs downloadable as Markdown", "Official SDKs in Python, Java, PHP, Go, C#, Node.js and JavaScript, a CLI with JSON output, and 40 dated changelog entries in the last 90 days" ], "weaknesses": [ "No status page, incident history or SLA; the terms give no uptime guarantee and cap liability at three months of fees", "The MCP endpoints live on gatemcp.ai, not gate.com, and the registry namespace is a GitHub organisation; the OAuth scopes in the metadata differ from the ones the docs describe", "The local MCP server sets no readOnlyHint or destructiveHint annotations, and the hosted server's annotations could not be read without a session", "The fee table loads only after login, and the docs disagree with themselves on keys per account (5 against 20) and tool counts", "Clause 1.3(h) of the user agreement bans automated activity through any channel Gate has not designated, and the agreement names no legal entity" ], "agentNotes": [ "Start on https://api.gatemcp.ai/mcp for prices and order books with no credential; switch to /mcp/exchange only when the person has approved the OAuth grant with the narrowest scopes", "For a key-based route, create a key on a dedicated sub-account with read-only on every group but the one the task needs, withdrawal disabled and an IP allow-list; changes take up to 5 minutes", "Put a unique `text` value starting with t- on every spot order and reuse it on the retry; read the order back before placing again", "Read X-Gate-RateLimit-Requests-Remain and stop at zero; spot order placement is capped at 10 a second and withdrawals at 1 per 3 seconds", "Rehearse futures logic on api-testnet.gateapi.io with TestNet keys; there is no spot testnet" ], "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": 56.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 77, "payments": 35, "reliability": 42, "schema": 70, "security": 60, "transparency": 37 }, "provenanceScore": 60, "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": "npx -y gate-mcp", "http": "curl https://api.gateio.ws/api/v4/spot/tickers?currency_pair=BTC_USDT", "claudeCode": "claude mcp add gate-mcp --transport http https://api.gatemcp.ai/mcp", "config": { "mcpServers": { "gate-mcp": { "transport": "streamable-http", "url": "https://api.gatemcp.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/gate-io" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, VIP 0 taker", "unit": "pct", "usd": 0.1, "note": "maker 0.1 per cent per Gate's learn articles; 0.09 per cent paid in GT" } ], "provenance": { "legalEntity": "", "domain": "gate.com", "domainRegistered": "1996-03-29", "endpointOnVendorDomain": true, "terms": "https://www.gate.com/user-agreement", "privacy": "https://www.gate.com/privacy-policy", "statusPage": "", "changelog": "https://www.gate.com/docs/developers/apiv4/en/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The user agreement (last updated 22 July 2026) and the privacy policy name only Gate, under the laws of the Republic of Panama with ICC arbitration; no company name or registration number appears. The about page names Gate Technology Ltd for the Malta licence only.", "www.gate.com/robots.txt allows the docs, help, legal and about paths and disallows /post/, search results, referral URLs and a list of internal API paths; nothing under those paths was fetched. The /about path answered 403 and /about-us loaded.", "RDAP gives gate.com a registration date of 29 March 1996 (Amazon Registrar); the exchange moved from gate.io to gate.com and traces its origin to 2013.", "https://www.gate.com/.well-known/security.txt answers 404. No status page found; status.gate.com does not resolve and the docs link none.", "The API endpoint api.gateio.ws is Gate's own; the MCP endpoints are on api.gatemcp.ai, a separate domain whose OAuth metadata points back to www.gate.com. The changelog is the versioned section of the API v4 docs page." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/gate-io.json", "live": { "slug": "gate-io", "probe": { "target": "https://api.gatemcp.ai/mcp", "method": "get", "lastAt": "2026-11-04T21:27:50.477184601Z", "lastOk": true, "lastStatus": 200, "lastMs": 10339, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 10329, "p95ms24h": 10591, "samples24h": 62, "samples30d": 62, "days": [ { "date": "2026-11-04", "probes": 62, "ok": 62 } ] }, "versions": [ { "registry": "mcp-registry", "name": "io.github.gateio-dev/gate-mcp", "version": "1.0.0", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "npm", "name": "gate-mcp", "version": "0.19.0", "seenAt": "2026-11-04T20:17:45.56236451Z" } ], "githubStars": 44, "npmWeekly": 303, "securityTxt": { "url": "https://gate.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-04T15:53:27.737532632Z" }, "updatedAt": "2026-11-04T21:27:50.477184601Z" } }, "edges": [ { "by": 49, "category": "maintenance", "leads": "gate-io", "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 hosted service with open-source MCP packages. The API changelog's latest entry is 2 November 2026 and gate-skills was pushed 3 November (30). 40 dated changelog entries since 5 August 2026 (20). developer@gate.com, a help centre and issue trackers on gate-mcp and gate-skills, replies not checked (12 of 25). In the official MCP registry under io.github.gateio-dev, a GitHub namespace rather than gate.com, and official SDKs current (10 of 15). The local package has a publish workflow and no test workflow in CI, and its last tag is 16 April 2026 (5 of 10). 77." }, "scores": { "a": 28, "b": 77 } }, { "by": 21, "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": "Graded with the hosted lines on the API v4 at api.gateio.ws with the hosted MCP beside it. No status page found (status.gate.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per endpoint group with numbers and fill-ratio rules (15). Every response carries X-Gate-RateLimit-Limit, X-Gate-RateLimit-Requests-Remain and X-Gate-RateLimit-Reset-Timestamp, 429 answers with the label TOO_FAST, and spot orders take a user `text` identifier, but no retry or idempotency guidance is written down (12 of 15). No SLA (0). API v4 and the MCP endpoints are production surfaces (10). 42." }, "scores": { "a": 63, "b": 42 } }, { "by": 19, "category": "schema", "leads": "gate-io", "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": "No public OpenAPI file was found, though the SDKs are generated and the MCP tools carry typed parameters per the tool reference; the hosted tools' JSON Schema could not be read without a session (12 of 25). The whole REST and WebSocket documentation is downloadable as Markdown and the agent guide is a plain page (10). The tool reference gives one line and the main parameters per tool, the API reference a description per endpoint, no when-not-to-use guidance (12 of 20). Required flags, enums for side, type and time_in_force (11 of 15). Examples per endpoint and a labelled error body with a fixed label list the docs tell you to branch on instead of messages (13 of 15). A versioned changelog, v4.106.177 on 2 November 2026 (12 of 15, since entries are terse). 70." }, "scores": { "a": 51, "b": 70 } }, { "by": 15, "category": "payments", "leads": "gate-io", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No machine payment protocol (0). The fee page's table loads after login; help centre and learn articles give the VIP 0 spot rates (15 of 20). Market data over REST and the public MCP needs no account and no card (20). A person registers, verifies identity and mints the key or approves the grant in a browser (0). 35." }, "scores": { "a": 20, "b": 35 } }, { "by": 8, "category": "ergonomics", "leads": "gate-io", "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": "Read for the API with the hosted MCP beside it. The MCP is split by endpoint (58 public tools on /mcp, 400 or more on /mcp/exchange, smaller info and news servers) and the local package filters by module and read-only flag, which stands in for toolsets (5 of 25 for the trading server, 10 added back). Pagination by page and limit, from and to timestamps, status filters (15 of 20). Error labels such as INVALID_SIGNATURE, REQUEST_EXPIRED, IP_FORBIDDEN and READ_ONLY name the recovery (15 of 20). The `text` order identifier makes retries safe; the local server's source sets no readOnlyHint or destructiveHint and the hosted annotations are unread (8 of 20). Three required fields on a spot order, SDKs in seven languages and a CLI (13 of 15). 66." }, "scores": { "a": 58, "b": 66 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Bitstamp Ltd.", "b": "Gate", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.gatemcp.ai/mcp", "name": "Hosted endpoint" }, { "a": "", "b": "Streamable HTTP, stdio", "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": "none", "name": "Licence" }, { "a": "none", "b": "58", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.gateio-dev/gate-mcp", "name": "MCP registry" }, { "a": "2026-08-28", "b": "2026-11-02", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-07-22", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "44 stars", "name": "Popularity" } ], "faq": [ { "answer": "Gate scores 56.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 4 of 7 scored categories. Bitstamp API leads on reliability.", "question": "Which is better for AI agents, Bitstamp API or Gate?" }, { "answer": "Bitstamp API needs an API key. Gate takes an API key or an OAuth sign-in.", "question": "Do Bitstamp API and Gate need an API key?" }, { "answer": "No hosted endpoint is listed for Bitstamp API. Gate has a hosted endpoint at https://api.gatemcp.ai/mcp.", "question": "Can an agent call Bitstamp API and Gate without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 63 against 42" ], "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, 70 against 51", "Agent ergonomics, 66 against 58", "Payments \u0026 pricing, 35 against 20", "Maintenance \u0026 community, 77 against 28" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "An agent trading spot, futures and earn products in a person's Gate account outside the 35 restricted locations, with a keyless MCP for research and an OAuth MCP or scoped key for trading.", "slug": "gate-io", "watchFor": "No status page, incident history or SLA; the terms give no uptime guarantee and cap liability at three months of fees" } ], "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-gate-io.json", "title": "Bitfinex API vs Gate", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-gate-io" }, { "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-gate-io.json", "title": "Bitget vs Gate", "url": "https://www.anchorterminal.com/compare/bitget-vs-gate-io" }, { "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-gate-io.json", "title": "Bithumb Open API vs Gate", "url": "https://www.anchorterminal.com/compare/bithumb-vs-gate-io" }, { "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-advanced-trade.json", "title": "Bitstamp API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade" }, { "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-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-gate-io.json", "title": "Bybit vs Gate", "url": "https://www.anchorterminal.com/compare/bybit-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io.json", "title": "Crypto.com Exchange API vs Gate", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange.json", "title": "Gate vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-htx.json", "title": "Gate vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid.json", "title": "Gate vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-kraken.json", "title": "Gate vs Kraken API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-kucoin.json", "title": "Gate vs KuCoin", "url": "https://www.anchorterminal.com/compare/gate-io-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-mexc.json", "title": "Gate vs MEXC API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-okx.json", "title": "Gate vs OKX API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-uniswap.json", "title": "Gate vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-upbit.json", "title": "Gate vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-upbit" }, { "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-gate-io.json", "title": "Binance API vs Gate", "url": "https://www.anchorterminal.com/compare/binance-vs-gate-io" }, { "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-mcp-vs-gate-io.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Gate", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-gate-io.json", "title": "Deribit vs Gate", "url": "https://www.anchorterminal.com/compare/deribit-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-gate-io.json", "title": "dYdX vs Gate", "url": "https://www.anchorterminal.com/compare/dydx-vs-gate-io" } ], "panel": null, "scores": [ { "bitstamp": 63, "by": 21, "edge": "bitstamp", "gate-io": 42, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bitstamp": 51, "by": 19, "edge": "gate-io", "gate-io": 70, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bitstamp": 58, "by": 8, "edge": "gate-io", "gate-io": 66, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bitstamp": 60, "by": 0, "edge": "", "gate-io": 60, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bitstamp": 20, "by": 15, "edge": "gate-io", "gate-io": 35, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bitstamp": 28, "by": 49, "edge": "gate-io", "gate-io": 77, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bitstamp": 53, "by": 4, "edge": "bitstamp", "gate-io": 49, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Gate scores 56.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 4 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.", "gate-io": "Gate runs official hosted MCP servers with keyless market data and OAuth-scoped trading, a local stdio server with a read-only switch, per-endpoint rate limits with headers and a futures testnet. There is no status page, SLA or OpenAPI file, the fee table needs a login, the MCP host is a separate domain, and the terms name no company." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io", "json": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.min.md" }, "markdown": "Gate scores 56.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 4 of 7 scored categories. Bitstamp API leads on reliability. Both do exchange market data.\n\n- Bitstamp API: grade D, 50.4/100, rank #942 of 1349. Markdown https://www.anchorterminal.com/tools/bitstamp.md · JSON https://www.anchorterminal.com/api/v1/tools/bitstamp.json\n- Gate: grade C, 56.4/100, rank #741 of 1349. Markdown https://www.anchorterminal.com/tools/gate-io.md · JSON https://www.anchorterminal.com/api/v1/tools/gate-io.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 42\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### Gate (C)\n\nGood for: An agent trading spot, futures and earn products in a person's Gate account outside the 35 restricted locations, with a keyless MCP for research and an OAuth MCP or scoped key for trading.\n\nAhead on:\n- Schema \u0026 documentation, 70 against 51\n- Agent ergonomics, 66 against 58\n- Payments \u0026 pricing, 35 against 20\n- Maintenance \u0026 community, 77 against 28\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: No status page, incident history or SLA; the terms give no uptime guarantee and cap liability at three months of fees\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Gate +49\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- Gate (77): Read as a hosted service with open-source MCP packages. The API changelog's latest entry is 2 November 2026 and gate-skills was pushed 3 November (30). 40 dated changelog entries since 5 August 2026 (20). developer@gate.com, a help centre and issue trackers on gate-mcp and gate-skills, replies not checked (12 of 25). In the official MCP registry under io.github.gateio-dev, a GitHub namespace rather than gate.com, and official SDKs current (10 of 15). The local package has a publish workflow and no test workflow in CI, and its last tag is 16 April 2026 (5 of 10). 77.\n\n### Reliability: Bitstamp API +21\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- Gate (42): Graded with the hosted lines on the API v4 at api.gateio.ws with the hosted MCP beside it. No status page found (status.gate.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per endpoint group with numbers and fill-ratio rules (15). Every response carries X-Gate-RateLimit-Limit, X-Gate-RateLimit-Requests-Remain and X-Gate-RateLimit-Reset-Timestamp, 429 answers with the label TOO_FAST, and spot orders take a user `text` identifier, but no retry or idempotency guidance is written down (12 of 15). No SLA (0). API v4 and the MCP endpoints are production surfaces (10). 42.\n\n### Schema \u0026 documentation: Gate +19\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- Gate (70): No public OpenAPI file was found, though the SDKs are generated and the MCP tools carry typed parameters per the tool reference; the hosted tools' JSON Schema could not be read without a session (12 of 25). The whole REST and WebSocket documentation is downloadable as Markdown and the agent guide is a plain page (10). The tool reference gives one line and the main parameters per tool, the API reference a description per endpoint, no when-not-to-use guidance (12 of 20). Required flags, enums for side, type and time_in_force (11 of 15). Examples per endpoint and a labelled error body with a fixed label list the docs tell you to branch on instead of messages (13 of 15). A versioned changelog, v4.106.177 on 2 November 2026 (12 of 15, since entries are terse). 70.\n\n### Payments \u0026 pricing: Gate +15\n\n- 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.\n- Gate (35): No machine payment protocol (0). The fee page's table loads after login; help centre and learn articles give the VIP 0 spot rates (15 of 20). Market data over REST and the public MCP needs no account and no card (20). A person registers, verifies identity and mints the key or approves the grant in a browser (0). 35.\n\n### Agent ergonomics: Gate +8\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- Gate (66): Read for the API with the hosted MCP beside it. The MCP is split by endpoint (58 public tools on /mcp, 400 or more on /mcp/exchange, smaller info and news servers) and the local package filters by module and read-only flag, which stands in for toolsets (5 of 25 for the trading server, 10 added back). Pagination by page and limit, from and to timestamps, status filters (15 of 20). Error labels such as INVALID_SIGNATURE, REQUEST_EXPIRED, IP_FORBIDDEN and READ_ONLY name the recovery (15 of 20). The `text` order identifier makes retries safe; the local server's source sets no readOnlyHint or destructiveHint and the hosted annotations are unread (8 of 20). Three required fields on a spot order, SDKs in seven languages and a CLI (13 of 15). 66.\n\n## Score by category\n\n| Category | Weight | Bitstamp API | Gate | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 42 | Bitstamp API +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 51 | 70 | Gate +19 |\n| Agent ergonomics | 13% (16.2 this run) | 58 | 66 | Gate +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 60 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 35 | Gate +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 77 | Gate +49 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 53 | 49 | Bitstamp API +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.4 · D** | **56.4 · C** | |\n\n## Facts side by side\n\n| Fact | Bitstamp API | Gate |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bitstamp Ltd. | Gate |\n| Hosted endpoint | no (local only) | `https://api.gatemcp.ai/mcp` |\n| Transports | | Streamable HTTP, stdio |\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 | none |\n| Tools exposed | none | 58 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | no |\n| MCP registry | not listed | `io.github.gateio-dev/gate-mcp` |\n| Last release | 2026-08-28 | 2026-11-02 |\n| Terms last updated | couldn't be read | 2026-07-22 |\n| Privacy policy last updated | couldn't be read | no date given |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | none | 44 stars |\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**Gate.** Gate runs official hosted MCP servers with keyless market data and OAuth-scoped trading, a local stdio server with a read-only switch, per-endpoint rate limits with headers and a futures testnet. There is no status page, SLA or OpenAPI file, the fee table needs a login, the MCP host is a separate domain, and the terms name no company.\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### Gate\n\n1. Start on https://api.gatemcp.ai/mcp for prices and order books with no credential; switch to /mcp/exchange only when the person has approved the OAuth grant with the narrowest scopes\n2. For a key-based route, create a key on a dedicated sub-account with read-only on every group but the one the task needs, withdrawal disabled and an IP allow-list; changes take up to 5 minutes\n3. Put a unique `text` value starting with t- on every spot order and reuse it on the retry; read the order back before placing again\n4. Read X-Gate-RateLimit-Requests-Remain and stop at zero; spot order placement is capped at 10 a second and withdrawals at 1 per 3 seconds\n5. Rehearse futures logic on api-testnet.gateapi.io with TestNet keys; there is no spot testnet\n\n## Questions\n\n### Which is better for AI agents, Bitstamp API or Gate?\n\nGate scores 56.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 4 of 7 scored categories. Bitstamp API leads on reliability.\n\n### Do Bitstamp API and Gate need an API key?\n\nBitstamp API needs an API key. Gate takes an API key or an OAuth sign-in.\n\n### Can an agent call Bitstamp API and Gate without installing anything?\n\nNo hosted endpoint is listed for Bitstamp API. Gate has a hosted endpoint at https://api.gatemcp.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitstamp\", \"b\": \"gate-io\"}`. From a terminal: `anchor compare bitstamp gate-io`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitstamp.json and https://www.anchorterminal.com/api/v1/tools/gate-io.json\n\n## Other comparisons with Bitstamp API or Gate\n\n- [Bitfinex API vs Bitstamp API](https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.md)\n- [Bitfinex API vs Gate](https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.md)\n- [Bitget vs Bitstamp API](https://www.anchorterminal.com/compare/bitget-vs-bitstamp.md)\n- [Bitget vs Gate](https://www.anchorterminal.com/compare/bitget-vs-gate-io.md)\n- [Bithumb Open API vs Bitstamp API](https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.md)\n- [Bithumb Open API vs Gate](https://www.anchorterminal.com/compare/bithumb-vs-gate-io.md)\n- [Bitstamp API vs Bybit](https://www.anchorterminal.com/compare/bitstamp-vs-bybit.md)\n- [Bitstamp API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.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 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 Gate](https://www.anchorterminal.com/compare/bybit-vs-gate-io.md)\n- [Crypto.com Exchange API vs Gate](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io.md)\n- [Gate vs Gemini Exchange API](https://www.anchorterminal.com/compare/gate-io-vs-gemini-exchange.md)\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md)\n- [Gate vs Hyperliquid](https://www.anchorterminal.com/compare/gate-io-vs-hyperliquid.md)\n- [Gate vs Kraken API](https://www.anchorterminal.com/compare/gate-io-vs-kraken.md)\n- [Gate vs KuCoin](https://www.anchorterminal.com/compare/gate-io-vs-kucoin.md)\n- [Gate vs MEXC API](https://www.anchorterminal.com/compare/gate-io-vs-mexc.md)\n- [Gate vs OKX API](https://www.anchorterminal.com/compare/gate-io-vs-okx.md)\n- [Gate vs Uniswap Trading API](https://www.anchorterminal.com/compare/gate-io-vs-uniswap.md)\n- [Gate vs Upbit Open API](https://www.anchorterminal.com/compare/gate-io-vs-upbit.md)\n- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.md)\n- [Binance API vs Gate](https://www.anchorterminal.com/compare/binance-vs-gate-io.md)\n- [Coinbase Advanced Trade API vs Gate](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-gate-io.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Gate](https://www.anchorterminal.com/compare/coinbase-mcp-vs-gate-io.md)\n- [Deribit vs Gate](https://www.anchorterminal.com/compare/deribit-vs-gate-io.md)\n- [dYdX vs Gate](https://www.anchorterminal.com/compare/dydx-vs-gate-io.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 Gate", "url": "" } ], "description": "Gate scores 56.4 (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", "Gate C 56.4", "scores" ], "h1": "Bitstamp API vs Gate", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bitstamp-vs-gate-io", "published": "2026-10-01", "section": "tools", "title": "Bitstamp vs Gate for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io" }, "tokens": { "markdown": 4500, "slim": 2380 }, "version": 1 }