{ "data": { "a": { "slug": "binance", "name": "Binance API", "vendor": "Binance", "vendorUrl": "https://developers.binance.com/", "kind": "http-api", "category": "crypto-exchanges", "summary": "Binance's API covers spot, margin and futures trading, market data and account endpoints over REST, WebSocket and FIX, with a free spot testnet and a remote MCP server, documented on 30 October 2026, that trades inside a dedicated Agentic sub-account.", "url": "https://www.anchorterminal.com/tools/binance", "markdownUrl": "https://www.anchorterminal.com/tools/binance.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/binance.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/binance.json", "dns": "binance.grade.anchorterminal.com", "repo": "https://github.com/binance/binance-spot-api-docs", "license": "Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://agent.binance.com/mcp/agentic", "packages": [], "auth": "mixed", "authNotes": "API key with an HMAC secret, or a self-generated RSA or Ed25519 key pair whose public key is registered, sent as X-MBX-APIKEY with a signed query and timestamp (recvWindow 5000 ms by default). Permissions are reading, spot and margin trading, futures and withdrawals; an HMAC key without an IP restriction can only read since 30 January 2023, and withdrawals need an IP restriction. Only Verified Plus accounts can create keys. The MCP server uses OAuth in a desktop browser with four scopes (market data, account, trade, transfer) on a dedicated Agentic sub-account and no withdrawal scope (https://www.binance.com/en/support/faq/detail/360002502072, https://developers.binance.com/en/docs/agent-native/mcp-server/agentic, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Spot trades carry a standard fee of 0.1 per cent for regular users per the fee FAQ; the maker and taker table on the fee page loads by script and wasn't read, nor were futures fees. Public market data and the spot testnet need no account; the testnet needs a GitHub login.", "priceSummary": "0.1% fee", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the exchange API or the MCP server in the docs read (checked 2026-11-03). A separate Binance x402 product is named in press coverage of Agent OS, which wasn't read first-hand.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 4903, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developers.binance.com/docs/binance-spot-api-docs/README", "llmsTxt": "https://developers.binance.com/en/docs/llms.txt", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "official", "closed-source", "api-key", "oauth", "mcp", "remote-mcp", "llms-txt", "sandbox", "python", "typescript", "java", "go", "cli", "usage-priced", "no-card" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 63.2, "grade": "B", "agentReady": false, "rank": 473, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 81, "payments": 35, "reliability": 45, "schema": 86, "security": 72, "transparency": 43 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.", "bestFor": "An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.", "strengths": [ "Rate limits published as per-endpoint weights with 6,000 a minute, 50 orders per 10 seconds and Retry-After on 429 and 418", "Spot testnet with REST, WebSocket and FIX endpoints, virtual balances and production limits, free with a GitHub login", "Official remote MCP server with OAuth scopes, an isolated Agentic sub-account, no withdrawal scope and confirmation before writes", "Keys with reading, trading, futures and withdrawal permissions; unrestricted-IP HMAC keys can only read and withdrawals need an IP restriction", "Dated changelog since 2018 with retirement dates announced months ahead, llms.txt and llms-full.txt" ], "weaknesses": [ "No status page or incident history found on binance.com or in the API docs", "The Terms of Use and privacy notice load by script and weren't read, so what they say about bots and API use is unknown", "The MCP server's tool list and schemas are not published; the docs describe four scopes", "The maker and taker fee table loads by script; only the 0.1 per cent standard rate in a FAQ was read", "binance-api-swagger was last pushed in October 2024, so the machine-readable spec lags the docs" ], "agentNotes": [ "Read the X-MBX-USED-WEIGHT and X-MBX-ORDER-COUNT headers and stop on 429 for the Retry-After seconds; a 418 ban runs 2 minutes to 3 days", "Treat a 5xx on an order as unknown, not failed, and query the order by origClientOrderId before retrying", "Use an Ed25519 key with an IP restriction and only the reading and trading permissions; never enable withdrawals for an agent key", "Develop on testnet.binance.vision with BINANCE_API_ENV=testnet; it resets about monthly without notice", "For the MCP route, the person must fund the Agentic sub-account from the web UI first; the agent cannot move funds in from the main account" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.2 } ], "editorialScores": { "ergonomics": 76, "maintenance": 81, "payments": 35, "reliability": 45, "schema": 86, "security": 72, "transparency": 31 }, "provenanceScore": 54, "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://api.binance.com/api/v3/ticker/price?symbol=BTCUSDT", "claudeCode": "claude mcp add binance-mcp-server --transport http https://agent.binance.com/mcp/agentic", "config": { "mcpServers": { "binance-mcp-server": { "url": "https://agent.binance.com/mcp/agentic" } } } }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/binance" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, regular user", "unit": "pct", "usd": 0.1, "note": "standard fee per the fee FAQ; maker and taker table not read" } ], "provenance": { "legalEntity": "", "domain": "binance.com", "domainRegistered": "2017-04-01", "endpointOnVendorDomain": true, "terms": "https://www.binance.com/en/terms", "privacy": "https://www.binance.com/en-GB/about-legal/privacy-portal", "statusPage": "", "changelog": "https://developers.binance.com/docs/binance-spot-api-docs/CHANGELOG", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "The Terms of Use and the privacy pages answered our reader with navigation and footer only, so no contracting entity, governing law or data-handling statement was read. The about page names three ADGM entities as regulated subsidiaries, not as the contracting party.", "RDAP gives binance.com a registration date of 1 April 2017.", "https://www.binance.com/.well-known/security.txt has a Contact line (security@binance.com) and no Expires or Policy line, so its validity is unknown under RFC 9116.", "No status page was found. www.binance.com/robots.txt allows the pages read and disallows */api/, */bapi/ and */my/; developers.binance.com and agent.binance.com have no robots.txt (404); api.binance.com and testnet.binance.vision disallow all crawlers, so no API call was made to either.", "The spot API changelog is dated, newest 30 October 2026." ], "score": 54 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/binance.json", "live": { "slug": "binance", "probe": { "target": "https://agent.binance.com/mcp/agentic", "method": "get", "lastAt": "2026-11-04T20:46:35.402187536Z", "lastOk": true, "lastStatus": 404, "lastMs": 531, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 475, "p95ms24h": 594, "samples24h": 55, "samples30d": 55, "days": [ { "date": "2026-11-04", "probes": 55, "ok": 55 } ] }, "githubStars": 4902, "securityTxt": { "url": "https://binance.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:53:46.658619838Z" }, "updatedAt": "2026-11-04T20:46:35.402187536Z" } }, "answer": "Uniswap Trading API and Binance API score within a point of each other on agent readiness, 63.3 (B) and 63.2 (B). Binance API leads on security \u0026 auth.", "b": { "slug": "uniswap", "name": "Uniswap Trading API", "vendor": "Uniswap Labs", "vendorUrl": "https://developers.uniswap.org", "kind": "http-api", "category": "crypto-exchanges", "summary": "Uniswap Labs' Trading API quotes and builds swap, bridge and liquidity transactions across Uniswap v2, v3, v4 and UniswapX on 21 chains. The caller signs with its own wallet and broadcasts; the API is free behind an API key.", "url": "https://www.anchorterminal.com/tools/uniswap", "markdownUrl": "https://www.anchorterminal.com/tools/uniswap.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/uniswap.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/uniswap.json", "dns": "uniswap.grade.anchorterminal.com", "repo": "https://github.com/Uniswap/uniswap-ai", "license": "The Trading API is a proprietary hosted service under Uniswap Labs' API Terms of Use, which we couldn't read; the SDKs and the uniswap-ai skills are MIT. Swaps execute on the open-source Uniswap protocol contracts on chain", "transports": [], "packages": [ { "registry": "npm", "name": "@uniswap/v4-sdk" } ], "auth": "api-key", "authNotes": "An API key from the Uniswap Developer Platform dashboard, sent as `x-api-key` on every request; the docs say to keep it server-side. The API never holds funds or keys. `/quote` returns `permitData` the user signs as EIP-712 typed data, `/swap` returns calldata the caller signs and broadcasts, and `/order` takes a signed UniswapX order. An optional `X-Agent-Info` header with `decision_origin` of `autonomous` or `human_mediated` attributes agent traffic (https://developers.uniswap.org/docs/trading/swapping-api/start-building/integration-guide, checked 2026-11-03).", "pricing": "free", "pricingNotes": "The API is free, with no subscription or per-call charge, per the FAQ and the Developer Platform post of 16 April 2026. Swaps pay the pool fee and gas on chain; UniswapX orders are gasless for the swapper. Integrators may add up to 4 fee entries totalling at most 500 bips. Each key is limited to 6 requests a second (https://developers.uniswap.org/docs/trading/swapping-api/faqs, checked 2026-11-03).", "priceSummary": "Free", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the API's endpoints (checked 2026-11-03). The uniswap-ai repository's `pay-with-any-token` skill helps an agent pay HTTP 402 challenges (MPP or x402) by swapping tokens through Uniswap, which is a buyer-side skill, not a paid endpoint.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 236, "npmWeekly": 153782, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developers.uniswap.org/docs/trading/overview", "llmsTxt": "https://developers.uniswap.org/llms.txt", "openapi": "https://trade-api.gateway.uniswap.org/v1/api.json", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "market.crypto", "wallet.onchain" ], "tags": [ "official", "hosted", "closed-source", "openapi", "llms-txt", "api-key", "free", "no-card", "typescript", "agent-skills", "no-status-page", "security-txt", "rest" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 63.3, "grade": "B", "agentReady": false, "rank": 470, "ranked": true, "rankOf": 1349, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 88, "payments": 40, "reliability": 42, "schema": 90, "security": 63, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "The Trading API is free, documented by an OpenAPI file with stable error codes, holds no keys since the caller signs every swap, and posts sunset notices 30 days ahead. There is no official MCP server, status page or sandbox, the key is a plain header secret at 6 requests a second, and the API terms refused our reader.", "bestFor": "An agent swapping or bridging tokens from its own wallet on 21 EVM chains, or managing liquidity positions, with routing done for it.", "strengths": [ "OpenAPI 3.0 file, llms.txt, llms-full.txt and Markdown twins, with 400, 401, 404 and 429 schemas and a stable `errorCode` enum", "The API builds calldata and never holds funds or keys; the caller signs `permitData` and the transaction with its own wallet", "Free with no per-call charge, 21 chains for classic swaps and UniswapX on 10 of them", "Dated changelog notices with a 30-day minimum sunset policy, and the uniswap-ai skills (MIT) for coding agents", "A documented `X-Agent-Info` header for autonomous and human-mediated traffic, and retry guidance per error code" ], "weaknesses": [ "No official MCP server; the registry's Uniswap entries are third parties", "No status page, no SLA and no sandbox; tests use production endpoints on testnets", "A single `x-api-key` per key with 6 requests a second and no scopes; the dashboard is disallowed by robots.txt so key management is unchecked", "The API Terms of Use and Uniswap Labs' terms and privacy policy are on a help centre that answered 403 or draw by script, so restricted countries and data handling are unchecked", "No official client library for the API; the TypeScript SDKs cover the protocol and quoting, not the API" ], "agentNotes": [ "Call `/check_approval` first, then `/quote`; if `permitData` is non-null sign it as EIP-712 and send `signature` and `permitData` together to `/swap` or `/order`, never one without the other", "Route on the quote's `routing`: `CLASSIC`, `WRAP`, `UNWRAP` and `BRIDGE` go to `/swap`, `DUTCH_V2`, `DUTCH_V3` and `PRIORITY` to `/order`, `CHAINED` to `/plan`", "Refresh any quote older than 30 seconds before broadcasting, and on 429 pause every request from the key before retrying", "Retry unchanged only on `UpstreamTimeoutError`; `NoRouteFoundError` and `QuoteAmountTooLowError` need a different amount, token or `protocols` list", "Send `X-Agent-Info` with `decision_origin: autonomous` and keep `x-api-key` server-side" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.3 } ], "editorialScores": { "ergonomics": 72, "maintenance": 88, "payments": 40, "reliability": 42, "schema": 90, "security": 63, "transparency": 35 }, "provenanceScore": 74, "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 skills add Uniswap/uniswap-ai", "http": "curl -X POST https://trade-api.gateway.uniswap.org/v1/quote -H 'x-api-key: YOUR_UNISWAP_API_KEY' -H 'Content-Type: application/json' -d '{\"tokenIn\":\"0x0000000000000000000000000000000000000000\",\"tokenOut\":\"0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48\",\"tokenInChainId\":1,\"tokenOutChainId\":1,\"type\":\"EXACT_INPUT\",\"amount\":\"1000000000000000000\",\"swapper\":\"0xYourWallet\"}'" }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/uniswap" }, "area": "payments", "provenance": { "legalEntity": "Uniswap Labs", "domain": "uniswap.org", "domainRegistered": "2018-11-26", "endpointOnVendorDomain": true, "terms": "https://support.uniswap.org/hc/en-us/articles/43018872248589-API-Terms-of-Use", "privacy": "", "statusPage": "", "changelog": "https://developers.uniswap.org/docs/changelog", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "Uniswap Labs is the name on the uniswap-ai licence and the blog; the API Terms of Use (support.uniswap.org, answered 403) are said in a search snippet to name Universal Navigation, Inc., which was not read first-hand.", "RDAP gives uniswap.org a registration date of 26 November 2018, registrar Cloudflare.", "app.uniswap.org/.well-known/security.txt lists a Cantina bounty and security@uniswap.org with no Expires field; uniswap.org redirects to the app.", "status.uniswap.org redirects to app.uniswap.org/swap, so no status page is recorded.", "The privacy policy at app.uniswap.org draws by script and was not read. developers.uniswap.org/robots.txt disallows /dashboard, /api/ and /oauth/, so the key dashboard was not fetched; trade-api.gateway.uniswap.org has no robots.txt (404)." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/uniswap.json", "live": { "slug": "uniswap", "securityTxt": { "url": "https://uniswap.org/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:09.573484239Z" }, "updatedAt": "2026-11-04T15:53:09.573484239Z" } }, "edges": [ { "by": 12, "category": "transparency", "leads": "uniswap", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed service whose Terms of Use couldn't be read; the docs, connectors, CLI and skills are MIT on GitHub (10 of 30). The privacy notice couldn't be read, so no retention or subprocessor statement was checked; the prohibited-countries list is public and dated (5 of 30). The changelog gives retirement dates for SBE schemas and FIX fields months ahead (16 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 5 + 16 + 0 = 31.", "b": "The editorial half. The API is closed under API Terms of Use that answered 403; the SDKs and uniswap-ai are MIT and the protocol contracts are open source (15 of 30). No privacy policy read (app.uniswap.org draws by script) and nothing in the docs on retention of quotes or wallet addresses (0 of 30). A published sunset policy of at least 30 days, ideally 60, with dated notices such as the Universal Router 2.0 and 2.1.1 sunset of 21 October 2026 (20). No subprocessors or data locations (0 of 20). Total 35." }, "scores": { "a": 43, "b": 55 } }, { "by": 9, "category": "security", "leads": "binance", "name": "Security \u0026 auth", "reasons": { "a": "API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72.", "b": "A single `x-api-key` header, no scopes, no IP allow-list; revocation and rotation happen in a dashboard robots.txt disallows, so unchecked; nothing in a URL (18 of 30). The API never holds keys or funds, every value transfer needs the caller's signature on `permitData` and the transaction, and the swapper sets slippage (16 of 20). The API returns routes and token lists, not untrusted content (10). The dashboard presumably shows key usage; not read, and no per-call log is documented (5 of 15). security.txt on app.uniswap.org with a Cantina bounty and security@uniswap.org, protocol audits in the docs; no SOC 2 or disclosure timeline read (14 of 20). Total 63." }, "scores": { "a": 72, "b": 63 } }, { "by": 7, "category": "maintenance", "leads": "uniswap", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.", "b": "Read as a closed hosted service. The newest changelog notice is dated 22 October 2026 (30). Notices of 20 August, 21 September and 22 October 2026, three in 90 days (20). A help form for developer support that says it won't debug integrators' code, and uniswap-ai with 6 open issues and a push on 26 October (14 of 25). Official TypeScript SDKs current (@uniswap/v4-sdk 2.4.4 with provenance) and the uniswap-ai skills, though no client for the API itself; no MCP registry entry (15). Trusted publishing with provenance on npm, CI and lint hooks on uniswap-ai (9 of 10). Total 88." }, "scores": { "a": 81, "b": 88 } }, { "by": 5, "category": "payments", "leads": "uniswap", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35.", "b": "No machine payment protocol on the API's endpoints; the `pay-with-any-token` skill lets an agent pay other services' 402 challenges by swapping, which earns nothing here (0). The API is free, stated in the FAQ and the 16 April 2026 post, and integrator fees are capped at 500 bips (20). No card and no plan (20). A person creates an account in the dashboard to get a key (0). Total 40." }, "scores": { "a": 35, "b": 40 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Binance", "b": "Uniswap Labs", "name": "Vendor" }, { "a": "https://agent.binance.com/mcp/agentic", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT", "b": "The Trading API is a proprietary hosted service under Uniswap Labs' API Terms of Use, which we couldn't read; the SDKs and the uniswap-ai skills are MIT. Swaps execute on the open-source Uniswap protocol contracts on chain", "name": "Licence" }, { "a": "none", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-10-22", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no document linked", "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" }, { "a": "4.9k stars", "b": "236 stars, 154k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Uniswap Trading API and Binance API score within a point of each other on agent readiness, 63.3 (B) and 63.2 (B). Binance API leads on security \u0026 auth.", "question": "Which is better for AI agents, Binance API or Uniswap Trading API?" }, { "answer": "Binance API takes an API key or an OAuth sign-in. Uniswap Trading API needs an API key.", "question": "Do Binance API and Uniswap Trading API need an API key?" }, { "answer": "Binance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. No hosted endpoint is listed for Uniswap Trading API.", "question": "Can an agent call Binance API and Uniswap Trading API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 72 against 63" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.", "slug": "binance", "watchFor": "No status page or incident history found on binance.com or in the API docs" }, { "aheadOn": [ "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 88 against 81", "Transparency \u0026 trust, 55 against 43" ], "also": null, "goodFor": "An agent swapping or bridging tokens from its own wallet on 21 EVM chains, or managing liquidity positions, with routing done for it.", "slug": "uniswap", "watchFor": "No official MCP server; the registry's Uniswap entries are third parties" } ], "history": null, "job": { "capability": "exchange.spot-trading", "name": "Exchange spot trading" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.json", "title": "Bitfinex API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-uniswap.json", "title": "Bitget vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitget-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-uniswap.json", "title": "Bithumb Open API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-uniswap" }, { "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/bybit-vs-uniswap.json", "title": "Bybit vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bybit-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap.json", "title": "Crypto.com Exchange API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-uniswap.json", "title": "dYdX vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-uniswap" }, { "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/gemini-exchange-vs-uniswap.json", "title": "Gemini Exchange API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-uniswap.json", "title": "HTX trading API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/htx-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-uniswap.json", "title": "KuCoin vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-uniswap.json", "title": "MEXC API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/mexc-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitfinex.json", "title": "Binance API vs Bitfinex API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitfinex" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitget.json", "title": "Binance API vs Bitget", "url": "https://www.anchorterminal.com/compare/binance-vs-bitget" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bithumb.json", "title": "Binance API vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-bithumb" }, { "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-bybit.json", "title": "Binance API vs Bybit", "url": "https://www.anchorterminal.com/compare/binance-vs-bybit" }, { "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/binance-vs-coinbase-mcp.json", "title": "Binance API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.json", "title": "Binance API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-deribit.json", "title": "Binance API vs Deribit", "url": "https://www.anchorterminal.com/compare/binance-vs-deribit" }, { "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/binance-vs-gemini-exchange.json", "title": "Binance API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-htx.json", "title": "Binance API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/binance-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-hyperliquid.json", "title": "Binance API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/binance-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-kraken.json", "title": "Binance API vs Kraken API", "url": "https://www.anchorterminal.com/compare/binance-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-kucoin.json", "title": "Binance API vs KuCoin", "url": "https://www.anchorterminal.com/compare/binance-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-mexc.json", "title": "Binance API vs MEXC API", "url": "https://www.anchorterminal.com/compare/binance-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-okx.json", "title": "Binance API vs OKX API", "url": "https://www.anchorterminal.com/compare/binance-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-upbit.json", "title": "Binance API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-upbit" }, { "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-mcp-vs-uniswap.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-uniswap.json", "title": "Deribit vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/deribit-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.json", "title": "Hyperliquid vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-uniswap.json", "title": "Kraken API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/kraken-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/okx-vs-uniswap.json", "title": "OKX API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/okx-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/uniswap-vs-upbit.json", "title": "Uniswap Trading API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/uniswap-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-dydx.json", "title": "Binance API vs dYdX", "url": "https://www.anchorterminal.com/compare/binance-vs-dydx" } ], "panel": null, "scores": [ { "binance": 45, "by": 3, "edge": "binance", "key": "reliability", "name": "Reliability", "uniswap": 42, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "binance": 86, "by": 4, "edge": "uniswap", "key": "schema", "name": "Schema \u0026 documentation", "uniswap": 90, "weight": 13 }, { "binance": 76, "by": 4, "edge": "binance", "key": "ergonomics", "name": "Agent ergonomics", "uniswap": 72, "weight": 13 }, { "binance": 72, "by": 9, "edge": "binance", "key": "security", "name": "Security \u0026 auth", "uniswap": 63, "weight": 14 }, { "binance": 35, "by": 5, "edge": "uniswap", "key": "payments", "name": "Payments \u0026 pricing", "uniswap": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "binance": 81, "by": 7, "edge": "uniswap", "key": "maintenance", "name": "Maintenance \u0026 community", "uniswap": 88, "weight": 7 }, { "binance": 43, "by": 12, "edge": "uniswap", "key": "transparency", "name": "Transparency \u0026 trust", "uniswap": 55, "weight": 7 } ], "summary": "Uniswap Trading API and Binance API score within a point of each other on agent readiness, 63.3 (B) and 63.2 (B). Binance API leads on security \u0026 auth. Both do exchange spot trading.", "tasks": null, "tutorials": [], "verdicts": { "binance": "Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.", "uniswap": "The Trading API is free, documented by an OpenAPI file with stable error codes, holds no keys since the caller signs every swap, and posts sunset notices 30 days ahead. There is no official MCP server, status page or sandbox, the key is a plain header secret at 6 requests a second, and the API terms refused our reader." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/binance-vs-uniswap", "json": "https://www.anchorterminal.com/compare/binance-vs-uniswap.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/binance-vs-uniswap.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/binance-vs-uniswap.min.md" }, "markdown": "Uniswap Trading API and Binance API score within a point of each other on agent readiness, 63.3 (B) and 63.2 (B). Binance API leads on security \u0026 auth. Both do exchange spot trading.\n\n- Binance API: grade B, 63.2/100, rank #473 of 1349. Markdown https://www.anchorterminal.com/tools/binance.md · JSON https://www.anchorterminal.com/api/v1/tools/binance.json\n- Uniswap Trading API: grade B, 63.3/100, rank #470 of 1349. Markdown https://www.anchorterminal.com/tools/uniswap.md · JSON https://www.anchorterminal.com/api/v1/tools/uniswap.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### Binance API (B)\n\nGood for: An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.\n\nAhead on:\n- Security \u0026 auth, 72 against 63\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No status page or incident history found on binance.com or in the API docs\n\n### Uniswap Trading API (B)\n\nGood for: An agent swapping or bridging tokens from its own wallet on 21 EVM chains, or managing liquidity positions, with routing done for it.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 88 against 81\n- Transparency \u0026 trust, 55 against 43\n\nWatch for: No official MCP server; the registry's Uniswap entries are third parties\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Uniswap Trading API +12\n\n- Binance API (43): The editorial half. A closed service whose Terms of Use couldn't be read; the docs, connectors, CLI and skills are MIT on GitHub (10 of 30). The privacy notice couldn't be read, so no retention or subprocessor statement was checked; the prohibited-countries list is public and dated (5 of 30). The changelog gives retirement dates for SBE schemas and FIX fields months ahead (16 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 5 + 16 + 0 = 31.\n- Uniswap Trading API (55): The editorial half. The API is closed under API Terms of Use that answered 403; the SDKs and uniswap-ai are MIT and the protocol contracts are open source (15 of 30). No privacy policy read (app.uniswap.org draws by script) and nothing in the docs on retention of quotes or wallet addresses (0 of 30). A published sunset policy of at least 30 days, ideally 60, with dated notices such as the Universal Router 2.0 and 2.1.1 sunset of 21 October 2026 (20). No subprocessors or data locations (0 of 20). Total 35.\n\n### Security \u0026 auth: Binance API +9\n\n- Binance API (72): API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72.\n- Uniswap Trading API (63): A single `x-api-key` header, no scopes, no IP allow-list; revocation and rotation happen in a dashboard robots.txt disallows, so unchecked; nothing in a URL (18 of 30). The API never holds keys or funds, every value transfer needs the caller's signature on `permitData` and the transaction, and the swapper sets slippage (16 of 20). The API returns routes and token lists, not untrusted content (10). The dashboard presumably shows key usage; not read, and no per-call log is documented (5 of 15). security.txt on app.uniswap.org with a Cantina bounty and security@uniswap.org, protocol audits in the docs; no SOC 2 or disclosure timeline read (14 of 20). Total 63.\n\n### Maintenance \u0026 community: Uniswap Trading API +7\n\n- Binance API (81): Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.\n- Uniswap Trading API (88): Read as a closed hosted service. The newest changelog notice is dated 22 October 2026 (30). Notices of 20 August, 21 September and 22 October 2026, three in 90 days (20). A help form for developer support that says it won't debug integrators' code, and uniswap-ai with 6 open issues and a push on 26 October (14 of 25). Official TypeScript SDKs current (@uniswap/v4-sdk 2.4.4 with provenance) and the uniswap-ai skills, though no client for the API itself; no MCP registry entry (15). Trusted publishing with provenance on npm, CI and lint hooks on uniswap-ai (9 of 10). Total 88.\n\n### Payments \u0026 pricing: Uniswap Trading API +5\n\n- Binance API (35): No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35.\n- Uniswap Trading API (40): No machine payment protocol on the API's endpoints; the `pay-with-any-token` skill lets an agent pay other services' 402 challenges by swapping, which earns nothing here (0). The API is free, stated in the FAQ and the 16 April 2026 post, and integrator fees are capped at 500 bips (20). No card and no plan (20). A person creates an account in the dashboard to get a key (0). Total 40.\n\n## Score by category\n\n| Category | Weight | Binance API | Uniswap Trading API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 42 | Binance API +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 90 | Uniswap Trading API +4 |\n| Agent ergonomics | 13% (16.2 this run) | 76 | 72 | Binance API +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 63 | Binance API +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Uniswap Trading API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 88 | Uniswap Trading API +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 43 | 55 | Uniswap Trading API +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.2 · B** | **63.3 · B** | |\n\n## Facts side by side\n\n| Fact | Binance API | Uniswap Trading API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Binance | Uniswap Labs |\n| Hosted endpoint | `https://agent.binance.com/mcp/agentic` | no (local only) |\n| Transports | Streamable HTTP | |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| Licence | Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT | The Trading API is a proprietary hosted service under Uniswap Labs' API Terms of Use, which we couldn't read; the SDKs and the uniswap-ai skills are MIT. Swaps execute on the open-source Uniswap protocol contracts on chain |\n| Tools exposed | none | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-30 | 2026-10-22 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | no document linked |\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| Popularity | 4.9k stars | 236 stars, 154k npm/wk |\n\n## Verdicts\n\n**Binance API.** Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.\n\n**Uniswap Trading API.** The Trading API is free, documented by an OpenAPI file with stable error codes, holds no keys since the caller signs every swap, and posts sunset notices 30 days ahead. There is no official MCP server, status page or sandbox, the key is a plain header secret at 6 requests a second, and the API terms refused our reader.\n\n## Before you call either\n\n### Binance API\n\n1. Read the X-MBX-USED-WEIGHT and X-MBX-ORDER-COUNT headers and stop on 429 for the Retry-After seconds; a 418 ban runs 2 minutes to 3 days\n2. Treat a 5xx on an order as unknown, not failed, and query the order by origClientOrderId before retrying\n3. Use an Ed25519 key with an IP restriction and only the reading and trading permissions; never enable withdrawals for an agent key\n4. Develop on testnet.binance.vision with BINANCE_API_ENV=testnet; it resets about monthly without notice\n5. For the MCP route, the person must fund the Agentic sub-account from the web UI first; the agent cannot move funds in from the main account\n\n### Uniswap Trading API\n\n1. Call `/check_approval` first, then `/quote`; if `permitData` is non-null sign it as EIP-712 and send `signature` and `permitData` together to `/swap` or `/order`, never one without the other\n2. Route on the quote's `routing`: `CLASSIC`, `WRAP`, `UNWRAP` and `BRIDGE` go to `/swap`, `DUTCH_V2`, `DUTCH_V3` and `PRIORITY` to `/order`, `CHAINED` to `/plan`\n3. Refresh any quote older than 30 seconds before broadcasting, and on 429 pause every request from the key before retrying\n4. Retry unchanged only on `UpstreamTimeoutError`; `NoRouteFoundError` and `QuoteAmountTooLowError` need a different amount, token or `protocols` list\n5. Send `X-Agent-Info` with `decision_origin: autonomous` and keep `x-api-key` server-side\n\n## Questions\n\n### Which is better for AI agents, Binance API or Uniswap Trading API?\n\nUniswap Trading API and Binance API score within a point of each other on agent readiness, 63.3 (B) and 63.2 (B). Binance API leads on security \u0026 auth.\n\n### Do Binance API and Uniswap Trading API need an API key?\n\nBinance API takes an API key or an OAuth sign-in. Uniswap Trading API needs an API key.\n\n### Can an agent call Binance API and Uniswap Trading API without installing anything?\n\nBinance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. No hosted endpoint is listed for Uniswap Trading API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/binance-vs-uniswap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/binance-vs-uniswap.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"binance\", \"b\": \"uniswap\"}`. From a terminal: `anchor compare binance uniswap`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/binance.json and https://www.anchorterminal.com/api/v1/tools/uniswap.json\n\n## Other comparisons with Binance API or Uniswap Trading API\n\n- [Bitfinex API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.md)\n- [Bitget vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitget-vs-uniswap.md)\n- [Bithumb Open API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bithumb-vs-uniswap.md)\n- [Bitstamp API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.md)\n- [Bybit vs Uniswap Trading API](https://www.anchorterminal.com/compare/bybit-vs-uniswap.md)\n- [Crypto.com Exchange API vs Uniswap Trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap.md)\n- [dYdX vs Uniswap Trading API](https://www.anchorterminal.com/compare/dydx-vs-uniswap.md)\n- [Gate vs Uniswap Trading API](https://www.anchorterminal.com/compare/gate-io-vs-uniswap.md)\n- [Gemini Exchange API vs Uniswap Trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-uniswap.md)\n- [HTX trading API vs Uniswap Trading API](https://www.anchorterminal.com/compare/htx-vs-uniswap.md)\n- [KuCoin vs Uniswap Trading API](https://www.anchorterminal.com/compare/kucoin-vs-uniswap.md)\n- [MEXC API vs Uniswap Trading API](https://www.anchorterminal.com/compare/mexc-vs-uniswap.md)\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)\n- [Binance API vs Bitget](https://www.anchorterminal.com/compare/binance-vs-bitget.md)\n- [Binance API vs Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md)\n- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.md)\n- [Binance API vs Bybit](https://www.anchorterminal.com/compare/binance-vs-bybit.md)\n- [Binance API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.md)\n- [Binance API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.md)\n- [Binance API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.md)\n- [Binance API vs Deribit](https://www.anchorterminal.com/compare/binance-vs-deribit.md)\n- [Binance API vs Gate](https://www.anchorterminal.com/compare/binance-vs-gate-io.md)\n- [Binance API vs Gemini Exchange API](https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Binance API vs Hyperliquid](https://www.anchorterminal.com/compare/binance-vs-hyperliquid.md)\n- [Binance API vs Kraken API](https://www.anchorterminal.com/compare/binance-vs-kraken.md)\n- [Binance API vs KuCoin](https://www.anchorterminal.com/compare/binance-vs-kucoin.md)\n- [Binance API vs MEXC API](https://www.anchorterminal.com/compare/binance-vs-mexc.md)\n- [Binance API vs OKX API](https://www.anchorterminal.com/compare/binance-vs-okx.md)\n- [Binance API vs Upbit Open API](https://www.anchorterminal.com/compare/binance-vs-upbit.md)\n- [Coinbase Advanced Trade API vs Uniswap Trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Uniswap Trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-uniswap.md)\n- [Deribit vs Uniswap Trading API](https://www.anchorterminal.com/compare/deribit-vs-uniswap.md)\n- [Hyperliquid vs Uniswap Trading API](https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.md)\n- [Kraken API vs Uniswap Trading API](https://www.anchorterminal.com/compare/kraken-vs-uniswap.md)\n- [OKX API vs Uniswap Trading API](https://www.anchorterminal.com/compare/okx-vs-uniswap.md)\n- [Uniswap Trading API vs Upbit Open API](https://www.anchorterminal.com/compare/uniswap-vs-upbit.md)\n- [Binance API vs dYdX](https://www.anchorterminal.com/compare/binance-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": "Binance API vs Uniswap Trading API", "url": "" } ], "description": "Uniswap Trading and Binance score within a point of each other for exchange spot trading, 63.3 and 63.2 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Binance API B 63.2", "Uniswap Trading API B 63.3", "scores" ], "h1": "Binance API vs Uniswap Trading API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/binance-vs-uniswap", "published": "2026-10-01", "section": "tools", "title": "Binance vs Uniswap Trading for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/binance-vs-uniswap" }, "tokens": { "markdown": 4100, "slim": 1830 }, "version": 1 }