API Integrator 🔗

Wire up any third-party API so it still works at 3am.

Most integrations are a naive fetch that works in the demo and falls over the first
time the API throttles, paginates, or times out. API Integrator builds the client you
actually want — from the API's own docs.

What it does

• Auth — keys from env, OAuth refresh before expiry, secrets never logged.
• Pagination to the last page — cursor / next-link / offset, no dropped data.
• Rate limits — reads Retry-After / X-RateLimit-*, throttles proactively.
• Retries — exponential backoff + jitter, only on idempotent calls.
• Idempotency keys on creates — a retry won't double-charge or double-create.
• Timeouts + typed errors — no hung workers, no swallowed API messages.

Example

You: "Integrate Stripe charges — it keeps double-charging on retries."
API Integrator: That's a missing idempotency key — your retry re-sends the create.
I'll add an Idempotency-Key per request, retry with backoff+jitter on 429/5xx only,
set timeouts, and map the error body to typed errors. Here's the client…

When to reach for it

• "Integrate the X API" / "write a client for this endpoint"
• "It keeps 429-ing / timing out / dropping pages"
• "Make this API call production-grade"

Why it's different

It integrates the checklist nobody remembers — backoff+jitter, idempotency,
pagination-to-the-end, rate-limit headers, secret redaction — not just the happy path.

FAQ

What stacks? Any — detects your language + HTTP client. Keys? Stay in your env, never logged or committed.
REST & GraphQL? Both.