> ## Documentation Index
> Fetch the complete documentation index at: https://docs.veedcrawl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate Limits for the Veedcrawl API

> Veedcrawl enforces two rate limit tiers based on computational cost. Learn the limits, response headers, and what to do when you hit a 429.

Veedcrawl uses two rate limit tiers based on the computational cost of each operation. Heavier operations like AI transcription and extraction have a lower limit to protect processing capacity. Lighter operations like metadata lookups and profile endpoints run at a much higher limit suitable for bulk workflows.

## Rate limit tiers

| Tier | Limit | Applies to |
| - | - | - |
| Heavy | 20 req/min | `/v1/extract`, `/v1/transcript` with Whisper (`mode=generate`) |
| Light | 120 req/min | `/v1/metadata`, native transcript (`mode=native`), profile endpoints |

## Rate limit headers

Every API response includes headers so you can track your current window:

| Header | Description |
| - | - |
| `X-RateLimit-Limit` | Total requests allowed in the current window |
| `X-RateLimit-Remaining` | Requests remaining before the limit resets |
| `X-RateLimit-Reset` | Unix timestamp when the current window resets |

## When you hit a rate limit

If you exceed the limit for a tier, the API returns a `429 Too Many Requests` response. Check the `X-RateLimit-Reset` header to find out when your window resets and retry after that timestamp.

<Tip>
  Profile endpoints (`/v1/tiktok/profile` and `/v1/instagram/profile`) are on the light tier — 120 requests per minute. Each call can return up to 24 videos, so that's up to **2,880 posts** of engagement data available to an agent in a single minute.
</Tip>

<Note>
  If your use case requires higher rate limits than what the current plans offer, contact Veedcrawl to discuss your needs.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.