> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration.

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/docs/rate-limits>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/docs/rate-limits.mdx>

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** <https://www.socialfetch.dev/openapi.json>

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages.
- [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples.
- [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths.
- [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install.
- [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 1112 endpoint tools, plus docs_search/docs_read for implementation help.
- [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples.
- [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start.
- [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog.
- [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI).
- [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls).
- [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- [Authentication](https://www.socialfetch.dev/docs/authentication.mdx) — `x-api-key` header, the `SOCIALFETCH_API_KEY` environment variable, and a curl check.
- [Rate limits](https://www.socialfetch.dev/docs/rate-limits.mdx) — no per-minute cap on paid lookups with a key, 200 in flight per workspace, per-minute limits on free and keyless routes, `429`/`503` and `Retry-After`.
- [CLI and agents](https://www.socialfetch.dev/docs/cli-and-agents.mdx) — curl and jq, the `socialfetch` CLI, MCP and the agent skill from a terminal.
- [`/pricing.json`](https://www.socialfetch.dev/pricing.json) — machine-readable pricing: credit packs, plans, free credits and each endpoint's credit cost.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).
- Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`).

---
# Rate limits (https://www.socialfetch.dev/docs/rate-limits)

{/* Every number on this page comes from code. Paid in-flight cap: DEFAULT_MAX_IN_FLIGHT_PER_ACCOUNT and IN_FLIGHT_RETRY_AFTER_SECONDS in apps/api/src/middleware/account-in-flight-limit.ts. Keyless and MCP limits: apps/api/src/middleware/authenticated-api-rate-limit.ts. Free routes: packages/public-api-executors/src/free-endpoint-rate-limit.ts. Webhook test sends: apps/api/src/lib/monitors/webhook-send-rate-limit.ts. Update this page when those change. */}

Paid lookups sent with an API key have **no request quota and no requests-per-second limit**. Your credit balance is what limits them, plus a cap of **200 requests in flight per workspace**. Free routes and requests sent without a key have per-minute limits.

Every limit is the same on every plan.

## Limits by route

| Requests                                                      | Limit                                                | Counted per                       | When you go over                                                                 |
| ------------------------------------------------------------- | ---------------------------------------------------- | --------------------------------- | -------------------------------------------------------------------------------- |
| Paid lookups (`/v1/**`, `/v2/**`) with an `x-api-key`         | No per-minute limit. 200 requests in flight at once. | Workspace (all its keys together) | `503` `temporarily_unavailable`, `reason: "concurrency_limit"`, `Retry-After: 1` |
| Requests without an API key (x402 payments, or a missing key) | 60 per minute                                        | Client IP address                 | `429` `temporarily_unavailable` with `Retry-After`                               |
| `GET /v1/whoami`                                              | 30 per minute                                        | User                              | `429` `temporarily_unavailable` with `Retry-After`                               |
| `GET /v1/balance`                                             | 30 per minute                                        | Workspace                         | `429` `temporarily_unavailable` with `Retry-After`                               |
| `GET /health`                                                 | 60 per minute                                        | Client IP address                 | `429` `temporarily_unavailable` with `Retry-After`                               |
| `POST /v1/query/validate`                                     | 60 per minute                                        | Workspace                         | `429` `temporarily_unavailable` with `Retry-After`                               |
| `POST /v1/query/suggest`                                      | 10 per minute and 300 per day                        | Workspace                         | `429` `temporarily_unavailable` with `Retry-After`                               |
| Webhook endpoint test sends                                   | 10 per minute                                        | Webhook endpoint                  | `429` with `Retry-After`                                                         |
| Webhook redeliveries                                          | 30 per minute                                        | Webhook endpoint                  | `429` with `Retry-After`                                                         |
| [MCP](/docs/integrations/mcp) (`/mcp`), signed in             | 600 per minute                                       | Signed-in user                    | `503` `temporarily_unavailable` with `Retry-After`                               |
| MCP, not signed in                                            | 60 per minute, and 15 unpaid tool calls per minute   | Client IP address                 | `429` `temporarily_unavailable` with `Retry-After`                               |

Per-minute limits use a sliding one-minute window, not a fixed clock minute.

The in-flight cap isn't a rate: a slot frees as soon as a request finishes, so a workspace can send far more than 200 requests a minute as long as no more than 200 are running at once.

## Headers

* **`Retry-After`**: sent with every `429` and with `503` `temporarily_unavailable`. It's a whole number of seconds to wait before retrying.
* **`X-Request-Id`**: sent on every response. Quote it to support.

The API doesn't send `X-RateLimit-Limit`, `X-RateLimit-Remaining` or `RateLimit-*` headers. Use `Retry-After` when you're refused, and [`GET /v1/balance`](/docs/api/v1/balance) (free) to see how many credits are left.

## What a refusal looks like

A `429` has the same `{ error }` body as every other error:

```http
HTTP/1.1 429 Too Many Requests
Retry-After: 12
Content-Type: application/json

{
  "error": {
    "code": "temporarily_unavailable",
    "message": "This endpoint is temporarily rate limited. Retry later.",
    "requestId": "req_..."
  }
}
```

Going over the in-flight cap returns `503` with `reason`:

```json
{
  "error": {
    "code": "temporarily_unavailable",
    "message": "Too many requests in progress for this account (limit 200 at once). Retry after a request finishes.",
    "requestId": "req_...",
    "reason": "concurrency_limit"
  }
}
```

Neither response costs credits.

## Retrying

1. On `429` or `503`, wait the number of seconds in `Retry-After`, then retry the same request.
2. If there's no `Retry-After`, back off with a growing, jittered delay (for example 1 s, 2 s, 4 s).
3. To stay under the in-flight cap, run paid lookups through a worker pool of at most 200 per workspace.
4. Don't retry `402` `insufficient_credits` in a loop: add credits first. See [Credits](/docs/credits).

To check that you're within a limit from the terminal:

```bash
curl -sS -i \
  -H "x-api-key: $SOCIALFETCH_API_KEY" \
  "https://api.socialfetch.dev/v1/balance"
```

A full retry wrapper is in [Errors](/docs/errors#429-and-503).