Changelog

Updates and improvements to Agentic Document Extraction.

​

March 20, 2026: DPT-2 mini Updates

DPT-2 mini Updates

includes the following updates:

• Improved table accuracy: Table parsing accuracy has been improved for simple tables.
• Visual element captions: now generates concise captions for image-based chunk types, including figure, logo, card, attestation, and scan_code.

These changes apply to all snapshots.

To learn more, go to DPT-2 mini.

​

March 12, 2026: New Parsing Model Snapshots and Parse Password-Protected Files

New Parsing Model Snapshots

New snapshots of and are now available:

• : dpt-2-20260302
• : dpt-2-mini-20260302

dpt-2-20260302 builds on previous versions with several improvements, including:

• Table boundary detection: Tables that were previously split into multiple chunks are now correctly identified as a single table.
• Improved large table accuracy: Large tables are now parsed more accurately.
• Special characters returned as Unicode: Characters such as asterisks are now returned as their Unicode characters (for example, *) rather than as spelled-out strings like asterisk.

The table boundary detection and large table accuracy improvements are also included in dpt-2-mini-20260302.

To learn more about parsing models and snapshots, go to Document Pre-Trained Transformers (Parsing Models).

How This Affects Your Results

If your code uses dpt-2-latest, dpt-2, dpt-2-mini-latest, or dpt-2-mini, it now points to these new snapshots and your parsing results may change.

To receive the latest improvements automatically, continue using a -latest alias. To maintain consistent results over time, pin your code to a specific snapshot (for example, dpt-2-20251103). For more information, go to Why Model Versioning Matters.

Parse Password-Protected Files

Accounts with Zero Data Retention (ZDR) enabled can now parse password-protected files. Pass the document’s password in the password parameter when calling the ADE Parse or ADE Parse Jobs APIs, or using the Python and TypeScript libraries.

For more information, go to Parse Password-Protected Files.

​

March 4, 2026: LandingLens and LandingEdge Documentation Has Moved

LandingLens and LandingEdge Documentation Has Moved

Documentation for LandingLens and LandingEdge has moved to landinglens.docs.landing.ai.

Existing links to docs.landing.ai/landinglens and docs.landing.ai/landingedge will automatically redirect to the new site.

​

February 26, 2026: Extraction Schema Validation Fix

Extraction Schema Validation Fix

The API now correctly validates anyOf sub-schemas before processing begins. If a sub-schema within anyOf is missing both the type and anyOf keywords, the API returns a 400 error identifying the invalid path in the schema. Previously, this caused an unexpected extraction failure.

For more information about extraction response statuses and errors, go to Troubleshoot Extraction.

​

February 12, 2026: In Preview - Confidence Scores for Parsing

Confidence Scores

The parsed results now include confidence scores for text, marginalia, card, and table chunks, as well as table cells.

Confidence scores measure the confidence level of parsed text in Markdown with respect to the actual text or visual data present in the document.

Each score ranges from 0.0 (low confidence) to 1.0 (high confidence). Lower values indicate regions where the model was less certain about the output.

The confidence score feature is in Preview. The numeric range and distribution may change as we continue to develop and improve the model.

Use Confidence Scores in the Playground

After parsing a document in the Playground, turn on the Confidence toggle (the toggle is only available when using ).

In the Markdown tab, the confidence score displays next to the chunk type.

Review Low-Confidence Sections

Low-confidence sections (with scores of 0.95 or lower) are highlighted in yellow in the Playground. Highlighting low-confidence sections helps you quickly identify content that may need review.

• Text, card, marginalia chunks: Specific text spans within a chunk are highlighted. A single chunk can contain multiple highlighted spans.
• Tables: Each cell has its own confidence score. If a cell has a low score, the entire cell is highlighted.

Why is 0.95 the threshold for low confidence scores?

The Playground highlights content with confidence scores of 0.95 or lower because this is the threshold used internally to evaluate parsing quality.

This threshold works well for general review workflows, but your use case may require a different threshold. When using the API, you can implement custom logic to identify and route content based on confidence scores that match your specific requirements.

Why don’t I see the confidence score for files I uploaded in the past?

The confidence score displays for documents parsed on February 12, 2026 or later. If you parsed a document before that date, the Playground does not re-process documents.

If you want to see the newest results for a file that you’ve already parsed, re-upload it to the Playground.

Use Confidence Scores in the API Response

The grounding object in the API response includes all the confidence information displayed in the Playground:

• Confidence scores for each chunk and table cell
• For text chunks with low-confidence spans: the text, confidence score, and character positions (start, end) for each span

This allows you to programmatically identify and route low-confidence content for review in your applications. Learn more in Confidence Scores.

​

DPT-1 Will Be Deprecated on March 31, 2026

will experience a technology change on February 17, 2026 that may affect parsing results, and will be fully deprecated on March 31, 2026.

If you are using , update your code to use DPT-2. To learn more about DPT models, go to Document Pre-Trained Transformers (Parsing Models).

DPT-1 Underlying Technology Change: February 17, 2026

One of our underlying solution providers for is upgrading their technology on February 17, 2026. While will continue to function, table parsing behavior and results may change for some documents.

DPT-1 Deprecation: March 31, 2026

Longer term, we plan to deprecate . After March 31, 2026, will no longer be supported and will be scheduled for shutdown.

Impacted Users and Next Steps

Check the scenarios below to determine if you are impacted and what action to take. Complete any necessary migration before February 17, 2026.

• Scenario 1: You Specify DPT-1 as the Model Parameter
• Scenario 2: You Use the Legacy API Endpoint
• Scenario 3: You Use the Legacy Python Library

We recommend that you test any changes in staging first, especially if you process table-heavy documents. After testing in staging, deploy changes to production.

Scenario 1: You Specify DPT-1 as the Model Parameter

You are in this scenario if:

• You call the /v1/ade/parse or /v1/ade/parse-jobs endpoint

AND

• You set the model parameter to dpt-1, dpt-1-latest, or dpt-1-20250615

What to do:

Update your code to use model=dpt-2-latest or a specific snapshot.

For example, run the command below to use the latest snapshot of .

curl -X POST 'https://api.va.landing.ai/v1/ade/parse' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -F 'document=@document.pdf' \
  -F 'model=dpt-2-latest'

Scenario 2: You Use the Legacy API Endpoint

You are in this scenario if you call the legacy endpoint: v1/tools/agentic-document-analysis.

What to do:

1. Migrate to the /v1/ade/parse endpoint. To learn how to use this endpoint, go to ADE Parse.

2. When calling the endpoint, use model=dpt-2-latest or a specific snapshot.

   For example, run the command below to use the latest snapshot of .

   curl -X POST 'https://api.va.landing.ai/v1/ade/parse' \
     -H 'Authorization: Bearer YOUR_API_KEY' \
     -F 'document=@document.pdf' \
     -F 'model=dpt-2-latest'
   

Scenario 3: You Use the Legacy Python Library

You are in this scenario if you use the legacy agentic-doc Python library.

What to do:

1. Migrate to the library. To learn how to use this library, go to Python Library.

2. Update your code to use model="dpt-2-latest" or a specific snapshot when calling the parse() function.

   For example, use this code to use the latest snapshot of .

   response = client.parse(
       document=Path("/path/to/file/document"),
       model="dpt-2-latest"
   )
   

​

February 5, 2026: Load Multiple Files at Once

When using the Playground, you can now load up to 10 files at once. After opening the Upload dialog box, navigate to and select multiple files or simply drag and drop the files.

Parsing Status

After loading multiple files into the Playground, a floating dialog box appears in the bottom right corner, showing the parsing progress for each file. If a file fails to process, an error message displays in this area.

Multiple File Upload Not Available with ZDR

When Zero Data Retention (ZDR) is enabled, only one file can be loaded at a time.

​

January 30, 2026: Python and TypeScript Libraries Support Saving Responses to Local Directories

Python and TypeScript Libraries Support Saving Responses to Local Directories

The and libraries now support saving API responses directly to local directories as JSON files.

The save parameter:

• Creates the specified directory if it doesn’t exist
• Saves the response with the filename format: {input_file}_{method}_output.json
• Works across all three core functions: parse, split, and extract

Availability

• Python library: v1.4.0 (parameter: save_to)
• TypeScript library: v2.0.0 (parameter: saveTo)

Example

These examples show how to save the API response when parsing.

Python

from pathlib import Path
from landingai_ade import LandingAIADE

client = LandingAIADE()

response = client.parse(
    document=Path("/path/to/document.pdf"),
    model="dpt-2-latest",
    save_to="output_folder"  # optional: saves as {input_file}_parse_output.json
)

For more information, go to Python Library or TypeScript Library.

​

January 6, 2026: Table Cell Position Information in Parsing Results and Credit Transfers at Upgrade

Table Cell Position Information

When you parse documents with tables, the API response now includes row and column position information for each table cell in the grounding object. This allows you to map parsed data back to specific cell locations in the original table.

Each table cell in the grounding object now includes a position field with:

• row: Row position (zero-indexed)
• col: Column position (zero-indexed)
• rowspan: Number of rows the cell spans
• colspan: Number of columns the cell spans
• chunk_id: Associated chunk identifier

Why this matters:

• Precise cell mapping: You can now identify the exact row and column for each piece of data in your table
• Merged cell detection: The rowspan and colspan values indicate when cells are merged
• Easier data validation: You can verify that extracted data came from the expected cell location

For more information about the grounding object structure, go to Table Cell Position Information.

Credits Transfer When Upgrading Plans

If you upgrade a subscription plan (Team or Visionary), your unused credits are now transferred to your new plan. The transferred credits are added to your next billing cycle and expire at the end of that cycle.

This applies when you:

• Upgrade within the same tier (for example, Team 55K credits per month to Team 110K credits per month)
• Upgrade from Team to Visionary
• Upgrade from monthly to annual billing

Transferred credits appear as additional credits but don’t change your base credit limit. Overage is calculated against your base credits only. Transferred credits automatically offset overage charges and appear as a credit grant line item on your bill.

If you downgrade your subscription plan and have unused credits, those credits do not transfer to the new plan. You have until the end of your current billing cycle to use the remaining credits.

For more information, go to What happens to my credits when I upgrade?

​

December 16, 2025: Extraction Model Fallback Tracking & Parse Jobs 206 Status

This release includes a new metadata field for tracking extraction model fallbacks, improved HTTP status codes for parse jobs with partial results, improved spreadsheet parsing, and documentation updates to Parse Jobs endpoint names.

Fallback Model Version Field

When using extraction model extract-20251024 with a complex JSON schema, the API may automatically fall back to extract-20250930 to complete the extraction. This fallback behavior already existed, but you could not determine if a fallback had occurred.

The API response now includes a metadata.fallback_model_version field. This field shows which extraction model was actually used when the API falls back from your requested model.

Why this matters:

• Know if your schema is too complex: If the field contains a value, your JSON schema triggered a fallback. You can simplify the schema to use the capabilities of extract-20251024.
• Understand which model processed your data: You now have visibility into which extraction model was actually used, which is important for understanding extraction results and debugging.

For more information about the response structure, go to JSON Response for Extraction.

For guidance on reducing schema complexity, go to Reduce JSON Schema Complexity.

Parse Jobs: Partial Content Now Returns a 206 Status

When you retrieve parse job results with the ADE Get Parse Jobs API, the API now returns a 206 (Partial Content) HTTP status code if some pages failed during processing.

The failed_pages array and failure_reason field that were already in the API response continue to provide details about which pages failed and why.

For more information, go to Troubleshoot Parsing.

Improved Title Detection in Spreadsheets

The API now better identifies titles in spreadsheets. When a spreadsheet has a title or text at the top, the API now returns:

• The title as a separate text chunk
• The table as its own chunk

You Can Now Resubscribe and Cancel in Interface

If you want to resubscribe to or cancel a subscription plan (Team or Visionary), you can now do so directly in the interface. For full details, go to Pricing & Billing.

Updated API Endpoint Names

We’ve updated the names of two Parse Jobs API endpoints:

• “List Async Jobs” is now “ADE List Parse Jobs”
• “Get Async Job Status” is now “ADE Get Parse Jobs”

This is a documentation-only change. The endpoint URLs have not changed. Your existing API calls will continue to work without any modifications.

​

December 4, 2025: Document Splitting Is Now in Preview

Split Documents with the New Split API (Preview)

We’re releasing a Preview of the API, which classifies and separates a parsed document into multiple sub-documents based on Split Rules you define. This is useful when you receive batched documents containing multiple document types or multiple instances of the same document type.

For example, a financial institution processing KYC documentation might receive a single PDF containing bank statements, utility bills, and identification documents for a customer. The API can automatically classify and separate each document type, enabling downstream processing systems to route each document appropriately.

Get the full details in Split.

is in Preview. This feature is still in development and may not return accurate results. Do not use this feature in production environments.

How It Works

1. Parse your document using the API to generate Markdown output
2. Define Split Rules that describe the document types or sections you want to identify
3. Call the API with the parsed Markdown and your Split Rules
4. The API returns each classified sub-document with its full Markdown content

For the complete workflow, go to Process Overview.

When to Use Split

Use the API when you need to:

• Separate batched documents containing multiple document types (invoices, receipts, contracts)
• Split documents with repeated sections by unique identifiers (multiple pay stubs by date)
• Organize multi-section documents into logical parts (academic articles with body, references, supplemental materials)
• Route different document types to appropriate downstream systems

For more use cases, go to Example Use Cases.

How to Use Split

The API is available through multiple interfaces:

• Playground: Interactively create and test Split Rules
• API: Integrate directly into your applications
• Python Library: Integrate into Python-based application with our Python library
• TypeScript Library: Integrate into TypeScript-based application with our TypeScript library

​

December 4, 2025: Revamped Playground

Revamped Playground

We’ve launched a complete redesign to our Playground! The updated Playground now guides you through each step of the document processing process: Parsing, Splitting, and Extraction. Simply click a tile to get started!

You can now see all the files you’ve processed on your Playground homepage, including which tools you’ve run on each file (parse, extract, split).

We’ve also made it easier to get help with by adding Product Update and Resources panels.

​

November 27, 2025: Updates to Parse Jobs

The Parse Jobs API Supports up to 6,000-Page Documents

The ADE Parse Jobs API now supports documents up to 6,000 pages long. Previously, the limit was 1,000 pages.

For more information, go to Rate Limits for ADE Parse Jobs.

Improved Support for Partial Content with the Parse Jobs API

We’ve improved how the ADE Parse Jobs API handles partially parsed documents.

Previously, if any pages failed to process, the job would fail with status failed.

Now, the API processes all pages in the document. If some pages fail, the job completes with status completed, and the successfully processed pages are returned in the results.

The failed_pages array in the metadata lists which pages failed, and the failure_reason field provides details about the failures.

For more information, go to Troubleshoot Parsing.

The Parse Jobs API Supports Additional Storage Providers for ZDR

When calling the ADE Parse Jobs API with zero data retention (ZDR) enabled, you must include the output_save_url parameter. This parameter specifies the URL where parsed results are saved, ensuring that does not store the document content.

We have now tested and confirmed support for Amazon S3, Azure Blob Storage, and Google Cloud Storage. Other storage providers that support PUT or CREATE operations via public or presigned URLs may also work.

For detailed information, go to Requirements for ZDR.

​

November 17, 2025: Credit Rounding Updated

Credit Rounding Updated

Credit usage for the API and is now rounded up to the nearest tenth decimal place instead of the nearest whole credit.

For example, if a calculation results in 1.67 credits, the cost is now rounded up to 1.7 credits (previously would have been rounded up to 2 credits).

For more information, go to Pricing & Billing.

​

November 12, 2025: DPT-2 mini Launch

DPT-2 mini Preview

We’ve released a preview of , a lightweight parsing model optimized for simple, digitally native documents.

consumes fewer credits than other parsing models, making it a cost-effective option for straightforward document processing.

is in Preview. This model is still in development and may not return accurate results. Do not use this model in production environments.

Credit Consumption

consumes fewer credits than other parsing models. If ZDR is enabled, credit consumption increases.

For pricing details, go to Pricing & Billing.

​

November 10, 2025: DPT-2 Is Now Generally Available, Spreadsheet Support, and Credit Rounding

DPT-2 Is Now Generally Available

, the latest series of parsing models for , is now generally available (GA). As part of going GA, we’re releasing this new snapshot: dpt-2-20251103. This updated version offers improvements to table parsing, figure captioning, and chunk detection.

For more information about parsing models, go to Document Pre-Trained Transformers (Parsing Models).

How This Affects Your API Calls

The new snapshot dpt-2-20251103 is now the default model. If you call the ADE Parse or ADE Parse Jobs API without specifying a model parameter (or if you use dpt-2-latest), your API calls will automatically use this latest snapshot.

Your parsing results may change with this update due to improvements in table parsing, figure captioning, and chunk detection.

Choose Your Approach

You can choose between two approaches when setting the model parameter:

Get automatic improvements:

• Omit the model parameter, or set it to dpt-2-latest
• Your API calls will automatically use the latest snapshot
• You’ll receive parsing improvements as new snapshots are released
• Parsing results may change when new versions are released

curl -X POST 'https://api.va.landing.ai/v1/ade/parse' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -F 'document=@document.pdf' \
  -F 'model=dpt-2-latest'

Maintain consistent results:

• Set the model parameter to a specific snapshot (like dpt-2-20251103)
• Your parsing results will remain consistent over time
• You won’t automatically receive improvements from new snapshots

curl -X POST 'https://api.va.landing.ai/v1/ade/parse' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -F 'document=@document.pdf' \
  -F 'model=dpt-2-20251103'

For more information about model versioning and when to use each approach, go to Model Versions and Snapshots.

Spreadsheet Support

can now parse the following file types:

• CSV (comma-separated values)
• XLSX (Microsoft Excel)

For more information, go to Supported File Types.

Credits Are Now Rounded Up

Credit usage for the API is now rounded up to the nearest whole credit. For more information, go to Pricing & Billing.

​

October 31, 2025: Annual Subscriptions

now offers annual subscriptions for . Annual subscriptions offer more credits per dollar when compared to monthly subscriptions. Explore our pricing plans here: https://va.landing.ai/plan.

You can now upgrade and downgrade your subscription plans directly in the Playground. For more information, go to Pricing & Billing.

​

October 30, 2025: New Extraction Model with Improved Accuracy

New Extraction Model: extract-20251024

We’ve released a new extraction model, extract-20251024, which offers improved extraction capabilities. An extraction model powers the field extraction capabilities of the API. It analyzes your Markdown content and extracts structured data according to your JSON schema.

The new model is now available for testing. It will become the default model soon.

What’s New

Model extract-20251024 provides:

• Better support for field extraction for large arrays. For example, the API can better extract data from multi-page tables.
• More deterministic outputs.
• Consistent handling of missing fields (returns null for all missing values).
• Improved accuracy for complex fields.
• Enhanced support for large documents. The model can reliably process 20+ pages of Markdown content.

Test the New Model

You can test how your JSON schema performs with the new extraction model by specifying the model parameter in your API calls.

Example:

curl -X POST 'https://api.va.landing.ai/v1/ade/extract' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -F 'schema={"type": "object", "properties": {"field1": {"type": "string"}, "field2": {"type": "string"}}, "required": ["field1", "field2"]}' \
  -F 'markdown=@document.md' \
  -F 'model=extract-20251024'

For details on how to specify a model, go to Extraction Model Versions.

Prepare Your JSON Schema

Model extract-20251024 has different JSON schema requirements than the previous model (extract-20250930). Review your schemas to ensure compatibility before the new model becomes the default.

Key changes to be aware of:

• Limited keyword support (only specific JSON Schema keywords are supported).
• Use nullable keyword instead of type arrays with null.
• Only string enums are supported.
• Complex schemas may fall back to the previous model.

For a complete migration checklist and detailed guidance, go to Migrate to extract-20251024.

​

October 27, 2025: New File Types, Increased Page Limits & EU Subscriptions

Support for Text Documents & Presentations

can now parse the following file types:

• DOC (Word)
• DOCX (Word)
• PPT (PowerPoint)
• PPTX (PowerPoint)
• ODT (OpenDocument Text)

For more information, go to Supported File Types.

Document Length Limit Increased to 100 Pages

now supports documents with up to 100 pages in both the Playground and via the API.

Need to parse longer documents? Use the ADE Parse Jobs API to parse documents that are up to 1,000 pages or 1 GB.

For more information, go to Rate Limits.

Subscriptions Now Available for EU Users

The EU-hosted version of now offers monthly subscription plans. To see the plans and upgrade, go to the EU Plans page.

The credit-based monthly subscription plans are designed to deliver more value and features to your team.

All EU users start on our pay-as-you-go plan that comes with free credits to help you get started! Once you’re ready for production, upgrade to a monthly subscription plan to get access to these features:

• More credits per dollar
• One-click Zero Data Retention (ZDR)
• Organization management
• Role-based access control (RBAC)
• API key management

​

October 10, 2025: New APIs for Parsing Large Documents

New APIs for Parsing Large Documents

We have released new APIs that allow you to create parsing jobs. These APIs allow you to process large documents without blocking other operations, improving performance and user experience.

To learn more about this workflow, go to Parse Large Files (Parse Jobs).

API Reference

To learn more, go to the reference pages for new APIs:

• ADE Parse Jobs
• ADE Get Parse Jobs
• ADE List Parse Jobs

​

September 30, 2025: DPT Models

Document Pre-Trained Transformers: You Can Now Pick a Parsing Model

In this release, we’re previewing a concept called (DPT). A DPT is the model that powers the parsing capabilities of the ADE Parsing APIs. The DPT identifies document layouts and chunks, then generates descriptive explanations (captions) for those chunks.

The API initially launched with a single DPT model called . Because there was only one DPT, it was not surfaced to users.

We are now introducing , which offers:

• Improved performance for complex tables
• Support for new chunk types (including barcodes and ID cards)
• More precise captioning for figures

With multiple DPT models now available, you can now select a DPT in both the Playground and when calling the API directly.

For more information about models and how to use them, go to Document Pre-Trained Transformers (Parsing Models).

ADE Parse and ADE Extract Are Now Generally Available

The and APIs are now Generally Available (GA). We recommend using these endpoints moving forward.

New Python Library

We’ve launched a new Python library to support extending the APIs: the library.

Key benefits:

• Support for the and APIs.
• Support for setting the .
• The library is automatically generated from our API specification, ensuring you have access to the latest endpoints and parameters.
• The library is lightweight, which makes it suitable for resource-constrained environments like AWS Lambda functions.

agentic-doc Library Transitioned to Legacy Status

The agentic-doc Python library has been transitioned to legacy status.

Migrate to the new library, which is now the recommended Python library for .

For more information, go to Legacy Library: agentic-doc.

The tools/agentic-document-analysis Endpoint Is Now Legacy

This endpoint has been transitioned to legacy status: https://api.va.landing.ai/v1/tools/agentic-document-analysis.

Migrate to the new and APIs.

​

September 23, 2025: Updated Overage Structure for New Subscriptions

Updated Overage Structure for New Subscriptions

If you enroll in an subscription plan (a Team or Visionary plan) on or after September 23, 2025, you can continue using ADE after you’ve used all of your included monthly credits. We call this overage usage.

Overage fees are billed separately from your base subscription.

Pricing & Plans

To get detailed information about pricing and overages, go to Pricing.

​

September 12, 2025: Separate APIs for Parsing & Extraction

Separate APIs for Parsing & Extraction

In our original launch of , the field extraction function was part of the parsing function; every time you wanted to run extraction, you had to run parsing, even if you had already parsed the document.

We are now introducing a Preview of two new endpoints that separate these functions: and . These APIs allow you to decouple parsing and extraction workflows for greater flexibility.

You can now parse the document once with the API, and then use the API to run field extraction on that output multiple times. This is helpful if you want to experiment with different extraction schemas or you have multiple extraction tasks.

To get detailed information about how to use these new APIs, go to Separate APIs: Parse & Extract.

​

August 20, 2025: Launch - Subscriptions & New Features

Monthly Subscriptions

We’re excited to announce a major update to Agentic Document Extraction! We’ve just launched credit-based monthly subscription plans designed to deliver more value and features to your team.

Learn more about available plans in Pricing.

All users start on our pay-as-you-go plan that comes with free credits to help you get started! Once you’re ready for production, upgrade to a monthly subscription plan to get access to these new features:

• More credits per dollar
• One-click Zero Data Retention (ZDR)
• Organization management
• Role-based access control (RBAC)
• API key management

One-Click Zero Data Retention (ZDR)

Users on the Team, Visionary, and Enterprise plans can turn on zero data retention (ZDR) directly in the user interface! This ensures that your documents are processed in-memory and are never stored at rest on LandingAI systems or by our sub-processors.

To learn more, go to Zero Data Retention (ZDR) Option Overview.

Organization Management

Upgrading to a Team, Visionary, or Enterprise plan automatically creates an organization. An organization contains all of the credits, members, API keys, and settings for the plan.

To learn more, go to Organizations & Members.

Member Management: Role-Based Access Control (RBAC)

Users on the Team, Visionary, and Enterprise plans can invite multiple users to their organization. These plans offer granular member controls, including the ability to:

• invite members
• assign roles to members that determine what functions they can perform
• change member roles
• revoke invitations
• remove members

To learn more, go to Organizations & Members.

API Key Management

Users on the Team, Visionary, and Enterprise plans can create multiple API keys for their organization. These plans offer granular API key controls, including the ability to:

• create API keys
• revoke API keys

To learn more, go to API Key.

​

July 17, 2025: European Union Availability

Agentic Document Extraction Now Available in Europe

Agentic Document Extraction is now available in Europe. To learn more, go to European Union (EU).

Agentic Document Extraction in the EU provides:

• Data residency: All data is stored and processed within the EU
• GDPR compliance: Coming soon; learn more at our Security and Data page
• Regional performance: Reduced latency for European users

​

May 14, 2025

Improved Accuracy

now delivers higher accuracy when extracting data from complex tables and multi-column layouts.

Increased Processing Speed

is now significantly faster than before, so you can process thousands of pages per minute.

Process Longer Pages

We’ve increased our page limits, so that you can process longer documents.

For more information, go to Rate Limits.

Zero Data Retention

Users on the Custom plan can enable a zero data retention policy, ensuring all data is deleted immediately after processing—supporting strict privacy and compliance requirements.

For more information, contact us.

Consolidated Chunk Types

We consolidated these chunk types into page_header:

• page_header
• page_footer
• page_number

We consolidated these chunk types into form:

• form
• key_value

For more information, go to Chunk Types.