Frequently asked questions
Short answers, no hedging. If a question isn't here, the contact page reaches a person.
Do I need a crypto wallet to use Agent Studio?
Not to build, test, or launch. The studio, dry runs, and launching are all wallet-free. You need a wallet address in exactly two cases: to receive money when your priced agent gets paid calls (an EVM address for your payout), and to make paid calls to someone else's live agent (a wallet that can sign USDC payments on Base).
What does it cost to build and launch an agent?
Nothing. There is no subscription and no listing fee. Your running costs are metered: the LLM node's first 100k gateway tokens per month are free per workspace, then tokens are billed per million, and specialized Suede endpoint nodes carry a fixed per-call price shown on the node card. Logic nodes (HTTP, Transform, Branch, Loop) are free.
What is dry-run mode exactly?
A dry run executes the real graph but stubs exactly the nodes that cost money or touch external systems: LLM returns without calling the model, HTTP returns a fixed placeholder without making a request, and paid nodes never settle. Branch, Transform, Loop, and the other logic nodes run for real. It is the default mode everywhere; nothing settles until an agent explicitly enables live settlement.
What does the platform take when my agent gets paid?
5% of each settled call. The remaining 95% routes to the payout address you set. There is no other fee on the selling side: no listing fee, no monthly minimum, no payout threshold.
Can people call my agent before I turn on real payments?
Yes, and that is deliberate. Until you enable settlement, your published endpoint answers every call free in dry-run mode, so integrators can wire it into their systems and verify the output shape before any money moves. When you go live, the same URL starts issuing 402 payment challenges.
Do callers need a Suede account or API key?
No. The run endpoint is open: free and dry-run calls need nothing, and paid calls authenticate with the payment itself; the caller's wallet signature is the identity. Suede never issues API keys to callers.
Where are my flows stored, and who can see them?
Flows are private to their owner; the directory only ever lists agents you have explicitly launched. Launching publishes the agent's name, description, price, and run endpoint, not the flow graph itself.
What stops a buggy flow from spending all my money?
Every run shares one in-run cost ceiling, checked before each cost-bearing node executes: the minimum of a per-run cap ($5 by default) and the agent's remaining daily budget. A loop that would exceed the ceiling aborts with an explicit error naming how many iterations completed. Loops are additionally capped at 200 iterations with concurrency at most 4.
Can I run my agent on my own server and still sell it through Suede?
Yes: that is the relay setting in the @suedeai/agents SDK. Callers hit your Suede endpoint and pay through the normal 402 gate; the platform verifies the payment, forwards the call to your server with an HMAC signature, and routes the USDC to your payout address. Your code runs on your machine.
What happens if a paid call fails mid-run?
Payment settles before execution starts, so a run that fails after settlement is a settled call with status "error" in the response. x402 has no chargeback mechanism, and the platform does not claw back settled payments. This is why testing with dry runs (free, both for you and for prospective callers) before going live matters.
Is this only for music and IP workflows?
No. The template catalog and node palette are mostly general business workflows: lead scoring, invoice chasing, contract review, support triage, dev-ops. Music and IP (song generation, IP registration, royalty splits) is one built-in vertical among the priced endpoint nodes, not the frame for the product.
What is x402 in one sentence?
An open protocol that uses HTTP status 402 to charge for a single API call: the server quotes machine-readable payment terms, the caller retries with a signed USDC authorization in an X-PAYMENT header, and settlement happens on Base before the response.