# Deribit vs Uniswap Trading API (slim)

> Uniswap Trading scores 63.3 (B) to Deribit's 59 (C) for exchange spot trading. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/deribit-vs-uniswap.md (~3,700 tokens) · this version ~1,530 tokens · JSON https://www.anchorterminal.com/compare/deribit-vs-uniswap.json · canonical https://www.anchorterminal.com/compare/deribit-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-04
- 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 Deribit's 59 (C), and leads in 5 of 7 scored categories. Both do exchange spot trading.

- Deribit: C 59, rank #646 of 1349 · https://www.anchorterminal.com/tools/deribit.min.md
- Uniswap Trading API: B 63.3, rank #470 of 1349 · https://www.anchorterminal.com/tools/uniswap.min.md
- Deribit, good for An agent trading crypto options, dated futures and perpetuals for an institutional or retail Deribit account, and anyone migrated from Coinbase International Exchange.
- 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 Payments & pricing, 40 against 25; Maintenance & community, 88 against 65; Transparency & trust, 55 against 46. Also Free to start without a card.

| Category | Deribit | Uniswap Trading API |
| --- | --- | --- |
| Reliability (16%) | 45 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 88 | 90 |
| Agent ergonomics (13%) | 74 | 72 |
| Security & auth (14%) | 62 | 63 |
| Payments & pricing (10%) | 25 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 65 | 88 |
| Transparency & trust (7%) | 46 | 55 |

| Fact (where they differ) | Deribit | Uniswap Trading API |
| --- | --- | --- |
| Vendor | Deribit FZE | Uniswap Labs |
| Pricing | Pay per use | Free |
| Licence | Proprietary hosted exchange. The API is documented under the Deribit docs with an OpenAPI 3.0 file; no official client library is published | 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 |
| Last release | 2026-10-13 | 2026-10-22 |
| Terms last updated | 2026-08-13 | couldn't be read |
| 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 | 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 | 236 stars, 154k npm/wk |

Why the edge:
- Maintenance & community, Uniswap Trading API +23: Deribit 65 (Read as a closed service. The JSON-RPC changelog's latest production entry is 13 October 2026 and an entry dated 5 November 2026 describes the next release; Deribit's posts of 14 October and 2 November 2026 change fees (30). Entries of 18 August, 15 September and 13 October 2026, three in 90 days (20). A public changelog and a support site; whether support answers wasn't tested and the support site refused our reader (10 of 15). No official SDK and no MCP registry entry (0). The OpenAPI and AsyncAPI files are maintained with the docs (5 of 10). Total 65.); 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 +15: Deribit 25 (No machine payment protocol (0). The fee schedule is on support.deribit.com, which answered 403; Deribit's own posts give VIP4 to VIP7 taker fees and the 0 bps linear options maker fee, so partial prices are public but the lowest tier is unchecked (5 of 20). Public market data needs no key and the test environment is free, with no card anywhere (20). A person signs up in a browser with identity checks before any key exists (0). Total 25.); 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.)
- Transparency & trust, Uniswap Trading API +9: Deribit 46 (The editorial half. A closed service whose terms (Deribit FZE membership terms and DRB Panama Inc. terms) sit on a support site that answered 403, with the entity confirmed on VARA's register (12 of 30). The privacy policy was not read, and nothing in the docs states retention (0 of 30). The changelog marks deprecations and the upcoming docs branch previews the next release, but removals such as `public/get_index` on 25 November 2025 carry no notice period (10 of 20). No subprocessor or data-location statement found (0 of 20). Total 22.); 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.)