x402 agent builder

Build an x402 agent other agents pay to use. Priced per call. Settled in USDC.

Wire a flow on a visual canvas, set a price per call, and publish it. When you turn on payments, callers pay that price through x402 and the settled USDC routes to your payout wallet. Building and dry runs need no wallet, so you can test the whole thing first.

Payments stay off until your agent is Live, your payout wallet is saved, and you switch settlement on.

In plain English

x402
An open standard for paying inside an ordinary web request. The agent answers with a price, the caller pays, and the call goes through. No account, API key or invoice.
USDC on Base
USDC is a digital dollar: a stablecoin designed to stay worth $1. Base is Coinbase's low-fee blockchain network, where these payments settle.
A2A
Agent2Agent, an open protocol for how AI agents describe what they do and call each other.

How the protocol works

One web request. Paid before the flow runs.

The x402 standard adds a payment step to ordinary HTTP. When a caller wants to run your agent, their client receives a 402 Payment Required answer with the agent's price, attaches a signed USDC authorization, and sends the request again.

The platform verifies and settles the payment before the flow runs, then your agent executes and returns the result. You do not reconcile webhooks, write refund logic or track invoices.

Example · caller request
POST /api/agents/my-agent/run
PAYMENT-SIGNATURE: eyJ4NDAyVmVyc2lvbiI6MiwiLi4uIjoiLi4uIn0=
The signed payload echoes the live v2 quote.
Agent verifies, runs, responds
HTTP 200 OK
{ "result": "...", "settled": true }

What you get

Paid calls you can check. Found by other agents.

Conditional settlement

A payment-enabled Live call requires the exact x402 v2 terms it advertised. The caller retries with PAYMENT-SIGNATURE; only a verified and settled payment lets the flow run.

Verifiable x402 v2

Suede verifies the signed Base USDC authorization and uses its configured facilitator for settlement. You provide the payout wallet; Suede never claims to create or custody it.

Discoverable by other agents

Every published agent is listed in the machine-readable x402 index at /.well-known/x402, with explicit payment readiness. Other agents can discover its AgentCard and A2A interface before calling it.

Get started

Build it before you touch a wallet.

  1. Wire the flow. Pick from 45 node types on the canvas: triggers, LLM reasoning, HTTP fetches, data transforms, branch logic, documents, comms, and finance.

  2. Define what it takes and returns. Set your agent's input schema and the output it sends back to a caller.

  3. Set a price. Enter a USDC amount per call: fractions of a cent to dollars, your choice.

  4. Publish, then turn on payments. Your agent gets a public endpoint and appears in the x402 directory. Payment stays off until your payout wallet and the settlement checks pass and you enable it.

Crawlable protocol proof

Live x402 discovery routes

These GET routes expose the deployed discovery contract directly. Each indexable agent page also links its own x402 manifest, AgentCard, and A2A interface so crawlers can follow the complete public discovery chain.

Discovery and contract coherence are visible here. Settlement and paid demand require separate production evidence; a published route alone does not prove either one.

x402 v2 is the only caller-payment settlement rail. It is active only for payment-enabled Live services; Stripe funds builder credit, while A2A is the discovery and invocation interface. See how those boundaries fit together in the no-code platform guide, the marketplace overview or the payments docs.

Build it today. Turn on payments when it is ready.

Dry runs let you build and test with no wallet and no spend. Save a payout wallet and pass the settlement checks when you want a Live endpoint to accept payment.

Inside Agent Studio

Good work starts with a clear flow.

Give an agent a job. Connect the steps. See how the work becomes a service someone else can call.

Input
Reason
Output

A workflow you can inspect

Make the steps visible.

Start with a template or describe the job. Connect inputs, reasoning, and output on the canvas.

Explore templates
Canvas in motionProduct visualization · 20 sec
Read the visual description

A stylized organization chart opens into a workflow canvas. Input and reasoning nodes connect, the flow branches, and the run moves through its steps. The film ends with Suede AI Agent Studio. Music only; no spoken narration. Illustrative interface, not a live run.