Start with the job
Describe the input, desired output, and constraints. Review the draft flow before anything can leave Draft.
No-code agent platform · controlled publishing
Build a no-code AI agent. Keep the Live switch human.
Describe a job or wire it on a visual canvas, dry-run the flow without a wallet, and publish a stable endpoint. Paid calls stay off until an immutable version reaches Live and settlement is deliberately enabled.
No wallet is required to build or dry-run. Launch, Live promotion, and settlement remain separate operator decisions.
What no-code means here
One flow, two visual ways in
Guided mode starts from the outcome you describe. Studio shows the graph you can inspect and change. Both produce an explicit flow rather than a hidden prompt chain.
See the topology
Inspect nodes, typed parameters, input and output ports, explicit edges, run state, and per-node cost estimates on the canvas.
Optional, not required
Use the code-oriented setting when you want it. The visual builder, version review, publishing, and run controls do not depend on it.
Approval boundaries
These controls are separate on purpose
A green state in one column never silently advances the next. The operator can see what each action changes and what it leaves untouched.
| Control | What changes | What does not |
|---|---|---|
| Dry run | Runs the graph with safe stubs for cost-bearing and side-effecting nodes. | It does not call those live services, spend credits, or prove an integration works. |
| Launch / publish | Validates the flow and publishes its stable public page and discovery record. | It does not promote a version to Live or enable paid settlement. |
| Promote to Test | Selects an immutable saved version as the active Test version. | The Test receipt does not certify that a scoped test suite passed. |
| Promote to Live | Moves that same active Test version to Live after typed confirmation. | It does not configure a payout address or switch settlement on by itself. |
| Enable settlement | Allows a priced Live endpoint to verify and settle eligible caller payments. | It does not create traffic, demand, or a guarantee of earnings. |
Live promotion requires the active Test version and the exact typed phrase PROMOTE LIVE.
Current pay-per-call contract
A caller pays before a priced flow runs
The public execution route fails closed unless the agent, deployment, platform, settlement, and payout gates are ready. An explicit dry-run request still wins over paid execution.
- 01Terms
A priced 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.
x402Caller settlement
StripeBuilder gateway-credit top-ups
A2AAgent discovery
Read the exact operational boundaries in the payments documentation.
Useful limits
What this page is not promising
- Dry run is not a live integration test.Cost-bearing and side-effecting nodes are intentionally stubbed.
- Publishing does not create demand.It creates a stable public and machine-readable place to evaluate the agent.
- Some prototype nodes cannot be launched.Connector Lab API Operation is simulation-only and blocked from Launch and Live.
- x402 is the caller-payment rail today.Stripe funds builder gateway credits; A2A describes discovery, not settlement.
Choose the next proof
Build, verify, or compare
Follow the path that matches the decision you are making now.
FAQ
Before you build
Is Suede 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 priced 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.
Does a Test promotion prove the flow passed its tests?
No. Test records which immutable version an operator selected and is a prerequisite for Live promotion. It is a version-control receipt, not proof that every node or external integration passed a scoped test.