Retry Budget API

One correct answer for "should I retry, and exactly when?"

The Problem

Every client hand-rolls retry logic, and most get it wrong: ignoring Retry-After, hammering a 429, no jitter (thundering herd), or no budget cap. Different APIs use Retry-After, RateLimit-Reset, X-RateLimit-Reset (epoch), and delta-seconds — inconsistently. This API turns all of it into one decision.

Decision

should_retry based on status class and your retry budget.

Exact delay

AWS-style backoff with full / equal / decorrelated jitter.

Header normalization

Retry-After (date or seconds) + every RateLimit-* variant.

Server wins

Honors server-directed timing over computed backoff.

Free

$0/mo

500 requests/day
All strategies
JSON + MCP

Pro

$9/mo

Unlimited requests
Priority support
MCP integration

curl -X POST https://api.lazy-mac.com/retry-budget-api/v1/decide \ -H 'content-type: application/json' \ -d '{"status":429,"attempt":2,"headers":{"Retry-After":"3"},"policy":{"max_attempts":5}}' # → {"should_retry":true,"delay_ms":3000,"timing_source":"retry-after",...}