Turn APIs into paid services for AI agents.

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.

Open console See request flow

BUIDL

Payment route

TestLive

Protected endpoint

API access with payment built in

https://gateway.buidlbnb.io/m/workspace/endpoint

Origin APIhttps://api.company.com/data

Gateway checkpayment required before forwarding

Merchant recordcharge, proof, ledger, webhook

How BUIDL Fits

A payment layer in front of the API you already run.

Keep the origin unchanged. Gateway handles payment enforcement, settlement records, and merchant operations around it.

Configure01

Connect an origin

Add the HTTP endpoint, allowed methods, and per-request price.

Protect02

Require agent payment

Gateway presents the right payment challenge before origin traffic is allowed.

Settle03

Record every charge

Successful payments create ledger credits, webhooks, and payout balance.

Platform

Gateway URLs, payment challenges, and merchant records.

The product is a payment gateway for agent traffic: endpoint creation, payment enforcement, charge tracking, reporting, payouts, and webhooks behind one merchant console.

Endpoint creation

Configure a paid proxy with origin URL, allowed methods, USD price, status, and a public Gateway URL for agents.

Payment rail abstraction

Agents can pay through supported machine-payment rails while merchants manage one endpoint, ledger, and operations surface.

Merchant records

Every successful payment becomes a charge, ledger credit, request log, webhook event, and payout-eligible balance.

Request Flow

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.

Agent calls Gateway URL

Gateway resolves the workspace, endpoint, method, price, network, and origin.

Gateway asks for payment

The response tells the agent which payment options are accepted for that endpoint.

Payment proof is verified

Gateway validates the payment response before the origin sees the request.

Origin response is returned

Settlement creates a charge, credits the ledger, and sends subscribed webhook events.

Operations

Everything maps back to the merchant console.

BUIDL keeps the operational model simple: workspaces own endpoints, endpoints create charges, successful charges credit the ledger, and the console reports on live or test activity.

EndpointsOrigin URL, public URL, methods, price, network, status

ChargesPayment payload, verification, settlement, tx hash, latency

AnalyticsRevenue, charge count, average charge, failures, top endpoints

Webhookscharge.succeeded, charge.failed, payout.paid, payout.failed

Payouts

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.

Merchant balances are computed from settled ledger entries

Threshold payout policies reserve balances before transfer

Destination wallet, network, asset, and claim state are tracked

Payout webhooks report paid and failed claim outcomes

FAQ

Questions before putting an API behind BUIDL.

Practical details about the gateway flow, console records, payouts, webhooks, supported rails, and mode separation.

What can I put behind BUIDL?

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.

What does an unpaid agent request receive?

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.

What happens after payment succeeds?

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.

Where do merchant balances and payouts show up?

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.

Is BUIDL only for x402?

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.

What can I monitor from the console?

Endpoints, charges, revenue, average charge, failure rate, latency, top endpoints, top payers, payout state, webhook endpoints, and webhook delivery results.

How should I use Test and Live mode?

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.

Live Platform

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.

Open console