List agent templates
List the agent templates a new agent can start from: tested agents kept in the template workspace (the inbound receptionist, speed-to-lead, review request and the rest of the set). Each has a `template` handle, the `name` a copy gets, a one-line description, its channels, its `section` (incoming, enquiries or customers) and its `direction` (inbound or outbound). Only agents a platform admin has listed with add_agent_template appear; an unlisted agent in the template workspace is a draft nobody sees. Read one in full with get_agent_template; start an agent from one with create_agent_from_template.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/list_agent_templates" \ -H "Content-Type: application/json" \ -d '{}'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}List agent prompt improvements POST
List this agent's Optimise-Prompt sessions, newest first. Each session is one run of the self-improving prompt loop and reports its status (pending / running / proposed / accepted / rejected / error), the before/after pass rate on the selected scenarios, the exit reason (e.g. 'Exited: 100% pass + full-set regression sweep clean' or 'Exited: max_iterations reached (10)'), and when it was created. Use this to see whether the last optimise run produced a proposal you can accept_agent_prompt_improvement, or to review past runs. Returns an empty list when the agent has never been optimised. agentId is optional and defaults to the agent you're editing.
List alert fires POST
List recent alert FIRES across this workspace for a window (24h / 3d / 7d, default 24h), the same payload the Alerts review dashboard renders: total fires, how many distinct rules fired, the top-firing rule, a bucketed activity timeline, and the fired list (each fire's rule name, fired-at time, value, baseline, reason, delivery status, and the triggering call's sessionId). Use this to answer 'what alerts have fired lately / which rule is noisiest?'. To read or change the alert RULES themselves use list_alerts; this reads their firings. Workspace-scoped and read-only, it never re-scores a call or changes a rule.