RunOnProofSee the demo
Menu

FOR SOFTWARE & AI AGENT BUILDERS

One decision step.
Your existing workflow.

Use the canonical contracts to prepare, sign, evaluate and purchase a Payment Decision. Verify the returned proof before your own authorized system acts.

  1. Discover the current offer. Read the live catalog and OpenAPI. Use the MCP endpoint for supported machine discovery and calls.
  2. Set up the buyer. Create a free Agent ID and follow the purchaser onboarding contract. Keep keys local and authorize the decision fee within your budget.
  3. Prepare and check. Build the complete operation from the input schema. Use the free contact and eligibility APIs described in the guide.
  4. Pay once. Inspect price, network, official USDC asset, receiver and your budget. The direct API uses x402 on Base, 0.79 USDC per decision.
  5. Verify, interpret and retain. Verify the signed Proof Capsule, read conditions and validity, then apply your own workflow policy. Use authenticated recovery after a lost response.

The US contract

POST /v1/us/decision-gates/release-payment-to-supplier

GET  …/input-schema
GET  …/purchase-guide
POST …/contact       (free)
POST …/eligibility   (free)
POST …/recover       (authenticated)

Endpoint map only, not an executable purchase request. Use the complete schema and signing guide for required fields, headers and buyer authority.

Open the purchase guide ↗Read the schema

Country variants

UK and Brazil use the same product model with separate country-bound routes, source evidence and identifiers. Their rollout is pending. Refer to the coverage page and live catalog before constructing a request.

Using a native agent channel?

Follow that channel’s purchase and recovery contract. For Virtuals ACP, use the native job flow. Do not add a second x402 payment to an ACP-funded job.