6–9 months · live (authenticated)
Some jobs need one model call. Others need a brief, an image, a video, and an evaluation step. Authenticated execute already expands a bounded DAG, waits on catalog jobs, and hands off image-to-video inputs. The planner is not a general-purpose agent. The sequence in the demo is illustrative.
Bounded plan · no jobs submitted
Create a 15-second product ad
Product analysis
vision brief
Hero still
image generation
15s 9:16 clip
image-to-video
Caption pass
copy step
Quality check
evaluation layer
Authenticated execute runs a bounded DAG with wait and handoff. This page does not start jobs.
Each step has a tool, expected input, expected output, and a stop condition. Open-ended tool use is out of scope.
The agent sees a quote for the completed job, with a SHA-256 routing attestation, before anything runs. The quote is an estimate: on execute, each catalog step reserves its own credits as it starts.
Retries and ambiguous submissions reconcile against that identity so the same plan cannot be charged twice. Authenticated execute is the charge path; this page does not start jobs.
QA is a step in the plan, not an afterthought. Failed checks are stored on the receipt the requesting agent can retrieve.
Customer asks for a defined creative job. Studio chooses the sequence.
Every step is inspectable. The planner is not an unbounded agent.
Execute runs the DAG. This page does not start jobs.
This page never opens Stripe Checkout, uses a wallet, or pays sellers. Authenticated outcome execute is the live charge path for agents. Named-model MCP, CLI, and /ai-router remain available.
Examples on this page are computed from sample intents and illustrative data. This page does not start a generation or call a model provider.
This page does not grant credits, settle USDC, or pay anyone. Revenue share for third-party capability sellers is not live.
People buy plans and credit packs through Stripe Checkout on /pricing. These plan pages never open Checkout or ask for card details.
Yes, through authenticated POST /api/v1/outcomes/execute or MCP execute_outcome. Catalog steps reserve Studio credits. This page does not submit those jobs.
No. The strategy is to be the specialized creative execution layer that other agents trust — not a general-purpose agent that browses the web or spends without a task boundary.
If the sequence cannot be audited, an agent cannot trust the charge.