x402 support is currently in beta. Endpoints, pricing, and supported networks may change. Join the Mobula Telegram to report issues or share feedback.
/x402/market/details endpoint provides real-time DEX pool and token market data, gated by a $0.001 USDC micropayment using the x402 payment protocol. No API key required — payment is the credential.
This endpoint is identical to Get Market Details but uses pay-per-use access instead of API key authentication. It is designed for AI agents, autonomous scripts, and any x402-compatible client.
Supported Networks
Payment is accepted in USDC on:| Network | CAIP-2 |
|---|---|
| Base mainnet | eip155:8453 |
| Solana mainnet | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
Price Per Call
$0.001 USDC per request, settled on-chain via the Coinbase CDP Facilitator.Query Parameters
| Parameter | Required | Description |
|---|---|---|
address | Yes | Pool or token contract address. EVM: checksummed hex (0x…). Solana: base58 address. Pass a DEX pool address for exact pool data, or a token address to resolve the most liquid pool automatically. |
blockchain | Yes | Blockchain identifier. Accepted formats: full name (Ethereum, Solana), short code (eth, sol), CAIP-2 (eip155:1), or numeric chain ID (1, 56, 8453). |
baseToken | No | Override which token in the pair is treated as base for price calculations. Pass the contract address of the desired base token. |
currencies | No | Comma-separated currency codes for additional price fields. Example: EUR,GBP,BTC. USD is always included. |
How x402 Payment Works
The x402 protocol follows a standard two-step flow: Step 1 — Request without payment (receives 402)payment-required header contains the accepted payment options (network, asset, amount, receiving address).
Step 2 — Sign and retry with payment header
Your x402-compatible client reads the payment-required header, signs a USDC transfer, and retries with the x-payment header:
What the Response Includes
The response is identical to the standard Market Details endpoint:priceUSD/priceToken— current price of the base tokenliquidityUSD— total liquidity in the pool in USDbase/quote— full token metadata for both sides of the pair (symbol, name, logo, marketCapUSD, circulatingSupply, approximateReserveUSD, security flags, holder stats)priceChange*— price change percentages across 1m, 5m, 1h, 4h, 6h, 12h, 24hvolume*/volumeBuy*/volumeSell*— volume metrics across all timeframestrades*/buys*/sells*/buyers*/sellers*/traders*— trade and participant countsholdersCount— number of unique holderssecurity— honeypot status, buy/sell tax, renounced, mintable flagssocials— Twitter, website, Telegram links when availableexchange— exchange name and logo
Using with AI Agents
Any agent or autonomous script using an x402-compatible HTTP client automatically handles the 402 → sign → retry flow. Thepayment-required response embeds the full type schema of the response (via the Bazaar extension), so agents know exactly what fields to expect before paying.
Compatible client libraries:
@x402/core— TypeScript/JavaScript@x402/evm— EVM (Base) payment signing@x402/svm— Solana payment signing
Testing
Two test scripts are included in the repository for end-to-end testing of the full 402 → sign → settle flow. Both scripts accept anENDPOINT env var to target any x402 route.
Prerequisites
Solana mainnet- Solana wallet private key in base58 format (export from Phantom or Backpack)
- USDC on Solana mainnet at
EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
- EVM wallet private key (
0x-prefixed) - USDC on Base mainnet at
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 - ETH on Base for gas
Run the test
Solana:/tmp/x402-response.json.