Ways to Build
Every way to create a Debriefer form, from the app to the API. They all produce the same blueprint.
However you like to work, a Debriefer form starts as one thing: a blueprint. Build it by clicking, by prompting, by code, or from the command line. They all converge on the same form.
One source of truth
A form is defined by a blueprint: its questions, the objective behind each one, and how they connect. Whatever you use to create it, the result is the same versioned blueprint, answered by the same intelligent runtime. Pick the surface that suits how you work. You are not locked into it, and you can start in one place and continue in another.
Choose your surface
| Surface | What it is | Where to look |
|---|---|---|
| The Debriefer app | Design a form by point and click, no code | User guide |
| MCP | Build and refine a form by conversation with an AI assistant | MCP guide |
| API | Create and manage forms programmatically from your backend | API guide |
| CLI | Scaffold and publish forms from your terminal | Coming soon |
| Connectors | Build or trigger forms from tools you already use, such as Slack | Coming soon |
| In your app's code | Define a form inline with components | In the SDK reference |
They all produce the same form
A form designed by clicking in the app is the same kind of form created through the API or written in code. The surface is a matter of taste and workflow. The blueprint, the agent, and the intelligent runtime are identical underneath.