402Dock / Ethereum Mainnet
turn requests
into revenue.
Payments for APIs, agents, and digital resources. USDC or ETH. Verified on Ethereum.
One payment. A verified receipt. Access delivered.
HTTP 402 / paid access
request → payment → accessGET /api/demo/research
Every paid request starts with a price. Read the resource’s payment requirements before connecting your wallet.
- network
- Ethereum Mainnet
- currencies
- USDC + ETH
- authorization
- your wallet
- settlement
- on Ethereum
- delivery
- after verification
- recovery
- saved orders
from request to paid access.
- 01
request
Call a protected resource and receive its payment requirements.
- 02
choose
Pay in USDC or ETH, with the exact amount shown before approval.
- 03
authorize
Approve the payment in your own wallet. Your signing keys stay with you.
- 04
settle
USDC authorizations are relayed to Ethereum. ETH is submitted directly by your wallet.
- 05
verify
The backend checks the receipt, recipient, amount, and required confirmations.
- 06
access
Unlock the resource and recover your order whenever you return.
built for the paid web
your resource.
your revenue.
- Exact USDC authorizations using EIP-3009.
- Native ETH payments with a unique order reference.
- Verified receipts before resources are released.
- Durable orders and recovery across interrupted sessions.
# Read the resource's payment requirements
curl -i http://localhost:4020/api/demo/research
# Read payment configuration and available currencies
curl -s http://localhost:4020/api/config
# Complete checkout, then retrieve the resource with your paid order
curl -i http://localhost:4020/api/demo/research \
-H "Authorization: Bearer <paid-order-id>"