x402 support is currently in beta. Endpoints, pricing, and supported networks may change. Join the Mobula Telegram to report issues or share feedback.
/x402/cefi/funding-rate endpoint provides live CeFi perpetual funding rates across all major exchanges, 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 CeFi Funding Rate but uses pay-per-use access instead of API key authentication. It is designed for AI agents, quant 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 |
|---|---|---|
symbol | Yes | Base asset ticker. Examples: BTC, ETH, SOL, BNB. Case-insensitive. Do not include the quote currency (USDT, USD) here. |
quote | No | Quote asset override. Default is USDT. Examples: USD, USDC. |
exchange | No | Comma-separated list of exchanges to query. Omit to fetch from all supported exchanges. Supported values: binance, bybit, deribit, okx, hyperliquid, gate, lighter. |
Supported Exchanges
| Exchange | Coverage |
|---|---|
| Binance | USDT-margined perpetuals |
| Bybit | Linear perpetuals |
| Deribit | Options and perpetuals |
| OKX | USDT/USDC swaps |
| Hyperliquid | Decentralized perpetuals |
| Gate.io | USDT perpetuals |
| Lighter | On-chain orderbook perps |
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
Per-exchange entries are returned as arrays, each containing:symbol— perpetual contract ticker as used on that exchange (e.g.BTCUSDT,BTC-USDT-SWAP)fundingRate— current funding rate as a decimal (e.g.0.0001= 0.01% per epoch)fundingTime— next settlement timestamp in Unix millisecondsepochDurationMs— duration of each funding epoch in millisecondsmarketPrice— current mark price on that exchange (where available)
queryDetails field echoes back the requested base and quote.
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.