Skip to main content

ModelError

Model-specific error context.

Usage profiles​

UsageFields and validation
In requestsView fields
In responsesView fields
In webhook payloadsView fields

In requests​

API JSON uses JSON field names (camelCase).

FieldTypePresenceMeaning
modelIdstringOptionalThe model ID that caused the error.
reasonstringOptionalWhy the model failed (e.g., "invalid", "unavailable", "moderation_flagged").
alternativesTriedArray of stringOptionalAlternative models that were tried or could be tried.

In responses​

API JSON uses JSON field names (camelCase).

FieldTypePresenceMeaning
modelIdstringOptionalThe model ID that caused the error.
reasonstringOptionalWhy the model failed (e.g., "invalid", "unavailable", "moderation_flagged").
alternativesTriedArray of stringOptionalAlternative models that were tried or could be tried.

In webhook payloads​

Webhook JSON uses protobuf field names (snake_case).

FieldTypePresenceMeaning
model_idstringOptionalThe model ID that caused the error.
reasonstringOptionalWhy the model failed (e.g., "invalid", "unavailable", "moderation_flagged").
alternatives_triedArray of stringOptionalAlternative models that were tried or could be tried.

Where used​

ReferenceRelationship
Submit client-side tool execution resultsPOST /api/v1/llm/submit-client-tool-results
Submit client-side tool results and wait for the next segmentPOST /api/v1/llm/submit-client-tool-results-sync
Send a message and wait for the resultPOST /api/v1/llm/send-message-sync
llm.generation_completedWebhook JSON uses protobuf field names (snake_case).
ErrorDetailsNested in model
ErrorDetailsNested in model
ErrorDetailsNested in model

Download the public reference contract.

Document: DOC-API-MODEL-model-error.