Operations

Some API requests start asynchronous work rather than completing everything in the original response. Operations resources expose the status and result of that work.

Discover operation endpoints

1
async () => Object.keys(spec.paths).filter((path) => path.startsWith('/operations'))

Poll deliberately

Return the operation identifier from the initiating request. Poll at a reasonable interval from the client or scheduled code—not a tight loop inside one short-lived MCP execution. Stop on the documented success or failure state and surface the complete error details when it fails.

An accepted request is not proof that the underlying work succeeded. Verify both the terminal operation and the resource it was meant to change. Keep the request ID and operation ID together for support and audit investigations.