Operations
Submit an operation
POST/operations
ScopePer operationRoleCurrent memberBilling1 credit per call
Submits any catalog operation - graph edits, context curation, research, enrichment, CRM and workflow actions, and the MCP tool suite - and returns a durable execution receipt. Arguments are validated against the operation's schema before dispatch. Paid work and writes run in a background worker; nothing is replayed automatically after an ambiguous outcome.
Headers
Idempotency-Keystringoptional
1–128 visible ASCII characters. Retrying with the same key returns the original response; reusing it for different input returns 409.
Body
operationstringrequired
Operation name from GET /capabilities, e.g. research.start_async_research.
argumentsobjectoptional
Input matching the operation's inputSchema. Defaults to {}.
reasonstringrequired
Why this change is being made. 1–500 characters. Stored in the audit trail.
decision_traceobjectoptional
The agent's own assessment behind this write, recorded with every row it changes and returned by GET /graph/traces: reason; basis (source_evidence, model_inference, human_judgment, reported_statement); intent; factors [{criterion, status: supports | contradicts | unknown | not_applicable, rationale}]; evidence [{source_id, quote}] from sources this key can read; definition_refs from POST /graph/decision-inputs; unknowns; alternatives; reported_origin {kind, name, model, run_id}. Without it only reason is recorded, and the trace reports no criteria or evidence.
Response
iduuid
operationstring
statusqueued | running | succeeded | failed | needs_review | canceled | outcome_unknown
resultunknown | null
errorunknown | null
created_atstring
started_atstring | null
completed_atstring | null