# MEXC API vs Uniswap Trading API (slim)

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

- Full: https://www.anchorterminal.com/compare/mexc-vs-uniswap.md (~4,150 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/compare/mexc-vs-uniswap.json · canonical https://www.anchorterminal.com/compare/mexc-vs-uniswap
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-03
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Uniswap Trading API scores 63.3 (B) on agent readiness against MEXC API's 56.3 (C), and leads in 4 of 7 scored categories. Both do exchange market data.

- MEXC API: C 56.3, rank #791 of 1349 · https://www.anchorterminal.com/tools/mexc.min.md
- Uniswap Trading API: B 63.3, rank #446 of 1349 · https://www.anchorterminal.com/tools/uniswap.min.md
- MEXC API, good for Spot and futures for agents in served countries that want a vendor-built MCP server with read-only and confirmation modes. Also Runs on your own machine.
- Uniswap Trading API, good for An agent swapping or bridging tokens from its own wallet on 21 EVM chains, or managing liquidity positions, with routing done for it. Ahead on Schema & documentation, 90 against 64; Agent ergonomics, 72 against 64; Payments & pricing, 40 against 31; Maintenance & community, 88 against 75. Also Free to start without a card.

| Category | MEXC API | Uniswap Trading API |
| --- | --- | --- |
| Reliability (16%) | 43 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 90 |
| Agent ergonomics (13%) | 64 | 72 |
| Security & auth (14%) | 65 | 63 |
| Payments & pricing (10%) | 31 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 88 |
| Transparency & trust (7%) | 58 | 55 |

| Fact (where they differ) | MEXC API | Uniswap Trading API |
| --- | --- | --- |
| Vendor | MEXC (Comoros) Ltd | Uniswap Labs |
| Transports | stdio |  |
| Pricing | Pay per use | Free |
| Licence | none | The Trading API is a proprietary hosted service under Uniswap Labs' API Terms of Use, which we couldn't read; the SDKs and the uniswap-ai skills are MIT. Swaps execute on the open-source Uniswap protocol contracts on chain |
| Tools exposed | 299 | 0 |
| Read-only variant documented | yes | no |
| Last release | 2026-10-23 | 2026-10-22 |
| Terms last updated | 2026-10-13 | couldn't be read |
| Privacy policy last updated | 2026-06-01 | no document linked |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 315 stars | 236 stars, 154k npm/wk |

Why the edge:
- Schema & documentation, Uniswap Trading API +26: MEXC API 64 (No OpenAPI found; a Postman collection and the CLI's 25 capability reference files are the nearest machine-readable contract (5 of 25). llms.txt on mexc.com, written for assistants and pointing at the API docs and legal pages (7 of 10). Per-endpoint pages with purpose, parameters and permissions, without when-not-to-use guidance (13 of 20). Typed parameters with enums for order types, statuses and intervals (11 of 15). Examples on each endpoint and a separate error-code page with numeric codes and messages (13 of 15). Versioned API (v3) with a dated changelog of 72 entries to 23 October 2026 (15). 5 + 7 + 13 + 11 + 13 + 15 = 64.); Uniswap Trading API 90 (OpenAPI 3.0 file (Token Trading 1.0.0) for the Trading and LP APIs, about 33 paths with `x-internal` markers on the margin and 4337 operations (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation summaries are one line, but the guides say which routing types go to `/swap`, `/order` and `/plan`, when UniswapX quotes are returned and when a 404 means change the request (14 of 20). Enums for routing types, urgency and position statuses, required fields and bounded integers such as `limit` 1 to 20 (12 of 15). Examples on every guide page and error schemas for 400, 401, 404 and 429 with a stable `errorCode` enum and per-code retry advice (14 of 15). A /v1 path, a changelog with posted and effective dates and a 30-day minimum sunset policy (15). Total 90.)
- Maintenance & community, Uniswap Trading API +13: MEXC API 75 (Read as a closed service. Last dated change 23 October 2026 in both the spot and futures logs (30). Spot entries on 14 August, 24 August, 11 September and 23 October 2026, futures on 1 September, 11 September, 19 October and 23 October (20). An API support Telegram group, a ticket form and dated changelogs; GitHub issues not read (10 of 15). The official SDK repository was last pushed in February 2024 while the CLI is current (10 of 15). The CLI ships platform binaries with no dependencies and no public repository or CI; the SDK is stale (5 of 10). 30 + 20 + 10 + 10 + 5 = 75.); 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.)
- Payments & pricing, Uniswap Trading API +9: MEXC API 31 (No machine payment protocol (0). Fees published without login on MEXC's own fee guide (20 October 2026) and a 2024 announcement, with a separate API futures schedule; the fee page itself is drawn by script (16 of 20). Public market data needs no key or card; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser, and futures need identity verification (0). 0 + 16 + 15 + 0 = 31.); Uniswap Trading API 40 (No machine payment protocol on the API's endpoints; the `pay-with-any-token` skill lets an agent pay other services' 402 challenges by swapping, which earns nothing here (0). The API is free, stated in the FAQ and the 16 April 2026 post, and integrator fees are capped at 500 bips (20). No card and no plan (20). A person creates an account in the dashboard to get a key (0). Total 40.)
- Agent ergonomics, Uniswap Trading API +8: MEXC API 64 (Graded on the REST API with the CLI's MCP mode. Responses take limit parameters and the MCP read-only market subset is 22 tools, but a full spot MCP category lists 123 tools (15 of 25). startTime, endTime and limit on history, symbol filters on open orders (14 of 20). Numeric codes with messages, a 30035 order-limit code added 23 October 2026, 5xx guidance (14 of 20). newClientOrderId is optional with no idempotency guarantee; the CLI adds --dry-run and a confirmation step (10 of 20). Few required parameters; SDKs in five languages whose repository was last pushed in February 2024 (11 of 15). 15 + 14 + 14 + 10 + 11 = 64.); Uniswap Trading API 72 (An API, read for response sizing. Quotes and calldata are compact and `/tokens` takes a limit; the quote can carry the swap calldata to save a call (20 of 25). `GET /orders` and `GET /swaps` poll status by id, `/swappable_tokens` and `/tokens` filter by chain and sort, with little pagination elsewhere (12 of 20). Stable `errorCode` values with a `detail` string and a `requestId`, and the docs say which codes to retry (18 of 20). No idempotency key; a swap is a signed transaction whose nonce prevents a double spend, and the docs warn about nonce collisions with pending transactions (12 of 20). Few required fields on `/quote`, defaults for slippage and urgency, but no official client library for the API and signing needs ethers.js, viem or web3.js (10 of 15). Total 72.)