moulds.ai
Governed autonomy

You stay in control. By design.

Autonomy without governance is just a black box that emails people. Everything below is a screenshot or recording of the real product — the same views you get on every run.

Approval gates — nothing outbound moves without you

Any step that sends something to the outside world gets a human gate inserted directly in front of it by the engine itself — it's structural, not a setting you can forget to turn on.

  • The run parks at the gate and waits for your explicit approve — no approve, no send.
  • Gates are auto-inserted before every outbound-sending step; there is no path around them in a worker's definition.
  • Approving is a one-click, one-time action — a duplicate or concurrent approve is rejected, not double-sent.
A task run on moulds.ai parked at an approval gate: the step card reads "Waiting for your approval" with an Approve & continue button — nothing proceeds without the owner.

Every run is a step list you can read

No log-diving. A run is a numbered, plain-English list of steps — what each one did, how long it took, what went in, and what came out.

  • Status, duration, inputs and outputs on every step — expandable in place.
  • Runs that need your approval float to the top of your roster and deep-link straight to the run that's waiting.
  • Sub-workers are walkable the same way: a gate deep inside a composition still bubbles up to the top-level run.
A completed moulds.ai task run: numbered steps in a vertical list, each with a plain-English label, status pill, duration, and expandable input/output.

Every AI call is on the record

Each step keeps a trace of every single AI call it made: which model, how many tokens in and out, retries, latency — and the exact prompt and response text, expandable right in the step detail.

  • Per-call rows, not aggregates — you can audit the one call that mattered.
  • The same trace covers your own keys and platform keys alike.
  • Recorded below: a real production run's trace, opened live.
Drilling into a completed moulds.ai task run: expanding a step’s output, then the AI-calls table showing model, tokens, latency — and the exact prompt and response text.
Sped up — real run: 0m 11s · recorded Jul 2026
Also true

The quieter guarantees

Every claim on this page is verifiable in the product. If we can't verify it, it isn't here.

Your keys, your call

Bring your own AI keys (Gemini or Anthropic) and your AI calls run at zero platform credit cost — the keys are stored in the platform vault and used only for your runs. No keys? Platform keys work out of the box, metered transparently against your credit balance.

Grounded in live sources

Research agents search the live web through a real Google-results search primitive — prospects, buyers, and signals come from pages that exist today, not from model memory. Search results carry their sources so you can check them.

Out of credits? It stops loud.

If your balance runs out, the run stops with an explicit credits-exhausted error before the AI call is made — never a silent failure, never a surprise charge. Top up or connect your own keys, then run again.

See the whole flow, gates included