Pricing

DWS Processor API enables you to programmatically generate, convert, edit, and optimize documents in the cloud. It supports a wide range of formats and workflows, including PDF generation, OCR, and redaction.

Usage is typically measured based on document operations, such as pages processed, files converted, or API calls made. The exact unit depends on the type of operation being performed.

Processor API supports a wide range of formats, including PDF, Office documents (Word, Excel, PowerPoint), images, and HTML, depending on the operation.

Yes. The API is designed for automation, enabling you to build workflows for document generation, conversion, extraction, redaction, and processing at scale.

Yes. Processor API includes AI-powered capabilities such as data extraction, document understanding, and intelligent processing for complex document workflows.

An operation typically represents a unit of work, such as processing a document or page. The exact definition depends on the feature used (e.g. conversion, OCR, redaction). Your usage is calculated based on these operations.

With pay-as-you-go, running out of credits doesn’t stop your production. We pre-authorize charges in $25 increments and add credits as you use them, up to a spending cap you control (by default, half your monthly subscription value) — we never charge beyond it. Set the cap to $0 to stop at your monthly limit with no extra charges. Pay-as-you-go is available on paid subscriptions only.

Yes. The Processor API is built with enterprise-grade security and processes documents in a secure cloud environment. It supports compliance requirements such as GDPR, HIPAA, and SOC 2 Type 2 audited controls.

All plans include access to documentation and developer support. Additional support options may be available depending on your plan.

The Data Extraction API parses PDFs, scans, images, and Office files into structured output, including spatial JSON and Markdown, or extracts specific fields to a schema with confidence scores and source coordinates.

Credits are the unit of consumption for the Data Extraction API. Parse requests cost 1 credit per page in text mode, 1.5 credits per page in structure mode, 9 credits per page in understand mode, and 18 credits per page in agentic mode. Extract requests add 6 credits per page to the selected Parse mode, for totals of 7, 7.5, 15, or 24 credits per page. Unused credits do not roll over to the next month.

understand mode is the recommended default — it handles all document types with structured extraction and semantic enrichment. For Parse, estimate monthly usage as 1 credit per page in text mode, 1.5 credits per page in structure mode, 9 credits per page in understand mode, or 18 credits per page in agentic mode. For Extract, add 6 credits per page to the selected mode.

Monthly billing charges month-to-month with no commitment. Annual billing is paid upfront for 12 months at a discounted rate.

With pay-as-you-go, processing doesn’t stop when your monthly credits run out. We pre-authorize charges in $25 increments and add credits as you use them, up to a spending cap you control (by default, half your monthly subscription value) — we never charge beyond it. Set the cap to $0 to turn pay-as-you-go off and stop at your monthly limit. You can also upgrade to a higher plan or contact sales for a custom quota.

Yes. The Free plan gives you 5,000 credits/month with no credit card required — enough for 5,000 text Parse pages, about 3,333 structure Parse pages, or about 555 understand Parse pages. For Extract, the same 5,000 credits cover about 714 text + Extract pages, 666 structure + Extract pages, 333 understand + Extract pages, or 208 agentic + Extract pages.

Yes. Upgrades take effect immediately. Downgrades take effect at the start of your next billing cycle.

Yes. The Data Extraction API is built with enterprise-grade security and processes documents in a secure cloud environment. It supports compliance requirements such as GDPR, HIPAA, and SOC 2 Type 2 audited controls.

All plans include access to documentation and developer support. Additional support options may be available depending on your plan.

The DWS Accessibility API enables you to automatically tag PDFs and validate accessibility compliance. It helps you generate accessible documents that support screen readers and meet standards like PDF/UA.

Usage is typically based on documents or pages processed for auto-tagging and validation. The exact unit depends on how the API is used.

The API is designed to support accessibility standards such as PDF/UA and align with guidelines like WCAG and Section 508.

Auto-tagging adds a structured layer to a PDF, defining elements like headings, paragraphs, tables, and images. This structure allows assistive technologies, such as screen readers, to interpret and navigate the document.

Yes. You can run validation checks independently to identify accessibility issues without applying changes to the original document.

Yes. The API automates both tagging and validation, allowing you to integrate accessibility into your document workflows without manual remediation.

Yes. The API is designed for automation and can be integrated into document generation or processing pipelines to ensure accessibility before documents are distributed.

With pay-as-you-go, reaching your quota doesn’t stop your remediation pipeline. We pre-authorize charges in $25 increments and add pages above your quota as you process them, up to a spending cap you control (by default, half your monthly subscription value) — we never charge beyond it. Set the cap to $0 to stop at your monthly quota. Pay-as-you-go is available on paid subscriptions only.

Yes. The Accessibility API is built with enterprise-grade security and processes documents in a secure cloud environment. It supports compliance requirements such as GDPR, HIPAA, and SOC 2 Type 2 audited controls.

All plans include access to documentation and developer support. Additional support options may be available depending on your plan.

DWS Viewer API enables you to embed a fully featured document viewer into your application. It supports viewing, annotation, form filling, and signing directly in the browser.

Usage is typically measured by viewer sessions — each time a document is loaded and interacted with in your application.

A viewer session represents a single instance of a document being opened in the viewer. This includes rendering the document and enabling user interactions like scrolling, annotating, or signing.

No. Viewer API can be used without managing backend infrastructure. It’s designed to render documents directly in the browser using cloud-based services.

Yes. Viewer API is highly customizable. You can control the UI, enable or disable features, and integrate it with your application’s workflows.

Yes. You can enable features such as annotations, comments, form filling, and electronic signatures directly within the viewer.

With pay-as-you-go, exceeding your monthly viewer sessions doesn’t interrupt your app. We pre-authorize charges in $25 increments and add sessions as you use them, up to a spending cap you control (by default, half your monthly subscription value) — we never charge beyond it. Set the cap to $0 to stop at your monthly limit. Pay-as-you-go is available on paid subscriptions only.

Yes. The Viewer API is built with enterprise-grade security and processes documents in a secure cloud environment. It supports compliance requirements such as GDPR, HIPAA, and SOC 2 Type 2 audited controls.

All plans include access to documentation and developer support. Additional support options may be available depending on your plan.