---
title: Errors
description: Handle schema errors, missing facts and completed Jev with a model failure.
icon: triangle-alert
---

Failed requests return problem details (`application/problem+json`) with a stable `code`. Validation problems can include `errors`, each with a `path` and `message`.

```json
{
  "status": 422,
  "code": "invalid_state",
  "detail": "State does not match the decision inputs.",
  "errors": [{ "path": "state.customer_intent", "message": "missing input" }]
}
```

| Status / code | Meaning | Next step |
|---|---|---|
| `400 invalid_request` | Malformed body or unsupported fields. | Use the current native payload and one top-level state. |
| `401 unauthorized` | Missing, expired, invalid or revoked credentials. | Check your API key in the console. |
| `403 access_disabled` | Access for this email was disabled. | Contact [hello@aityx.ai](mailto:hello@aityx.ai). |
| `402 insufficient_balance` | Jev calls require a positive balance; Decision-only calls require funds for the full reservation. | Check Usage; contact the preview team for credits. |
| `422 invalid_state` | Facts do not match the model schema. Nothing extracts facts for you. | Supply matching facts, or add Jev `questions` that establish them. |
| `422 invalid_model` | The supplied model failed validation. | Fix its definition or use the console’s free Check. |
| `422 evaluation_failed` | The model could not evaluate these inputs. | Read the details and check expressions and types. |
| `502 jev_failed` or `invalid_jev_response` | Jev failed or returned unusable results. | Read the problem detail; the native model did not run. |
| `503 jev_unavailable` | Jev execution is unavailable. | Retry later or use matching native facts when available. |
| `504 jev_timeout` | Jev timed out. | Retry with backoff; inspect the detail. |
| `500 internal_error` | An unexpected service failure. | Retry with backoff; report the request identifier if available. |

## HTTP 200 can still mean partial failure

If Jev completes but the following native model fails, the completed Jev result is preserved:

```json
{
  "decision_error": {
    "code": "invalid_state",
    "detail": "State does not match the decision inputs."
  }
}
```

This is an error-field excerpt. The full public response includes Jev’s `answers`, `receipt`, `usage` and `decision_error`; it does not include execution status or billing metadata. The completed Jev operation is charged once at the single rate.

```js
if (response.decision_error) {
  // Keep response.answers and response.receipt; inspect decision_error.
  // Native answers are not available; do not act on them.
}
```

Always check both the HTTP status and `decision_error` for combined calls. Other failed operations release their credit reservation; review settled charges in the console.

Model checks and replay are console/internal operations; there is no public validation or model-authoring route. See [Pricing and limits](/docs/resources/pricing-and-limits).
