create_agent
Create an agent.
`name` is lower-cased on save — it is a key, not a display name.
soul = persona/identity; task = duties and boundaries; tools = tool-name whitelist (check
list_tools first; the system tools time/geo/weather **and `compute_chart`** are
**auto-enabled by default**, no need to list them — but note that passing `tools` at all
replaces that default list, so include them yourself if you pass any);
knowledge_bases = attached knowledge base names (once attached, retrieval is injected
automatically every turn).
`ask_forms` (**on by default**) lets the agent reply with a tappable single/multi-choice form
instead of a paragraph of questions — the natural move when it needs two or three facts before
it can answer. `compute_chart`, on by default too, is what lets it draw a chart; it computes
shares / growth / running totals / projections in code from numbers already in the material,
so the model never does the arithmetic. Pass `ask_forms=False` for an agent that should only
ever answer in prose.
alias = the **public human-readable slug** — strongly recommended: it becomes the memorable URL
segment for this agent (`{public_base}/t/<tenant>/<alias>`), the link you hand to people. Use a
URL-safe lowercase-hyphen name (`booking`, `suchka-venue`); it is normalised automatically.
Collisions / invalid names are reported in alias_result.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| soul | No | ||
| task | No | ||
| alias | No | ||
| model | No | ||
| tools | No | ||
| skills | No | ||
| ask_forms | No | ||
| published | No | ||
| knowledge_bases | No |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |