Skip to main content

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.

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

TierLimitApplies to
Heavy20 req/min/v1/extract, /v1/transcript with Whisper (mode=generate)
Light120 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:
HeaderDescription
X-RateLimit-LimitTotal requests allowed in the current window
X-RateLimit-RemainingRequests remaining before the limit resets
X-RateLimit-ResetUnix 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.
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.
If your use case requires higher rate limits than what the current plans offer, contact Veedcrawl to discuss your needs.