scenario_id to start a session.
Starter scenarios (auto-seeded)
Every new account already has two scenarios ready to use. List them and you’ll see them in the response.default_kind field:
Grab the
id and pass it to POST /meetings — that’s the fastest way to a live AI session.
Get one scenario
Persona, attached goals, meeting controls, and session options.
Create a scenario
When you need a custom flow.string
required
Shown in the dashboard and to participants.
string
required
interview, roleplay, upskill, or brainstorm.string
The meeting script — flow, rules, guardrails. Markdown supported. See the Prompting Guide.
string
Short description shown to participants on the join page.
integer
Max session length in minutes. Default
30.string
The AI’s opening line. If omitted, one is auto-generated from the prompt.
string
public (embeddable) or restricted (invite-only). Default public.Generate a scenario with AI
Skip building manually. Describe what you want and the AI generates a persona, prompt, and goals.-F '[email protected]'. The response gives you a scenario_id ready to use.
Tools, guardrails and skills
What a scenario is allowed to do is set with three fields on the scenario, each the complete set of ids in the order the agent should see them:
Leave a field out to leave that set alone; send
[] to detach everything of
that kind. The scenario read returns the same three fields. Ids that are not
your workspace’s answer 400 with the offending ids in errors. A whole
skill package attaches with one call of its own.

