Skip to main content
Every TrueParser application is governed by plan-based limits. These limits are enforced automatically at runtime and determine how much parsing work your application can perform.

​
Overview

TrueParser tracks three separate kinds of usage:
  • API request limits
  • Document Unit quotas
  • byte usage
In product and plan language, TrueParser refers to one countable unit of parsing consumption as a Document Unit.

​
What Is a Document Unit?

A Document Unit is the common product term for one countable unit of parsing work. Depending on parser family, one Document Unit may correspond to:
  • a page
  • an email/message item
  • a SQL statement
  • a logical file or dataset
This lets TrueParser present one consistent commercial model across very different parsing engines.

​
Request-Rate Limits

TrueParser also enforces request-rate limits for API traffic. Current public request-rate behavior:
  • request limits are app-scoped
  • the current API uses a requests-per-minute limit
  • request-rate limits are separate from Document Unit quotas
If your application exceeds the allowed request rate, the API returns 429 Too Many Requests.

​
Document Units by Family

The current Document Unit mapping is:
FamilyOne Document Unit means
PDFOne page
MsOfficeOne page
OpenDocOne page
MailKitOne top-level email/message item
SQLOne statement
GISOne logical dataset
CADOne processed document

Important

Document Unit is the product term used across plans, pricing, quota enforcement, and customer-facing usage discussions. The exact technical counting rule depends on the parser family listed above.

​
Quota Windows

Document Unit quotas are enforced across multiple windows:
  • per document
  • hourly
  • daily
  • weekly
  • monthly
If a parsing job would exceed the allowed quota window, TrueParser rejects or fails that operation under the current plan rules.

​
Byte Usage

TrueParser also tracks accepted upload size in bytes. Byte tracking is useful for:
  • visibility
  • telemetry
  • operational monitoring
Byte usage is separate from Document Units. A large upload does not automatically mean a large Document Unit count, and vice versa. The platform also enforces a maximum upload size per document under your plan.

​
Usage Visibility

You can inspect current usage through the Usage API. The current API exposes usage as separate request, quota, and byte windows rather than one aggregated usage object. At a high level, the Usage API provides visibility into:
  • request-rate usage
  • Document Unit quota windows
  • byte usage windows

​
Quota Errors

When your application exceeds a limit, the current API can surface errors such as:
  • rate_limit_exceeded
  • quota_exceeded
  • document_quota_exceeded
At a high level:
  • rate_limit_exceeded means your application exceeded an API traffic limit
  • quota_exceeded means your application exceeded a rolling Document Unit window
  • document_quota_exceeded means a single document exceeded the allowed per-document quota
Last modified on April 1, 2026