Tensorlake · Rate Limits

Tensorlake Rate Limits

Tensorlake does not publish fixed numeric per-minute request-rate limits for the Document Ingestion API. In practice throughput is governed by plan-level concurrency (for example up to 2 concurrent sandboxes on Free, up to 100 on On-Demand, and up to 1,000 on Pro) and by the credit / page allowance of the plan rather than by a per-endpoint request cap. Parsing and extraction run as asynchronous jobs, so large workloads are absorbed by the job queue and read back by polling or webhook rather than by holding open synchronous requests.

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

It captures 3 rate-limit definitions, measuring requests, sandboxes, and pages.

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

Tagged areas include Document Extraction, Document Ingestion, OCR, AI, and Rate Limiting.

3 Limits Throttle: 429
Document ExtractionDocument IngestionOCRAIRate LimitingQuotas

Limits

API Request Rate account
requests
not published
No fixed numeric request-rate limit is documented for the REST API.
Concurrent Sandboxes account
sandboxes
per plan (Free ~2, On-Demand ~100, Pro ~1,000)
Concurrency ceiling is set by the subscription tier.
Document Page Allowance account
pages
per plan / credit balance
Document ingestion is metered by the page against the plan's credit allowance.

Policies

Asynchronous Jobs
Parse and extraction requests return a job id immediately; results are retrieved by polling GET /documents/v2/parse/{parse_id} or via webhook, smoothing bursty load.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources