Turn APIs intopaid servicesfor AI agents.
- Price
- 0.0100 USDC
- Ledger
- awaiting proof
BUIDL is a merchant console and gateway proxy for agentic payments. Create paid URLs, verify agent payment proofs, settle charges, configure payouts, and send signed webhook events without changing your origin API.
- Changes to your origin API
- None
- Unpaid request receives
- HTTP 402 challenge
- Each settled payment creates
- Charge, ledger credit, webhook
Agents pay before your origin handles the request.
Gateway sits in front of the merchant origin. It presents payment options, validates agent payment proof, settles the charge, emits webhooks, and forwards the request only when the payment path succeeds.
Transcripts are abridged and illustrative.
- 1
Agent calls the Gateway URL
Gateway resolves the workspace, endpoint, method, price, network, and origin from the public URL.
GET /m/workspace/endpoint HTTP/1.1Host: gateway.buidlbnb.io - 2
Gateway asks for payment
The response tells the agent which payment options are accepted for that endpoint, in a machine-readable challenge.
HTTP/1.1 402 Payment RequiredContent-Type: application/json{ "accepts": [{ "scheme": "exact","asset": "USDC", "maxAmountRequired": "…" }] } - 3
Payment proof is verified
The agent retries with payment proof. Gateway validates it before the origin sees the request.
GET /m/workspace/endpoint HTTP/1.1X-PAYMENT: eyJ4NDAyVmVyc2lvbiI6MSwic2NoZW1l… - 4
Origin response is returned
Settlement creates a charge, credits the merchant ledger, and sends subscribed webhook events.
HTTP/1.1 200 OKX-PAYMENT-RESPONSE: eyJzdWNjZXNzIjp0cnVl…ledger credit charge.succeeded
Set a wallet, define a threshold, and reconcile claims.
Settled charges credit the merchant ledger. Payout policy controls define when balances are reserved and sent to the configured destination wallet, and every claim is tracked to paid or failed.
- Balances are computed from settled ledger entries
- Threshold policies reserve balances before transfer
- Destination, network, asset, and claim state are tracked
- Payout webhooks report paid and failed outcomes
| Description | Debit | Credit | Balance | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CHG-7F3A21 | charge.succeeded /m/acme/weather | 0.0100 | 24.9600 | |||||||||
| CHG-7F3A44 | charge.succeeded /m/acme/weather | 0.0100 | 24.9700 | |||||||||
| CHG-80B1C9 | charge.succeeded /m/acme/forecast | 0.0250 | 24.9950 | |||||||||
| CHG-80B1D2 | charge.succeeded /m/acme/forecast | 0.0250 | 25.0200 | |||||||||
| PAY-0019 | Payout claim reserved at threshold | 25.0200 | 0.0000 | |||||||||
| CHG-81E004 | charge.succeeded /m/acme/weather | 0.0100 | 0.0100 | |||||||||
| Closing balance | Closing balance | Closing balance | 0.0100 | |||||||||
Everything maps back to the merchant console.
Workspaces own endpoints, endpoints create charges, successful charges credit the ledger, and the console reports on Live or Test activity, kept apart.
- EndpointsOrigin URL, public URL, methods, price, network, status/endpoints
- ChargesPayment payload, verification, settlement, tx hash, latency/charges
- AnalyticsRevenue, charge count, average charge, failures, top endpoints/analytics
- PayoutsDestination wallet, network, asset, threshold, claim state/payouts
- Webhookscharge.succeeded, charge.failed, payout.paid, payout.failed/developers/webhooks
Questions before putting an API behind BUIDL.
Practical details about the gateway flow, console records, payouts, webhooks, supported rails, and mode separation.
Any HTTP endpoint with a reachable origin URL. You configure the origin, allowed methods, price, and status; BUIDL gives you a paid Gateway URL for agents to call.
Gateway responds with a machine-readable payment challenge for the endpoint. The agent retries with payment proof, and Gateway verifies it before forwarding to your origin.
BUIDL settles the payment through the selected rail, streams the origin response, records a charge, credits the merchant ledger, stores proof details, and emits subscribed webhook events.
Settled charges appear in the merchant ledger. Payout policies define destination, asset, network, and threshold, while payout claims show requested, processing, paid, failed, or cancelled state.
No. x402 is one supported machine-payment rail. The product is a gateway layer so merchants can expose paid APIs to agents without rebuilding endpoint, ledger, payout, and webhook operations for each protocol.
Endpoints, charges, revenue, average charge, failure rate, latency, top endpoints, top payers, payout state, webhook endpoints, and webhook delivery results.
Use Test mode to configure and validate endpoint behavior without mixing it into Live reporting. Live mode is for production endpoints, charges, analytics, and payout activity.
Start from the console. Create an endpoint first.
The first useful action is creating a paid proxy in front of an existing HTTP origin, then testing the payment challenge and retry loop.