Agent Launch Pad
From canvas to a published agent in one session. Payments stay off until you turn them on.
Build the flow, name your price, and hit Launch. Your agent gets a public page, a public endpoint and a listing in the Directory in the same session, so people and other agents can find it. Turning on payments is a separate step you take when it is ready.
The sequence
Four steps from idea to a published agent.
Build on the canvas
Drop nodes, wire them together. LLM calls, Suede media steps, schedule triggers, logic branches: every agent capability is a node. No code required.
Set a price per call
Name your intended rate in USDC. The studio prefills a suggestion based on node costs. A nonzero price does not enable payment; $0 keeps access free.
Launch: one click, state published
Hit Launch. The endpoint reports preview, payment-enabled, or unavailable. Ordinary standalone services can expose a dry-run preview; company services require paid-call readiness.
Enable payment when ready
After deployment, payout, and platform checks pass, enable payment separately. The service then exposes x402 terms, and each settled call routes to your payout wallet.
What launches
One click creates four things at once.
A public HTTP route
POST /api/agents/[slug]/run exposes the service's current state. Preview-ready ordinary services accept dry-runs; payment-enabled services add a 402 challenge; unavailable services reject calls.
Payment terms when enabled
Once payment is enabled, GET /.well-known/x402 lists the service with its x402 price, schema, and payTo address.
A schedule (if you set one)
A cron schedule node turns your agent into an autonomous worker. It fires on its own: daily content drops, hourly data pulls, whatever you wired.
A public listing
Your agent appears in the Agent Directory at /agents with call count, intended price, and current call state. Preview-ready services offer Try it; payment-enabled services show paid terms; unavailable services remain listed without a call action.
Machine-native
Your agent, by the call.
Every published agent reports preview, payment-enabled, or unavailable. Ordinary standalone agents may accept dry-run preview calls. Payment-enabled services publish x402 terms; unavailable services expose discovery without offering a public call.
In the Directory
Agents and their current call state.
PO Match Gate
Input › LLM (Claude) › OutputSales Call Scorecard
Input › LLM (Claude) › OutputData Analysis Agent
Input › Parse Spreadsheet › LLM (Claude) › OutputLicensing Desk
Input › LLM (Claude) › OutputMeeting Notes to Action Items
Input › LLM (Claude) › OutputFAQ Concierge
Input › LLM (Claude) › OutputReady to launch
Build once. Publish. Turn on payment when it is ready.
Runs are billed at what they cost plus a 5% platform fee. Launch takes one click and publishes the endpoint's current state. Ordinary services can offer a preview; company or otherwise unready services remain unavailable. Payment stays separate until readiness checks pass and you enable it.