Vectorize · Rate Limits

Vectorize Io Rate Limits

The Vectorize API is organization-scoped and Bearer-authenticated. Practical usage is governed primarily by subscription-tier quotas - number of RAG pipelines, monthly pages processed, and index update frequency - rather than granular per-second request ceilings published in the documentation. Specific per-endpoint request rate limits for retrieval, extraction, and deep research are not reconciled in this artifact and should be confirmed with Vectorize, as the API is in Beta and breaking changes may occur.

Vectorize Io Rate Limits is the machine-readable rate-limit profile for Vectorize on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring pipelines, pages, schedule, requests, and jobs.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, RAG, Vectorization, Embeddings, and Retrieval.

6 Limits Throttle: 429
AIRAGVectorizationEmbeddingsRetrievalVector DatabaseRate LimitingQuotasThrottling

Limits

RAG Pipelines organization
pipelines
see plan (1 Free / 3 Starter / 10 Professional / custom Enterprise)
Maximum concurrent RAG pipelines per organization, set by subscription tier.
Pages Processed organization
pages
see plan (1,500/month Free; higher on paid tiers)
Monthly document page-processing allowance for ingestion / extraction.
Index Update Frequency pipeline
schedule
see plan (hourly on Professional)
How often a pipeline refreshes its vector index, gated by tier.
Retrieval Requests organization
requests
see provider documentation
Per-pipeline retrieval query volume; specific rate not documented.
Extraction Jobs organization
jobs
see provider documentation
Iris extraction jobs run asynchronously; poll the result endpoint until ready.
Deep Research Runs organization
jobs
see provider documentation
Deep research runs are asynchronous; poll for the report by researchId.

Policies

Tiered Quotas
Pipeline counts, page allowances, and update frequency raise as accounts move from Free to Starter to Professional to Enterprise.
Asynchronous Polling
Extraction and deep research are async; clients poll the result endpoint until ready is true rather than holding a long connection.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor Retry-After when present.
Beta Stability
The API is in Beta; breaking changes may occur, so clients should pin client-library versions and monitor changelogs.

Sources