x402 Micropayments

For crypto-native agents and developers, Rekko supports x402 — the HTTP 402 payment protocol. Pay per request with USDC stablecoins on Base L2 instead of subscribing.

How it works

Make a request without an API key
Rekko returns HTTP 402 Payment Required with a payment envelope
Your x402 client automatically pays the USDC amount and retries
The response comes back as normal

Pricing

Per-call pricing matches the subscription tiers:

Tier	USDC per call
LISTING	$0.01
INSIGHT	$0.10
STRATEGY	$2.00
DEEP	$5.00

Setup

Fund a wallet on Base L2

You need a wallet with USDC on Base (Coinbase’s L2 network). Bridge from Ethereum mainnet or purchase directly.

Install an x402 client

Use the RekkoClient from the rekko-skill repo, or any x402-compatible HTTP client:

pip install httpx "x402[fastapi]" eth-account

Make requests

from eth_account import Account
from rekko_tools import RekkoClient

signer = Account.from_key("0x<your-private-key>")
async with RekkoClient(signer=signer) as client:
    markets = await client.list_markets()

Or set X402_PRIVATE_KEY in your environment for auto-detection. Payments are handled automatically per request.

When to use x402

No subscription commitment — pay only for what you use
Agent-native — autonomous agents can self-fund from a wallet
Pseudonymous — no email signup required
Composable — works alongside other x402-enabled APIs

When to use a subscription instead

If you make more than ~100 LISTING calls per month, the Free tier is more cost-effective. For heavy usage, the Pro plan ($49/mo) includes thousands of calls.

MCP Server

RapidAPI

OpenClaw

Postman

Crypto Payments

x402 Micropayments

How it works

Pricing

Setup

When to use x402

When to use a subscription instead

​How it works

​Pricing

​Setup

​When to use x402

​When to use a subscription instead

How it works

Pricing

Setup

When to use x402

When to use a subscription instead