Head to head · Exchange spot trading · October 2026 research run

Hyperliquid vs Uniswap Trading API

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.

Best crypto exchange APIs and MCP servers for AI agents · All 210 exchanges comparisons

Which one, for what

Hyperliquid D

Best 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

Watch for

No official MCP server; the 23 registry entries are all third parties, several selling data by x402

Uniswap Trading API B

Best 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 in its favour

  • Free to start without a card

Watch for

No official MCP server; the registry's Uniswap entries are third parties

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 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.

Score by category

CategoryWeight this runHyperliquidUniswap Trading APIEdge
Reliability16%204042Uniswap Trading API +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24290Uniswap Trading API +48
Agent ergonomics13%16.27072Uniswap Trading API +2
Security & auth14%17.56463Hyperliquid +1
Payments & pricing10%12.55540Hyperliquid +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83988Uniswap Trading API +49
Transparency & trust7%8.82655Uniswap Trading API +29
Negative events≤1500
TotalD 50/100B 63.3/100

Facts side by side

FactHyperliquidUniswap Trading API
KindHTTP APIHTTP API
VendorHyperliquid LabsUniswap Labs
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyAPI key
PricingPay per useFree
x402nono
LicenceThe 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 closedThe 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 exposed00
Read-only variant documentednono
llms.txtyesyes
Last release2026-06-042026-10-22
Terms last updatedcouldn't be readcouldn't be read
Privacy policy last updatedno document linkedno document linked
Customer content may train modelscouldn't be readcouldn't be read
Terms restrict automated accesscouldn't be readcouldn't be read
Terms restrict benchmarkingcouldn't be readcouldn't be read
Terms or service can change without noticecouldn't be readcouldn't be read
Arbitration or class-action waivercouldn't be readcouldn't be read
Popularity1.9k stars, 167k PyPI/wk236 stars, 154k npm/wk

Verdicts

Hyperliquid

Hyperliquid's API needs no signup or key, an approved API wallet can trade but not withdraw, fees and rate limits are published with numbers, and a testnet mirrors mainnet. There is no official MCP server, OpenAPI file, status page, changelog or readable terms, and signing uses two schemes the docs say to leave to an SDK.

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.

Before you call either

Hyperliquid

  1. Generate a fresh API wallet, approve it with approveAgent with a name and expiry, sign with it, and query with the master address, never the agent address
  2. Use the Python SDK's sign_l1_action and sign_user_signed_action; mixing the two, field order in msgpack or an uppercase address gives "User or API Wallet ... does not exist"
  3. Set a cloid on every order and read the per-order statuses array; one batch-level error rejects the whole batch
  4. Budget address limits by volume (one action per 1 USDC traded after 10,000); batch orders to lower IP weight, and use WebSocket for data
  5. Arm scheduleCancel before unattended trading so open orders are cancelled if the agent stops

Uniswap Trading API

  1. 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
  2. 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
  3. Refresh any quote older than 30 seconds before broadcasting, and on 429 pause every request from the key before retrying
  4. Retry unchanged only on UpstreamTimeoutError; NoRouteFoundError and QuoteAmountTooLowError need a different amount, token or protocols list
  5. Send X-Agent-Info with decision_origin: autonomous and keep x-api-key server-side

Questions

Which is better for AI agents, Hyperliquid or Uniswap Trading API?

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.

Do Hyperliquid and Uniswap Trading API need an API key?

Hyperliquid takes an API key or an OAuth sign-in. Uniswap Trading API needs an API key.

Can an agent call Hyperliquid and Uniswap Trading API without installing anything?

No hosted endpoint is listed for Hyperliquid. No hosted endpoint is listed for Uniswap Trading API.

Other comparisons with Hyperliquid or Uniswap Trading API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.