Head to head · Exchange market data · October 2026 research run
Bitpont API and MCP vs Gemini Exchange API
Gemini Exchange API scores 77.1 (BB) on agent readiness against Bitpont API and MCP's 62.9 (B), and leads in 6 of 7 scored categories. Bitpont API and MCP leads on payments & pricing. Both do exchange market data.
Best crypto exchange APIs and MCP servers for AI agents · All 231 exchanges comparisons
Which one, for what
Best for An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.
Ahead on
- Payments & pricing, 90 against 60
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
No status page, no SLA and no sandbox or testnet in the reviewed documentation
Best for An agent trading spot, perpetuals or prediction markets for a US customer with a role-limited key and a sandbox to rehearse on.
Ahead on
- Reliability, 73 against 45
- Schema & documentation, 88 against 82
- Agent ergonomics, 79 against 74
- Security & auth, 78 against 63
- Maintenance & community, 88 against 14
- Transparency & trust, 75 against 58
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
Watch for
Client order ids are only recommended to be unique and no duplicate rejection is documented, so a retried order can execute twice
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Gemini Exchange API +74
Bitpont API and MCP 14
Read as a closed hosted service. The changelog names versions (Bitpont 5.102.20, API 1.9) with no dates, so the time since the last release can't be established (0) and there are no dated entries (0). A public changelog and a support email; no answer observed and the GitHub organisation is closed to our reader (6 of 15). A first-party JavaScript client and TypeScript declarations as downloads, not on a package registry, and no MCP registry entry (8 of 15). No package or public CI seen (0). The public announcement was on 20 November 2026, so the record is days old. Total 14.
Gemini Exchange API 88
Read as a closed hosted service with an open repository. The revision history's latest entry is 28 October 2026 and the repository was pushed on 5 October (30). Thirteen dated entries between 2 September and 28 October 2026 (20). The nine open items on the repository are all pull requests with replies, Dependabot included, and the docs name trading@gemini.com for developer support; no public issue tracker was tested (15 of 25). Not in the official MCP registry, but current official SDKs, TypeScript 0.1.1 of 23 September and Go 0.1.0 of 29 August 2026 (15). CI workflows validate and publish both SDKs and the MCP server has tests; dependencies are current (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.
Payments & pricing Bitpont API and MCP +30
Bitpont API and MCP 90
No x402, MPP or L402; a verified trading fee lifting quotas for an hour is not a payment protocol (0). The API is free under published limits and the 0.40% interface fee is published per route without a login (30). Free access with no card (30). An agent starts with no signup by creating a private workspace through the API (30). Total 90.
Gemini Exchange API 60
No machine payment protocol (0). The API fee schedule is public per tier without login, 0.6% maker and 1.2% taker at the base tier (20). The API is free to call, public market data needs no key, and the sandbox credits test funds with no card (20). A person must sign up in a browser with identity checks, mint a key or approve an OAuth grant, and production OAuth apps wait for Gemini's review (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Reliability Gemini Exchange API +28
Bitpont API and MCP 45
Read with the hosted lines on the REST API and hosted MCP server. No status page linked from any page read (0). No readable incident history (5). Rate limits with numbers, 30 request units a minute per IP for free access, 60 for partner keys, six items a batch (15). RateLimit and Retry-After headers documented, a retryable flag on every error, and stable request IDs and saved tasks for recovering a write after a lost response (15). No SLA (0). Nothing in the reviewed pages marks the API as beta or preview (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.
Gemini Exchange API 73
Read with the hosted lines on the REST API at api.gemini.com. status.gemini.com is a Statuspage site with component history (20). Its Atom feed for 10 September to 3 November 2026 holds 25 entries, mostly scheduled trading and FIX upgrades of 15 to 60 minutes with possible order timeouts, single-network deposit delays, and incorrect perpetual index prices for about 3.5 hours on 15 and 16 October; a 3-hour scheduled eOTC window was planned and outside the core API. Minor only (20). Rate limits with numbers, 120 a minute public and 600 private plus per-endpoint limits (15). 429 is documented but with no Retry-After or backoff guidance, and client order ids are recommended without duplicate rejection, so retries are not safe by contract; the heartbeat cancel is a safety net rather than idempotency (8 of 15). No SLA found (0). Generally available (10). 20 + 20 + 15 + 8 + 0 + 10 = 73.
Transparency & trust Gemini Exchange API +17
Bitpont API and MCP 58
The editorial half. Closed source under readable terms, which licence the published SDK and documentation for integrations (15 of 30). A detailed privacy notice naming the operator, bases, recipients and browser storage, but it promises no deletion period for server logs and support records and no DPA was found (18 of 30). No deprecation policy or dated notices; the changelog only says changes are additive (5 of 20). Integration providers named by function (Jupiter, deBridge, Velocity, Jito, Kamino, KyberSwap, LI.FI, 1inch); the hosting provider and data locations are given only on request (10 of 20). Total 48.
Gemini Exchange API 75
The editorial half. A closed service under a user agreement that names its entities by state, with the MCP server and SDKs open under Apache-2.0 (18 of 30). The privacy policy of 11 May 2026 names entities and processing countries, ties retention to need without numbers and names provider categories only, with no DPA or subprocessor list found (16 of 30). The revision history records removals and type changes with dates, but the upcoming-changes page is "TBD" and no notice period is stated (8 of 20). Processing countries are named (US, Ireland, UK, Malta, Singapore, Australia) and providers by category, with no named subprocessors (12 of 20). 18 + 16 + 8 + 12 = 54.
Security & auth Gemini Exchange API +15
Bitpont API and MCP 63
Keyless use with a client-created workspace secret in a header; optional partner bearer keys with scopes, expiry and revocation, rotated by asking the operator; no key in a URL (22 of 30). Four scopes from read to submit, customer approval of exact trading tickets, and the owner's wallet signs every value transfer (18 of 20). The API returns third-party token and protocol data; the pages say symbols are labels and exact addresses identify assets, but nothing on prompt injection (8 of 15). Per-workspace execution receipts, a monthly settlement report and a usage endpoint (10 of 15). A private reporting email on the security page with no bounty, response time or safe harbour, no security.txt (404) and no certification; the page says Bitpont itself has no independent audit (5 of 20). Total 63.
Gemini Exchange API 78
Revocable API keys with one role each (Trader, Fund Manager, Auditor, Administrator), HMAC-SHA384 signing with a nonce, and OAuth 2.0 with scopes, PKCE S256, single-use refresh tokens and RFC 7009 revocation; no IP allow-list documented and no key expiry (28 of 30). Auditor is read-only, a Trader key cannot withdraw, approved withdrawal addresses are a Fund Manager action, and the MCP server refuses funds-moving tools without confirm: true (18 of 20). The MCP server wraps every response in untrusted-output markers, strips control and bidi characters and redacts memos, labels and agreement text; the REST docs say nothing on the subject (13 of 15). Order and transfer history are readable, but no per-key audit log or API access log was found (5 of 15). security.txt with a PGP contact and a bug bounty paying $150 to $20,000, scoped to the sandbox hosts; no certification was read and no public advisory process was found (14 of 20). 28 + 18 + 13 + 5 + 14 = 78.
Schema & documentation Gemini Exchange API +6
Bitpont API and MCP 82
OpenAPI 3.1 file Bitpont Developer API 1.33.0 with 1,149 operations, read once as the reference viewer's source (25). llms.txt, Markdown downloads of the developer pages and Markdown agent guides (10). Every operation has a description and most a summary that states its job, and the guides say which tool to use for which task, though few say when not to (14 of 20). Enums, regex patterns and length limits on addresses and base-unit amounts, required fields; some inputs still allow free-form objects and the MCP operation takes a generic params object (12 of 15). Code examples in the guides and a shared error schema with code, requestId and retryable on 400 to 504 (13 of 15). A versioned changelog, but its entries carry no dates and its latest API version (1.9) doesn't match the file's 1.33.0 (8 of 15). Total 82.
Gemini Exchange API 88
OpenAPI 3 for REST (specs/openapi/rest.yaml), AsyncAPI for WebSocket, a prediction-markets OpenAPI file and a specs/index.json catalogue; the MCP server's tools take zod schemas published as JSON Schema (25). llms.txt, llms-full.txt, agents.md, an agent card and an agent skills index (10). Endpoint pages state purpose, the Build an agent guide says what to establish before acting and when to stop, and MCP tool descriptions tell the model when to confirm; the docs don't say when not to use an endpoint (15 of 20). Typed inputs with enums for order types, options and sessions, required fields marked, decimals as strings since 7 July 2026 (12 of 15). Examples throughout, samples in three languages, and an error-codes page with 53 named reasons and their HTTP statuses (14 of 15). A revision history dated from 2015 to 28 October 2026 and versioned paths (v1, v2), but the upcoming-changes page reads "TBD" (12 of 15). 25 + 10 + 15 + 12 + 14 + 12 = 88.
Score by category
| Category | Weight | Bitpont API and MCP | Gemini Exchange API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 73 | Gemini Exchange API +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 88 | Gemini Exchange API +6 |
| Agent ergonomics | 13% | 74 | 79 | Gemini Exchange API +5 |
| Security & auth | 14% | 63 | 78 | Gemini Exchange API +15 |
| Payments & pricing | 10% | 90 | 60 | Bitpont API and MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 14 | 88 | Gemini Exchange API +74 |
| Transparency & trust | 7% | 58 | 75 | Gemini Exchange API +17 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.9/100 | BB 77.1/100 |
Facts side by side
| Fact | Bitpont API and MCP | Gemini Exchange API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bitpont (LiMiT) | Gemini Trust Company, LLC |
| Hosted endpoint | https://www.bitpont.com/api/v1/mcp | no (local only) |
| Transports | Streamable HTTP | stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | A proprietary hosted service under the Bitpont Terms of Use (LIMIT SRL). The terms licence the published SDK, declarations, examples and API documentation for building integrations, with no copyright fee; the backend is closed | Proprietary hosted API under Gemini's user agreement. The developer-platform repository (MCP server, TypeScript and Go SDKs, samples and skills) is Apache-2.0 |
| Tools exposed | 1148 | 87 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | none | 2026-10-28 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2026-11-11 | no date given |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 8 stars, 99 npm/wk |
How the scores have moved
Bitpont API and MCP
No score change since it was listed.
Verdicts
Bitpont API and MCP
Public market reads, quotes and unsigned transaction drafts work without an account, every trade is signed in the owner's wallet, and an OpenAPI 3.1 file covers all 1,148 operations. There is no status page, the changelog carries no dates, and the hosted MCP server exposes the same 1,148 tools, narrowed by product filters and a search tool.
Gemini Exchange API
Gemini publishes an OpenAPI and AsyncAPI contract, API key roles that keep withdrawals off a trading key, a funded sandbox, and an official MCP server whose tools carry read-only and destructive annotations and a confirm gate. Client order ids are not checked for duplicates, there is no SLA, and UK, EEA and Australian accounts closed in April 2026.
Before you call either
Bitpont API and MCP
- Connect with
?product=swapor another product ID, then callbitpont_findToolsandbitpont_describeToolrather than loading all 1,148 tools - Create a private workspace before the first ticket and store its secret and your
requestId; reuse both to recover an order - Call
bitpont_checkInputsbefore preparing a transaction; amounts are base-unit decimal strings - If a request returns 429, wait for the
Retry-Aftervalue. The free budget is 30 units a minute per IP and a batch costs one unit per item - Never repeat a submission whose outcome is unknown; read the execution receipt first
Gemini Exchange API
- Create a Trader key for order flow and a separate Fund Manager key only if withdrawals are in scope; never combine them, and keep the secret out of prompts and logs
- Set a
client_order_idper order and look it up withget_order_statusbefore resending after a timeout, because Gemini does not reject duplicates - Start on api.sandbox.gemini.com with the same code; sandbox apps register at once, production OAuth apps wait for Gemini's review
- Stay under 1 public and 5 private requests a second; a 429 keeps answering 429 until the rate falls, with no Retry-After to read
- Check the person's country against the availability page first; UK, EEA and Australian accounts were closed on 6 April 2026
Questions
Which is better for AI agents, Bitpont API and MCP or Gemini Exchange API?
Gemini Exchange API scores 77.1 (BB) on agent readiness against Bitpont API and MCP's 62.9 (B), and leads in 6 of 7 scored categories. Bitpont API and MCP leads on payments & pricing.
Do Bitpont API and MCP and Gemini Exchange API need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Bitpont API and MCP and Gemini Exchange API without installing anything?
Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. Gemini Exchange API runs on your own machine, with no hosted endpoint listed.
Other comparisons with Bitpont API and MCP or Gemini Exchange API
- Bitfinex API vs Bitpont API and MCP
- Bitfinex API vs Gemini Exchange API
- Bitget vs Bitpont API and MCP
- Bitget vs Gemini Exchange API
- Bithumb Open API vs Bitpont API and MCP
- Bithumb Open API vs Gemini Exchange API
- Bitpont API and MCP vs Bitstamp API
- Bitpont API and MCP vs Bybit
- Bitpont API and MCP vs Coinbase Advanced Trade API
- Bitpont API and MCP vs Coinbase MCP server (Coinbase for Agents)
- Bitpont API and MCP vs Crypto.com Exchange API
- Bitpont API and MCP vs Deribit
- Bitpont API and MCP vs dYdX
- Bitpont API and MCP vs Gate
- Bitpont API and MCP vs HTX trading API
- Bitpont API and MCP vs Hyperliquid
- Bitpont API and MCP vs Kraken API
- Bitpont API and MCP vs KuCoin
- Bitpont API and MCP vs MEXC API
- Bitpont API and MCP vs OKX API
- Bitpont API and MCP vs Uniswap Trading API
- Bitpont API and MCP vs Upbit Open API
- Bitstamp API vs Gemini Exchange API
- Bybit vs Gemini Exchange API
- Crypto.com Exchange API vs Gemini Exchange API
- Gate vs Gemini Exchange API
- Gemini Exchange API vs HTX trading API
- Gemini Exchange API vs Hyperliquid
- Gemini Exchange API vs Kraken API
- Gemini Exchange API vs KuCoin
- Gemini Exchange API vs MEXC API
- Gemini Exchange API vs OKX API
- Gemini Exchange API vs Uniswap Trading API
- Gemini Exchange API vs Upbit Open API
- Binance API vs Bitpont API and MCP
- Binance API vs Gemini Exchange API
- Coinbase Advanced Trade API vs Gemini Exchange API
- Coinbase MCP server (Coinbase for Agents) vs Gemini Exchange API
- Deribit vs Gemini Exchange API
- dYdX vs Gemini Exchange API
Machine-readable
- This page as Markdown
/compare/bitpont-vs-gemini-exchange.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bitpont.json·/api/v1/tools/gemini-exchange.json - From a terminal
anchor compare bitpont gemini-exchange(the CLI) - Over MCP
compare_tools {"a": "bitpont", "b": "gemini-exchange"}at/mcp, no key