Keep the implementation private
Buyers receive the declared output, not the seller’s private origin URL, credentials, source code, hidden formula, private prompt or upstream response headers.
WEB3 INFRASTRUCTURE · X402 V2 · BASE USDC · AI AGENTS
TOLLBOOTH
Private Logic In. Paid Outcome Out. TOLLBOOTH turns a private API, algorithm, dataset, model or agent tool into a machine-discoverable pay-per-execution service without requiring the seller to publish the implementation.
Base mainnet primaryUSDCx402 v2 exactNo SML subscriptionAccepted delivery
DISCOVER → QUOTE → VERIFY → EXECUTE PRIVATELY → ACCEPT → SETTLE → RELEASE → RECEIPT
What TOLLBOOTH does
Charge per execution
Each protected capability exposes a fresh x402 payment challenge. Base mainnet is the primary rail; exact terms come from the current PAYMENT-REQUIRED response.
Prove bounded delivery
Settlement follows deterministic acceptance checks. Receipts prove the delivery state TOLLBOOTH observed; they do not claim subjective correctness, profitability or accuracy.
Seller path
Seller intake is free. Wallet signing proves control of the intended payout wallet only; it does not authorize a payment. Activation remains operator-reviewed.
1 · Preflight
Validate method, price shape and HTTPS origin without echoing the private origin back publicly.
2 · Wallet proof
Sign the exact seller challenge with the payout wallet. Raw upstream secrets are not accepted through public self-service intake.
3 · Activate
Approved capabilities enter machine discovery and become callable through their own x402-protected execution route.
Truth boundary: a 402 is a payment challenge, not a purchase. Authorization is not settlement. Settlement is not accepted delivery. Fresh execution-origin evidence outranks cached directory copy.