Files & billing
Clear ownership, predictable credits, explicit retention.
Organization ownership
Keys and API-created files belong to the organization. Rotating a key does not lose access to previous API jobs. Keys do not grant access to billing administration, account settings, staff tools, or unrelated personal uploads.
Credits
Repair modes use the existing page-credit balance and plan concurrency. Credits are reserved after the server verifies the PDF’s page count. Validation-only reserves no credits and works with a zero balance. It still requires API eligibility.
If API eligibility ends, new processing is blocked. Valid keys can still retrieve and delete retained results. Organization administrators can still revoke keys.
Retention
API uploads default to 14 days, with 90-day and keep options. These defaults are independent of the key creator’s website preferences. Human-review sharing is off for API uploads. Automatic improvements are off unless you explicitly set automatic_improvements: true on a fix_and_validate job. They require API eligibility at enrollment and execution; revoking a key alone does not revoke the file’s opt-in. Deleting the file cancels future work and pending document webhook deliveries.
Deleting a file makes it unavailable immediately. Storage cleanup removes its artifact versions asynchronously; accounting history remains. A signed download link already issued can remain usable until its short expiry, which is at most five minutes.
Upload limits
Read max_upload_size_bytes from GET /account. The configured default is 200 MB. Upload directly to the returned storage destination before its expiry. Never send API credentials to that destination.