Maximum string length: 65536
Executions
Follow up
Message a run: queued while it runs, a new turn once it finished.
A run still in flight takes the message at its next turn (202 queued); a finished run continues its conversation (its agent session, else a researcher with the prior result as context) and answers 200.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
exec-…)Body
application/jsontext/yaml
Available options: json, yaml, markdown, text
Response
The agent’s reply Response format negotiates via the format field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
application/jsontext/yamltext/markdowntext/plain
Queued for the live run
application/json
missing_text — body needs a non-empty text; invalid_format / invalid_json / invalid_yaml — unreadable body or unknown format
application/json
unauthorized — missing, invalid or revoked ozk_ key
application/json
execution_not_found — no execution with that id for this key (a foreign id answers the same); not_found — no route for this method on this path: every other method answers it
application/json
followup_failed — no answer; retry; upstream_error — a store failed; no detail is returned, retry shortly
application/json