Start with the job
Describe the input, desired output, and constraints. Review the draft flow before anything can leave Draft.
The no-code AI agent builder for the work that repeats. Then let it earn per call.
Describe the job in a sentence or wire it on a visual canvas: qualify leads, chase invoices, triage support, file reports. Test it with a dry run that spends nothing, then launch it on a schedule or a trigger. When it is ready, publish it and let other businesses and their agents pay to use it.
Describe the job in one sentence. The studio drafts your agent on the canvas, free to test before it goes live.
One flow. Three ways to shape it.
Guided starts from the outcome you describe. Studio shows the graph you can inspect and change. Code is there if you want it and never required. All three edit the same flow, not a hidden prompt chain.
See every step
Inspect nodes, typed parameters, input and output ports, explicit edges, run state, and per-node cost estimates on the canvas.
Code when you want it
Use the code-oriented setting when you want it. The visual builder, version review, publishing, and run controls do not depend on it.
Every step that matters waits for your say-so.
Testing, publishing, going Live and taking payments are separate controls. You choose when to advance each step, with a clear receipt of what changed.
| Control | What changes | Your next step |
|---|---|---|
| Dry run | Runs the graph with safe stubs for cost-bearing and side-effecting nodes. | Check flow logic with test responses at no credit cost; verify live integrations separately. |
| Launch / publish | Validates the flow and publishes its stable public page and discovery record. | Promote a saved version through Test and Live, then enable payments separately. |
| Promote to Test | Selects an immutable saved version as the active Test version. | Review scoped test results separately; this receipt records the selected version. |
| Promote to Live | Moves that same active Test version to Live after typed confirmation. | Configure your payout address and enable settlement when you are ready to accept payments. |
| Enable settlement | Allows a priced Live endpoint to verify and settle eligible caller payments. | Share your public service page with prospective callers and track settled calls in your ledger. |
Live promotion requires the active Test version and the exact typed phrase PROMOTE LIVE.
A caller pays before a priced flow runs.
The public run route refuses a paid call unless the agent, deployment, platform, settlement and payout checks are all ready. An explicit dry-run request still wins over paid execution.
- 01Terms
A payment-enabled Live endpoint returns x402 payment terms to the caller.
- 02Authorization
The caller signs a USDC authorization on Base and retries the call.
- 03Settlement
The platform verifies and settles the payment before running the flow.
- 04Result
The response reports settled true only after real settlement succeeds.
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.
x402Caller settlement
StripeBuilder gateway-credit top-ups
A2AAgent discovery
Read the exact operational boundaries in the payments documentation.
Take your workflow from preview to paid calls.
- Preview the logic. Verify live integrations.Dry runs use test responses for cost-bearing and external-action nodes; test live services separately.
- Give buyers a service they can evaluate.Publish a stable public page and machine-readable service record, then share them with prospective callers.
- Choose runtime nodes for your live workflow.Use Connector Lab API Operation for simulation. Launch and Live require supported runtime nodes.
- x402 is the caller-payment rail today.Stripe funds builder gateway credits; A2A describes discovery, not settlement.
Build, verify, or compare.
Follow the path that matches the decision you are making now.
Before you build.
Is Suede AI Agent Studio really no-code?
Yes. Guided mode can turn a plain-language job into a draft flow, and Studio exposes the same flow as visual nodes, ports, and edges. Code is an optional setting, not a requirement for building or publishing an agent.
Do I need a wallet to build or dry-run an agent?
No. You can start, edit, save, and dry-run a flow without connecting a wallet. A valid payout configuration is required before an operator can receive settled caller payments.
Does publishing automatically turn on paid execution?
No. Publishing, promoting an immutable version through Test and Live, and enabling settlement are separate controls. Each boundary has to be satisfied before a priced public call can settle.
How do caller payments work today?
A payment-enabled Live endpoint returns x402 payment terms. The caller authorizes USDC on Base and retries; the platform verifies and settles the payment before the flow runs. A response reports settled true only after real settlement succeeds.
What does a Test promotion record?
Test records which immutable version an operator selected, and it comes before Live promotion, so the version that goes live is always one an operator chose and named.
Hand off the work that repeats. Keep the final say.
Describe the job or pick a template, test it with a dry run, and launch it when it is ready. Runs bill at what they cost plus 20% from credit you top up.
Want more customers instead? Run the free audit.