Built on Base · x402 Protocol · USDC
The payment layer for x402 APIs.
One API key. One top-up. Instant access to any pay-per-call API on Base. We handle wallets, 402 flows, EIP-3009 signing, and on-chain settlement.
Pay-as-you-gono subscription
0savg. latency
1M cr = $1credit rate
Base L2network
$ npm install @allow402/sdk
then:$ client.proxy('https://api.example.com/v1/data')
The problem
Why developers struggle with API payments
Every option available today forces you to make a painful tradeoff.
01
Roll your own wallet
Private keys in .env, gas estimation logic, signing scattered across services, RPC node management. One wrong move and payments stop silently.
✗Keys exposed in env files
✗Gas fluctuations break flows
✗On-call for every chain upgrade
02
Build your own billing
Stripe webhooks, credit ledger, balance checks, fraud prevention, refunds — weeks of infrastructure before your first API call is monetized.
✗4–6 weeks of setup time
✗Stripe fees eat your margin
✗No crypto-native support
03
Use raw x402
The protocol is powerful but low-level. No SDK, no dashboard, no credit system. You implement the full 402→sign→retry loop yourself on every client.
✗No official SDK
✗Manual EIP-3009 implementation
✗Zero visibility into usage
allow402 solves all three.
No wallet to manage. No billing to build. The full x402 stack, abstracted into one API key.
DashboardEverything in
Open Dashboard →
Everything in
one place.
Monitor your usage, top up credits, manage API keys — without ever touching a wallet.
📊
Real-time call logs
Every API call: service, latency, cost, status. Updated live.
💳
Top up with card or USDC
Pay with your credit card or send USDC directly. Credits available instantly, no wallet setup.
🔑
API key management
Create, revoke, and scope keys. Track usage per key.
Architecture
How it works
allow402 sits as a transparent proxy. You never touch a wallet.
01
You call the API
SDK or HTTP with your API key. No wallet, no private keys needed.
02
We intercept the 402
We parse the payment requirements and sign an EIP-3009 USDC authorization.
03
You get the 200
Facilitator verifies on Base. API returns 200. Credits auto-deducted.
💻
→
allow402
→
x402 API
Waiting…
Features
Everything handled for you.
API key auth
Generate keys in the dashboard. Scoped, revocable, tracked. No OAuth dance.
EIP-3009 signing
We sign transferWithAuthorization on your behalf via a secure proxy wallet.
Credit system
1 credit = 1 micro-USDC (10⁻⁶). Top up with card or crypto. View your balance in $ or €.
Credits Available
98.72M ≈ $98.72
Live dashboard
Balance, transactions, and call logs in real time.
coinbase-pricesLIVE
weather-api
openai-proxy
maps-api
Any x402 service
Register any x402-compatible API. Base mainnet and Sepolia supported.
← 402 Payment Required
⚡ signing EIP-3009...
→ PAYMENT-SIGNATURE: eyJ...
← 200 OK ✓
Transparent retry
402 → sign → retry is invisible. Your code always gets a clean 200.
Agent budgetsYour agents,
Your agents,
your budget.
Create API keys with a fixed credit allocation. Your agents spend freely — but only within the budget you set.
01
Create a key with a credit budget
Allocate a fixed amount of credits to an API key. Those credits are reserved — set aside specifically for that key.
02
Hand it to any agent or client
Share the key with an AI agent, a teammate, or a third-party user. No wallet, no top-up, no crypto knowledge needed on their end.
03
It only spends what you gave it
The key is hard-capped at its budget. Calls beyond the limit are rejected automatically. You stay in full control.
allow402
ACTIVEMy Agent
x402_abc••••••••••••
CREDIT BUDGET
0 / 500k
≈ $0.00 / $0.50
RECENT CALLS
−1k
−2k
−1k
−3k
Building a x402 API?
Generate a key with 1€ of credits and share it directly with your customers. They can test your API immediately — no wallet setup, no USDC, no friction. You control the budget; they just call.
Built for everyone
One platform, three use cases.
For Developers
Ship in minutes,
not weeks.
Two lines of SDK code and you're calling any paid API. No wallet setup, no blockchain knowledge required. Focus on what you're building, not the payment plumbing.
const client = new Allow402Client({ apiKey })
const data = await client.proxy(apiUrl)
✓JS, TS, Python SDKs
✓Works in any environment
✓Full event logging for debugging
For AI Agents
Autonomous payments
for autonomous agents.
Give your LLM agent an allow402 API key and a credit budget. It calls any paid data source, tool, or model API — no human approval loop, no gas management.
// Claude, GPT, or any agent
// Just give it an API key
ALLOW402_KEY=x402_... tool_call()
✓Pre-funded credit budgets
✓Per-key spend limits
✓Audit trail of every call
For API Publishers
Monetize any endpoint
in 60 seconds.
Use PayLinks to add a price gate to any URL. Share your link — callers pay from their credits, you earn 90%. No Stripe account, no billing code, no infrastructure.
POST /v1/links
{ "targetUrl": "https://your-api.com",
"priceCredits": 1000 }
✓90% revenue share
✓Instant USDC earnings
✓Built-in usage analytics
SDK
Three lines to your first call.
Install the SDK, initialize with your API key, and start calling. The entire payment layer is invisible to your application code.
✓ No wallet setup
✓ No USDC management
✓ No on-chain transactions
Comparison
Infrastructure you don't build anymore.
Everything that used to take weeks of crypto infra work — handled.
Time to launch (traditional)Weeks
Time to launch (allow402)Minutes
Top up
Pay in any currency.
Top up your credit balance with crypto or fiat. Credits convert automatically to USDC for on-chain payments.
₿
BTC
Bitcoin
Ξ
ETH
Ethereum
$
USDC
USD Coin
₮
USDT
Tether
✕
XRP
XRP
◎
SOL
Solana
€
EUR
Euro
Your currency
BTC, ETH, EUR…
→
Credits
converted instantly
→
API calls
any x402 service
FAQ