Documentation

Errors and troubleshooting

Prismatic returns protocol-compatible error payloads so clients can handle authentication, billing, validation and model availability clearly.

Common errors

400invalid_requestThe JSON body does not match the selected endpoint schema.

401invalid_api_keyThe API key is missing, invalid, revoked or attached to a suspended account.

402billing_requiredSubscription quota is unavailable and PAYG cannot cover the request.

404model_not_foundThe requested public model ID is not enabled or does not exist.

429rate_limit_exceededThe account or API key exceeded its per-minute limit.

503service_unavailableThe request could not be completed due to a temporary service dependency failure.

OpenAI-compatible endpoints return an error object with message, type and code.
Anthropic-compatible endpoints return Anthropic-style error payloads when the request uses the Messages protocol.
Do not parse raw text; branch on HTTP status and code.

401 on every request

Regenerate the key in the dashboard, confirm the prefix is correct and verify the integration did not trim the header.

Model not found

Call GET /v1/models with the same API key and use one of the returned public IDs.

Billing errors

Check active subscription quota first, then wallet balance and PAYG enabled state.

Streaming stops early

Ensure the client consumes the SSE stream to completion so final usage can be captured.