About Orderbook Depth X402
Orderbook Depth X402 is an MCP-accessible API for analyzing liquidity in Uniswap V3 pools, intended for agents assessing trades. It returns price-impact depth and pool details, with pay-per-call access through x402 using USDC on Base.
Key features
- 01Analyze Uniswap V3 pool depth
- 02Estimate liquidity at 1–10% impact
- 03Return price and pool details
- 04Pay per call with USDC on Base
Use cases
- 01Estimate slippage before a large trade
- 02Assess liquidity to size a trade
- 03Inspect a pool's price and fee tier
MCP support
The remote MCP server exposes `dex_analyze_orderbook_depth` for GET and POST requests. Calls use x402 pay-per-call payments in USDC on Base.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://orderbook-depth.api.klymax402.com/mcpclaude mcp add --transport sse orderbook-depth-x402 https://orderbook-depth.api.klymax402.com/mcp{"mcpServers":{"orderbook-depth-x402":{"type":"sse","url":"https://orderbook-depth.api.klymax402.com/mcp"}}}Open in Cursor{"servers":{"orderbook-depth-x402":{"type":"sse","url":"https://orderbook-depth.api.klymax402.com/mcp"}}}Open in VS Code{"mcpServers":{"orderbook-depth-x402":{"type":"sse","url":"https://orderbook-depth.api.klymax402.com/mcp"}}}{"mcpServers":{"orderbook-depth-x402":{"serverUrl":"https://orderbook-depth.api.klymax402.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEOrder Book Depth API
Uniswap V3 liquidity depth analysis -- price impact at 1/2/5/10% levels. Slippage estimation pre-trade. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"orderbook-depth": {
"url": "https://orderbook-depth.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
curl "https://orderbook-depth.api.klymax402.com/api/depth?pool=..."
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
dex_analyze_orderbook_depth | GET | /api/depth | $0.012 | Analyze orderbook depth for a Uniswap V3 pool |
dex_analyze_orderbook_depth | POST | /api/depth | $0.012 | Analyze orderbook depth for a Uniswap V3 pool (POST variant) |
dex_analyze_orderbook_depth
Use this when you need to analyze liquidity depth of a Uniswap V3 pool before a large trade. Returns depth analysis in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
pool | string | yes | Uniswap V3 pool address (0x...) |
chain | string | no | Chain name: base, ethereum (default: base) |
Returns
currentPrice-- current pool pricedepth1pct-- USD liquidity available within 1% price impactdepth2pct-- USD liquidity available within 2% price impactdepth5pct-- USD liquidity available within 5% price impactdepth10pct-- USD liquidity available within 10% price impacttotalLiquidity-- total pool liquidity in USDfeeTier-- pool fee tier (0.01%, 0.05%, 0.3%, 1%)token0/token1-- pool token pair symbols
Example response:
{"currentPrice":3128.50,"depth1pct":850000,"depth2pct":2100000,"depth5pct":5400000,"depth10pct":9800000,"totalLiquidity":15200000,"feeTier":"0.3%","token0":"USDC","token1":"WETH"}
When to use: executing large on-chain trades to estimate slippage and determine optimal trade size. Essential for MEV-aware agents and OTC sizing.
Not for: swap quotes (use dex_get_swap_quote), token safety (use token_check_safety), token holders (use token_get_holder_analysis).
dex_analyze_orderbook_depth
Use this when you need to analyze liquidity depth of a Uniswap V3 pool before a large trade. Returns depth analysis in JSON. POST variant of dex_analyze_orderbook_depth -- same params passed as JSON body instead of query string.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
pool | string | yes | Uniswap V3 pool address (0x...) |
chain | string | no | Chain name: base, ethereum (default: base) |
Returns
currentPrice-- current pool pricedepth1pct-- USD liquidity available within 1% price impactdepth2pct-- USD liquidity available within 2% price impactdepth5pct-- USD liquidity available within 5% price impactdepth10pct-- USD liquidity available within 10% price impacttotalLiquidity-- total pool liquidity in USDfeeTier-- pool fee tier (0.01%, 0.05%, 0.3%, 1%)token0/token1-- pool token pair symbols
Example response:
{"currentPrice":3128.50,"depth1pct":850000,"depth2pct":2100000,"depth5pct":5400000,"depth10pct":9800000,"totalLiquidity":15200000,"feeTier":"0.3%","token0":"USDC","token1":"WETH"}
When to use: executing large on-chain trades to estimate slippage and determine optimal trade size. Essential for MEV-aware agents and OTC sizing.
Not for: swap quotes (use dex_get_swap_quote), token safety (use token_check_safety), token holders (use token_get_holder_analysis).
Example agent prompts
- "Analyze liquidity depth of a Uniswap V3 pool before a large trade"
- "Analyze liquidity depth of a Uniswap V3 pool before a large trade"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.