A single eval typically spends many MCP / API calls — every tool call the agent under
test makes against a twin is one of the latter. This page is about the first meter.
The rule
One agent eval is charged when a simulation run is graded at finalize, and at
no other moment.
What is free
The short version: a run you get no verdict from is never charged. Concretely —What is charged
On the free plan
run_trials is pinned to one trial per task, so a run there always
costs exactly one eval. The response tells you when it clamped a larger request.What happens at the limit
On the free plan there is no overage. When the month’s 100 evals are used, the next finalize is refused with HTTP 402 — it does not silently bill, and it does not degrade to a cheaper grade. The allowance resets on the 1st. On paid plans, evals beyond the included allowance depend on overage billing being enabled on your subscription. Because a refused finalize happens after your agent has already done the work, the number is quoted up front instead:- Coach / MCP —
run_taskandrun_trialsreturn aneval_costblock with what the run will consume and what is left.get_platform_contextreports both meters. - Dashboard — the running-sessions view and Usage show the same reading.
Checking your usage
- Dashboard → Usage shows used / quota / remaining for both meters and the reset date.
- Over MCP,
get_platform_contextreturns the same snapshot asentitlements.