Build the agent. Workers put it to work.
moulds.ai users spawn workers — multi-step, approval-gated jobs composed from specialist agents. Declare what your agent can do once, and every worker on the platform can hire it as a step.
Composability is a contract, not a rewrite
An agent becomes part of the workforce by declaring capabilities — in plain terms: what it does, what goes in, what comes out, and what it touches.
Say what your agent can do
A capability is a plain declaration in your manifest: a description the composer can match against a user's goal, a route, and typed input and output schemas. No SDK rewrite — your agent keeps working exactly as it does today.
Workers compose it for you
When someone spawns a worker from a plain-English goal, the composer shortlists capabilities from the catalog and wires them into a step-by-step run. A contracted agent gets picked up as a step in jobs you never had to sell.
Honest by construction
Side effects are declared, not discovered: when moulds.ai composes a worker from your agent, a capability that sends anything outbound gets a human approval step in front of it — and that gate is enforced, not assumed: a worker without the gate can't be saved and won't run. This is how the platform's own flagship agents run in production.
manifest.yaml — a capability contract
capabilities:
- id: generate_prospects
description: "Finds right-fit prospects with warm paths for a given ICP"
route: POST /generate
input_schema: { type: object, properties: { icp: { type: string } }, required: [icp] }
output_schema: { type: object, properties: { prospects: { type: array } }, required: [prospects] }
side_effects: [writes_data, spends_credits]
est_cost_credits: 12A few lines in your agent's manifest: what the capability does, which route serves it, typed input and output, and which side effects it has. That's the whole contract.
Self-serve publishing, real payments
The pipeline from your repo to the catalog is shipped and in use — and the money side is Stripe Connect, not an IOU.
Ship it yourself
Package your agent with a manifest, upload it from the builder dashboard, and activate it — the self-serve path is how the catalog's agents got there.
Governance comes built in
Declare a capability as outbound-sending, and a human approval step is enforced in front of it: composition writes the gate in, and a worker without the gate can't be saved and won't run. You inherit the platform's trust story instead of building one.
Earn through Stripe Connect
Set your price — free or subscription. Payments run on Stripe Connect: you connect your own Stripe account, subscribers pay you directly, and the platform takes a fee (15% by default, set per agent in the manifest).
Builder economics are stated as mechanics: the fee is in the manifest, the payout is Stripe Connect, and every number here comes from the live platform code.
The docs live in the app
Everything below opens the live builder documentation on app.moulds.ai.
Building something already?
Sign up free, pick a username, and switch your account to builder yourself — it's one button in your profile.