Compiled workflows, published only when they deserve it.
Rhumb recipes are the Layer 3 surface for deterministic multi-step execution. The route is live. The public catalog is not padded with placeholders. If a recipe is not ready for public use, this page says so plainly.
Current public state
Published
0
API route
Live
Catalog
Curating
There are currently no public recipes in the live catalog. That is intentional truth, not a broken page.
No public catalog yet
We would rather show zero than publish a fake marketplace.
Layer 3 exists in the product, but the public recipe inventory is still being curated. Until each workflow has a stable schema, bounded cost envelope, clear failure behavior, and docs we are willing to defend, the public catalog stays empty on purpose.
Direct API probe
curl https://api.rhumb.dev/v2/recipes
# => { "data": { "recipes": [], "count": 0, ... } }What a public recipe must prove
- Deterministic execution order. No improvised planning loops disguised as a recipe.
- Bounded cost and timeout behavior. Public workflows need visible ceilings before we ask agents to trust them.
- Traceable step outcomes. Inputs, outputs, and failure surfaces must be inspectable, not hand-waved.
Why this page exists
Because a 404 is less honest than a zero.
If you reached for Rhumb recipes, you should land on a truthful status page: the API route exists, the catalog is empty, and the next useful surfaces are capabilities, docs, and pricing.
Today
Layer 2 is the public workhorse
Use capabilities and governed execution while the Layer 3 catalog is curated.
Next
Publish only canonical workflows
When recipes go live here, they should have stable schemas, step counts, ceilings, and receipts.
Principle
Truth over theater
Public surfaces should say exactly what exists now, not what we hope to publish next week.