# Hyperliquid vs Uniswap Trading API (slim)

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

- Full: https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.md (~4,200 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.json · canonical https://www.anchorterminal.com/compare/hyperliquid-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 Hyperliquid's 50 (D), and leads in 5 of 7 scored categories. Hyperliquid leads on payments & pricing. Both do exchange spot trading.

- Hyperliquid: D 50, rank #966 of 1349 · https://www.anchorterminal.com/tools/hyperliquid.min.md
- Uniswap Trading API: B 63.3, rank #470 of 1349 · https://www.anchorterminal.com/tools/uniswap.min.md
- Hyperliquid, good for An agent trading perpetuals or spot on chain from its own wallet with no account, or acting for a master account through an approved API wallet. Ahead on Payments & pricing, 55 against 40.
- 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 42; Maintenance & community, 88 against 39; Transparency & trust, 55 against 26. Also Free to start without a card.

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

| Fact (where they differ) | Hyperliquid | Uniswap Trading API |
| --- | --- | --- |
| Vendor | Hyperliquid Labs | Uniswap Labs |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Free |
| Licence | The exchange runs on the Hyperliquid chain (HyperCore), whose node is distributed as a binary under an Apache-2.0 repository; the Python and Rust SDKs are MIT. The API servers and front end are closed | 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-06-04 | 2026-10-22 |
| Popularity | 1.9k stars, 167k PyPI/wk | 236 stars, 154k npm/wk |

Why the edge:
- Maintenance & community, Uniswap Trading API +49: Hyperliquid 39 (Read as a closed hosted service with open SDKs. The API has no dated changelog, so the last dated change is the Python SDK's 0.24.0 on 4 June 2026, 152 days before this check; the node repository was pushed on 10 August 2026 and the docs describe newer actions (HIP-4 outcome markets, borrow and lend) without dates. Judgement call (10 of 30). No three dated releases in 90 days (0). Support through Discord and the docs' FAQ, 112 open issues on the SDK whose replies couldn't be read (8 of 25). Official Python and Rust SDKs, the Rust one last pushed 21 October 2025; no MCP registry entry (15). CI on Python 3.9 and 3.13 with Poetry, Dependabot badge, a lock file (6 of 10). Total 39.); 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.)
- Schema & documentation, Uniswap Trading API +48: Hyperliquid 42 (No OpenAPI or other machine-readable contract; request and response shapes are tables and JSON examples in the docs (0 of 25). llms.txt and a Markdown twin of every page by appending .md (10). Each info type and exchange action has a short description of what it does, and the signing page lists common mistakes, but little says when to use one call over another (12 of 20). Fields are one-letter keys (`a`, `b`, `p`, `s`, `r`, `t`, `c`) with numbers as strings, enums such as `tif` Alo, Ioc or Gtc, and required fields marked in tables (9 of 15). An example for every call and a list of order and cancel error strings, with no HTTP error table (11 of 15). No API version, no changelog and no dated release notes; deprecated actions such as `userDexAbstraction` are marked in place (0 of 15). Total 42.); 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.)
- Transparency & trust, Uniswap Trading API +29: Hyperliquid 26 (The editorial half. The SDKs are MIT and the node repository Apache-2.0 with a Dockerfile around a binary; the API servers and front end are closed and the terms were unreadable (12 of 30). No privacy policy read and nothing in the docs on data handling (0 of 30). Deprecated actions are marked in the docs without dates or a policy (8 of 20). No subprocessors or data locations (0 of 20). Total 20.); 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.)
- Payments & pricing, Hyperliquid +15: Hyperliquid 55 (No machine payment protocol (0). Fees published per tier without login (20). No card anywhere; public info endpoints are free and the testnet faucet gives 1,000 mock USDC, though only to an address that has deposited on mainnet (15 of 20). No signup; an agent with a funded EVM wallet deposits USDC on a bridged chain and trades, subject to the unread terms (20). Total 55.); 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.)