Declare or annotate a variable
Optionally attach a note, a type hint, or a manual declaration to a variable. This is documentation only — it carries no runtime meaning and never gates a call. Annotating a name that’s already derived returns 200 (not a conflict). Names are case-sensitive and must match ^[a-zA-Z_][a-zA-Z0-9_]*$; the reserved caller variables (caller_info, caller_number, caller_name, verified) can’t be declared.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Path Parameters
Body
Declare or annotate a variable. Upserting an already-derived name is a 200, not a conflict.
Response
The upserted variable (merged derived ∪ annotation).
A merged interaction variable: the DERIVED registry (scanned from playbooks + skills) unioned with the per-agent annotation overlay. source, deletable, producedBy, and consumedBy are computed from the scan; note, type, and updatedAt come from the annotation. type is an OPTIONAL, nullable hint that is NEVER enforced.