⚠ BETAGatefare is in limited beta. Expect occasional issues, breaking changes, and features still being finalized. Use small amounts while we harden the system. Report problems to [email protected].
Built on x402 · Base mainnet · BETA

Turn any API
into a paid API.

Register your endpoint, set a price per request, get a proxy URL. Clients pay USDC automatically via HTTP 402. No code changes. No billing infrastructure. Under a minute if you already have a Base wallet.

APIs live
19
public catalog
Requests served
0
since launch
Paid out
$0.00
on-chain
402 FLOW · INTERACTIVE DEMO
wallet$12.40730
01POST/v1/sentimentclient → origin
02402Payment Requiredprice: $0.004 USDC
03SIGNwallet · 0.004 USDCBase
04POST/v1/sentiment + X-Paymentre-request
05200OK · data returned340ms · split 90/10
$0.00360 → publisher$0.00040 → platform
Built on open, public primitives
BASE
0xSplits
USDC
x402
Non-custodial
How it works

Ship a paid endpoint in four steps.

Your code stays exactly as it is. Gatefare proxies the endpoint — you never modify a handler or install a library.

step 01
Register your API
Paste your upstream URL, pick a wallet address. We compute your immutable 0xSplits address and hand back a proxy URL. No gas, no on-chain deploy — the contract activates on the first payout.
step 02
Consumer hits the proxy
A client calls your proxy URL without payment. Gatefare answers 402 with the price, chain, and settlement address — standard x402 headers.
step 03
Client signs and retries
x402-aware clients (Coinbase AgentKit, the reference SDK) sign a USDC payment automatically and retry the request with an X-Payment header.
step 04
USDC splits on-chain
Payment lands in your immutable 0xSplits contract — 90% to your wallet, 10% platform fee. distribute() is permissionless, so nobody can block your payout.
The wire

The 402 handshake.

example
Request · unpaid402
GET /p/you/endpoint HTTP/1.1
Host: gatefare.io

> 402 Payment Required
{
  "price":   "0.002",
  "asset":   "USDC",
  "network": "base",
  "payTo":   "0x6f…A1",
  "nonce":   "0x71a…c4"
}
Request · signed200
GET /p/you/endpoint HTTP/1.1
x-payment: eyJzaWciOiIweDQ4YzIu…

> 200 OK
x-receipt: 0x4a7c…f81
x-split:   90/10

data: { "token": "Hi" }
data: [DONE]

Illustrative headers. Actual responses follow the public x402 specification by Coinbase.

Gatefare in your language

Same service. Different reasons to care.

Find the one that sounds like you.

Developer
→ GET /p/your-slug
← 402  X-PRICE: 0.01 USDC
→ GET /p/your-slug + X-PAYMENT
← 200  your upstream response

No SDK. No middleware. Your server doesn't even know Gatefare exists — it just receives normal requests after the proxy verifies payment.

Read the docs
Business owner
  • Revenue per API call — $0.001 to $100+
  • No billing portal, no licensing negotiations
  • On-chain ledger — every payment is auditable
  • List on the catalog or keep your API private

APIs, datasets, model predictions — if it's behind an HTTP endpoint, set a price per call. Publish to the catalog so buyers find you, or share the proxy URL privately.

Register your API
AI agent builder
  • Agent reads X-PRICE from the 402 response
  • Signs a USDC payment, attaches X-PAYMENT
  • Gets data back — no API key, no OAuth
  • Budget cap per task, not per provider

x402 is machine-native. Your agent discovers price, pays, and gets data in a single HTTP round-trip. No human approval per call.

See agent docs
ML engineer
→ POST /p/your-model
  { "prompt": "..." }
← 200
  { "result": "..." }

Serve your model behind Flask, FastAPI, or anything that speaks HTTP. Gatefare handles metering and payment. You handle inference. Charge per prediction — no billing portal, no usage tracking, no API keys to manage.

Start selling
Web3 builder
Settlement:     USDC on Base
Split contract: 0xSplits V2
Owner:          0x0 (immutable)
Withdraw:       distribute() — permissionless

The split contract is immutable — ownerAddress: 0x0 means nobody (us, Coinbase, you) can alter recipients after deployment. The 90/10 split is locked on-chain. Call distribute() yourself — no one can block your withdrawal.

See the contracts
API catalog
  • Browse paid APIs by category and price
  • Every listing links to a live proxy URL
  • Prices, networks, and wallets — all public
  • List yours or keep it unlisted — your call

A public directory of paid endpoints. Buyers discover APIs without hunting for docs. Sellers get traffic without marketing. Listing is optional — you can share your proxy URL privately and never appear in the catalog.

Browse the catalog
On the catalog

Featured endpoints.

Browse all
Fine print

The fine print, actually printed.

Money. Each paid request routes USDC to an immutable 0xSplits contract on Base — 90% to your wallet, 10% platform fee, locked by ownerAddress: 0x0. Nobody can change the split after deployment — not us, not Coinbase, not you. Gatefare never custodies your balance; distribute() is permissionless, so you can withdraw directly without us. The contract itself deploys lazily on the first payout, paid out of accumulated USDC — registration is free for you and for us. The 10% platform share is routed to a Gnosis Safe multi-sig controlled by Gatefare operators.

Uptime. Your proxy URL lives on our domain. If Gatefare is offline, new payments pause until we're back. Funds already in your split are untouched — they sit on Base regardless of our uptime. Removing that single point of failure is on the roadmap, and we'll announce it when it ships.

Compliance. Payer wallets are screened against OFAC, EU, and UN consolidated sanctions lists at request time, and against Chainalysis risk indicators where available. A payment originating from a screened wallet is rejected with a 402 before it reaches your upstream. If you're in a comprehensively sanctioned jurisdiction, the platform is not available to you. Full policy in the Acceptable Use Policy.

Moderation. APIs that violate the Acceptable Use Policy (CSAM, illegal content, sanctions evasion, confirmed DMCA notices) may be suspended without prior notice. Suspended proxy URLs return 451 Unavailable For Legal Reasons and are removed from the public catalog. Counter-notices go to [email protected]. Enforcement counts are public on the transparency page.

Protocol. x402 is a public specification by Coinbase. Gatefare implements the server side — pricing, header negotiation, on-chain settlement — as a proxy. We didn't invent the protocol; we run a production-quality server for it.

Ready

Ship a paid endpoint.

Register, set a price, share the URL. Under a minute with a wallet in hand.