Tools
Execute a tool
Run one operation of a tool agent with typed params. Gated and money verbs refuse unattended calls.
Headers: every response carries x-request-id (quote it in support requests). Send x-trace-id (optional, a UUID) to correlate this call across planes; reusing an id that already ran answers 409 duplicate_execution_id. Pick the body format with format or Accept (application/json, text/yaml, text/markdown, text/plain).
Authorization: send Authorization: Bearer $PLUNGE_API_KEY; X-API-Key: <ozk_ key> is accepted as an alternative.
The response also carries execution_id. The request may be sent as text/yaml instead of JSON.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
Body
application/jsonAvailable options: json, yaml, markdown, text
Response
Execution result 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
Response headers
invalid_format — format must be one of json, yaml, markdown, text
application/json
Missing, invalid, expired or revoked ozk_ key.
Error code: unauthorizedfrom code
refused — fence/gated operation
application/json
unknown_tool
application/json
approval_required — needs a human approval surface; duplicate_execution_id — x-trace-id already used by an earlier run
application/json
payload_too_large — body over 1 MiB (MAX_REQUEST_SIZE)
application/json
invalid_params — needs_input; body carries missing/reserved + the contract
Error code: invalid_paramsfrom code
application/json
connection_required / credential_required — agent needs a connection or key
application/json
rate_limited — Retry-After header
application/json
execution_failed
application/json
agent_unavailable — agent temporarily down
application/json