Shipping
Pick the path from done to live that fits how your team already works. Versioned releases, gradual rollouts, one-click promotion — each one runs smooth, and you stay in control the whole way.
Pick the shape that fits your app. Same pipeline. Four ways to receive it.
Drop a request into a curl one-liner, stream the trace into a live UI, follow every step as it lands, or hand us a URL and walk away. The pipeline doesn't decide the shape — you do.
Fire one request. Get one JSON back.
When you just need the answer, hit /execute and read the response. One round trip, one JSON body, done.
- Lowest-friction integration — paste a curl, you're done
- Best for short pipelines and synchronous request paths
{
"intent": "billing_question",
"confidence": 0.94,
"summary": "Customer asks about..."
}Every pipeline you ship gets its own URL. Append a verb to run it. Pin a version when you need to.
The moment you publish, your pipeline owns a URL. Hit it with /execute and you're done. Need to lock a caller to a specific version? Slide /v4 between the slug and the verb — one segment, full isolation.
One URL, two forms. Toggle between them.
- Live form always follows the production pointer — promote a new version and every live-URL caller upgrades with zero changes
- Pinned form freezes a caller at a specific version — useful for A/B tests, canary rollouts, or callers you can't redeploy
- Actions are composable: replace /execute with /jobs or /step without changing the org, project, or slug segments
Move what's live with one click. Zero code changes. The URL stays the same.
Your live URL always points to whichever version carries the production tag. Promote v3, and every caller hitting the unversioned URL gets v3 — instantly, without touching their code. The pinned /v4 callers? Untouched.
- v4tighten validator on edge casesPRODUCTION
- v3switch draft step to gpt-5
- v2add language fork, retire fallback
- v1initial publish
Same URL. New production version. Every caller keeps running, untouched.
- Promote in the dashboard — no redeployment, no environment variable to rotate, no downtime
- Callers on the unversioned URL follow the pointer automatically; callers hitting /v4 stay pinned to v4
- Roll back by promoting an older version — the pointer just moves back