Agent skill · software engineering · jeremylongshore
exa-rate-limits
Budget Exa throughput per endpoint and distinguish caller rate limiting from vendor overload and billing exhaustion. Use when operating or reviewing this Exa boundary. Trigger with "Exa rate limits", "review Exa rate limits", or "fix Exa rate limits".
Why this skill is useful
Adds executable scripts for handling Exa API rate limits with exponential backoff and request queuing that aren't in public docs.
What it needs
Requires exa-js, p-queue installed locally. Requires exa account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa Endpoint Rate-limit Control Overview Budget Exa throughput per endpoint and distinguish caller rate limiting from vendor overload and billing exhaustion. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries. Prerequisites The target repository, environment, Exa team, product surface, and accountable owner. The workload's data classification, latency and freshness promise, cost ceiling, and retention policy. Current first-party documentation plus credentials only for a narrowly approved live check. Current Contract Published defaults are 10 QPS for /search, 100 QPS for /contents, and 10 QPS for /answer, while enterprise limits may differ. A 429 can reflect API-key, team, or network limits and should honor Retry-After when present. A 503 SERVICEOVERLOADED is a separate capacity signal. Authentication For normal REST work, inject EXAAPIKEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client. Instructions 1. Inventory endpoint mix, team limits, key-specific controls, concurrency, and burst shape. 2. Set independent token buckets for Search, Contents, Answer, Agent, and administrative traffic. 3. Bound queues and propagate deadlines instead of allowing hidden backlog growth. 4. Honor Retry-After and use capped jitter only for retryable classes. 5. Measure attempts, completions, throttles, overloads, queue age, and cost together. 6. Request a limit change only with measured demand and an owner-approved capacity plan. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. Use Write and Edit only for approved implementation or documentation changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-rate-limits