/v1 routes
and on /mcp. Over a limit you get 429 rate_limited with a Retry-After header in seconds.
The limits
The per-IP limits are high on purpose: every user of one AI platform (ChatGPT, Claude, Grok) shares a few
of its IP addresses. The limits that matter are per key, per email and per MC/DOT number.
The per-minute and per-10-minute limits are counted on each Lanesurf server, so treat them as the
most you should send, not a target.
What a 429 looks like
next_step. Over MCP, a limited tool call returns the same JSON as an error result,
with retry_after_seconds.
How to back off
- On
429, wait theRetry-Afterseconds (orretry_after_seconds), then retry once. - Don’t retry in a tight loop. A second
429means wait again, longer. - Poll slowly. A load’s offers change over minutes, not seconds: poll
GET /v1/loads/{id}orGET /v1/carrier/bidsevery few minutes. Stop polling a load that iscovered,inactiveordeleted, and slow down onstalled. - Spread bulk work (many trucks or lanes) out instead of sending it all at once.
POST /v1/loads after a 429 is safe with the same Idempotency-Key. See Idempotency and retries.