Publish an action.
Skip the backend.
An action is a pipeline of steps — http, llm, wasm — reviewed per version, priced per run, and paid out to its author. The smallest complete business on Wandlet is one action and one sealed key: no servers, no billing integration, no storefront.
From a pipeline to a listing.
-
01
Write the pipeline
Your agent builds a real action — the actions repo is the worked path: a pipeline of
http,llm, andwasmsteps, compiled to a WebAssembly component and proved insimulatebefore it ever ships. -
02
Declare what it may touch
Each step declares its capabilities: the exact hosts it may fetch, the model pass it makes, the compute it needs. The declaration is the enforcement — the sandbox grants nothing else.
-
03
Per-version review
A reviewer approves a specific version of your pack, and only that version is served. Listed artifacts are built from your submitted source, so review reads source, not bytes. An edit starts the next version.
-
04
Listed, on both surfaces
People install your pack from the Library and run it from the menu. Agents discover the same actions over MCP and pay per cast. You never see the difference — every run lands the same receipt.
Your key. Anyone can spend it. Nobody can see it.
Bind your own API key to your action at publish. The value goes into a sealed, write-only store — no API returns it, no log prints it. It is usable only inside your sealed artifact: the code is fixed by content hash, the destination is pinned by your declared allowlist.
Anyone who runs your action spends the key without ever holding it. A price action carrying the author's own data-provider key is a complete, chargeable product — no bring-your-own-key for users, no infrastructure for you.
Resolution order
When the same secret name is bound at several levels, the most specific wins:
An organization's own key overrides yours. Quota abuse is priced, not policed — every run pays your fee either way.
Two ways to earn on every run.
The developer fee
Your declared margin, on the action's manifest: a fixed amount, a percentage, or both. It is data, like every other rate — and it appears on the caller's receipt as its own named line.
Developer-priced calls
Price a specific call from inside your action code. Declare a maximum up front — it is reserved from the caller's grant before the call runs — then settle the actual price at or below it afterwards.
Payouts
Fees and developer-priced lines accrue to your identity on every receipt. Payouts are aggregated and paid in the form you prefer. What the caller was charged and what you are owed derive from the same receipt — there is exactly one version of the money.
Callers always see an estimate first, spend never exceeds its ceiling, and the unspent remainder refunds. Your prices ride inside that promise. How estimates and receipts work →
Headless businesses.
A bridge is a developer-operated backend registered with the platform — the integration between the ecosystem and a traditional service. The flow is always the same: input and payment in, result out.
Zero infrastructure
If your upstream already takes machine payments (x402), your product is an action plus an allowlist entry: the platform's treasury answers the upstream's quote automatically, and the real cost lands on the caller's receipt. Nothing to host.
Your own backend
For services that cannot take machine payments, register a bridge: your backend, your credentials in the sealed store, your fee on every call. Wandlet is the storefront, the meter, the clearinghouse, and the identity layer — your business is just its service.
First-party today. Built for everyone.
Publishing is first-party at launch: every listed action currently ships from Wandlet, through the same listing, per-version approval, and built-from-source review that third-party publishers will use. Opening the gate is a policy decision on machinery that already exists — not a rebuild. The release notes will say when it opens: get them by e-mail.