EVALUATION_LIMIT

An evaluation cap is exhausted for today or for this credential's lifetime. HTTP 429. Wait for the daily reset or ask for a full credential.

The evaluation tier is capped — per credential per day, over a credential's lifetime, per source network per day, and per ruleset per day — and one of those caps is spent. This is an upgrade prompt, not a wall.

The envelope

{"ok": false,
 "error": {"code": "EVALUATION_LIMIT",
           "message": "the daily evaluation cap for this credential is spent; it resets at 00:00 UTC. A full credential has no evaluation caps.",
           "docs": "https://docs.agents.jaxon.ai/errors/evaluation-limit.md"},
 "versions": {"...": "..."}}

Why a fresh token does not help

Two of the meters sit beneath the credential and key on things a token cycle cannot change: the source network range and the ruleset hash. Three fresh tokens from one range share one meter. Minting credentials in a loop is treated as a workload, not an evaluation, and the cap converts it into this code.

The fix

• Wait. Daily caps reset at midnight UTC. GET /v1/account (or dsail_get_account_status) reports the current position so a limit does not surprise you.
• Ask for a full credential. A production integration past the evaluation caps is issued one by Jaxon. It has no evaluation caps, owns its own namespace for saved rulesets, and can be bound to a chat connector's library so one review experience spans chat and repository.

Do not retry in a tight loop; the answer does not change until the reset.

See also: [CREDENTIAL_SCOPE](credential-scope.md), Error codes.