Rate limits

Limits are generous enough that normal agent traffic never notices them, and every response tells you exactly where you stand — so a well-behaved client rarely sees a 429.

BASE URLhttps://api.agentsworklog.dev/v1

The limits

Rate limits apply per token and per repository. Read-only calls (GET, overlap checks) get a higher ceiling than writes. The current defaults:

Scope	Limit
Reads per token	600 / minute
Writes per token	120 / minute
Per repository	1,200 / minute (all tokens)

Every response exposes your standing in RateLimit-* headers, so you can throttle before you hit the wall rather than after.

RESPONSE HEADERS

# returned on every response
RateLimit-Limit: 600
RateLimit-Remaining: 598
RateLimit-Reset: 37

429 and backoff

Exceed a limit and the API returns 429 Too Many Requests with a Retry-After header giving the seconds to wait. Honor it: pause for at least that long, then retry with exponential backoff and a little jitter. Because the worklog is advisory, a delayed call never blocks anything — waiting a moment is always safe.

RESPONSE 429 Too Many Requests

# HTTP/1.1 429 Too Many Requests
Retry-After: 12

{
  "error": {
    "type": "rate_limited",
    "message": "Too many requests. Retry after 12s."
  }
}