TESSEN Platform
Documentation
Docs/Models
MODELS / PROJECT ZERO

ZERO limits

ZERO Alpha allows 200 requests a day and 30 a minute per developer, and resets at 00:00 UTC.

Restricted accessPrivate enrollment. Alpha limits can change.

Every limit is enforced by the Gateway before a request is served, and every refusal says which limit closed and when it clears.

limitWhat closedClears
rateMore than 30 requests in the current UTC minute.At the start of the next minute.
concurrencyToo many requests in flight at once.In a few seconds.
requestsYour 200-request daily allowance is used.At 00:00 UTC.
dailyYour daily spend allowance is used.At 00:00 UTC.
globalThe program's shared daily capacity is used.At 00:00 UTC.
provider_capacityThe serving capacity is momentarily saturated.In seconds.

A refusal is HTTP 503 zero_capacity_unavailable with error.limit, error.reset_at and a Retry-After header. It is not a 429. Refused requests cost nothing and do not count against your allowance.

503 REFUSAL
{  "error": {    "code": "zero_capacity_unavailable",    "message": "You have used today's free ZERO Alpha request allowance.",    "capacity_state": "exhausted",    "limit": "requests",    "owner": "you",    "actions": ["wait", "add_credits", "learn_tessen_node"],    "reset_at": "2026-10-30T00:00:00+00:00"  }}

Client behaviour

  • Wait for Retry-After or reset_at; do not retry in a tight loop.
  • Call GET /v1/zero/status before a batch of work to read allowance.requests_remaining.
  • Coding agents may send several requests per task; the per-minute limit is the one an agent meets first, and OpenCode retries automatically.

Search documentation

Titles, headings and guides↑ ↓ navigate · Enter open