Consistency and request status
Choose eventual or required mind-update consistency and poll retryable work.
mind_consistency controls what happens when the model response is ready before the mind update has completed.
Eventual consistency
eventual is the default. The model response can succeed while the update continues. Inspect x-mind-request-id and x-mind-update-status on the response when your application needs to observe it.
Required consistency
Use required for a non-streaming request when the next operation must observe the completed update.
If the model response succeeds but the update is still processing, the API returns a retryable 503 with a request ID instead of returning a successful-looking response. Poll that request:
curl https://api.pluralmatter.com/v1/requests/req_example \
--header "Authorization: Bearer $PLURALMATTER_API_KEY"While retryable is true, wait at least retry_after_ms before polling again. Stop when status is committed or not_applicable.
Required consistency is not available for streaming requests.