Pricing

The Nutrient DWS Data Extraction API charges credits per page processed. The cost depends on the endpoint and processing mode.

Parse endpoint

The parse endpoint charges per page based on the processing mode. For request details, refer to the parse endpoint guide.

For example, processing a 10-page PDF in structure mode costs 15 credits. The same document costs 10 credits in text mode and 90 credits in understand mode.

Extract endpoint

The extract endpoint bills two components per page. For request details, refer to the extract endpoint guide.

• Parse component — Charged at the rate of the parseConfig.mode used.
• Extract component — Charged at a fixed rate.

The total per-page cost is the sum of both components.

The response breaks the total down in usage.price_composition so you can review how the request was billed:

{
  "usage": {
    "data_extraction_credits": { "cost": 27, "remainingCredits": 832 },
    "price_composition": {
      "parse": { "units": 1, "unit_cost": 9, "cost": 9, "currency": "data_extraction_credits" },
      "extract": { "units": 1, "unit_cost": 18, "cost": 18, "currency": "data_extraction_credits" }
    }
  }
}

In this example, one page processed with parseConfig.mode: "understand" costs 27 credits: 9 credits for parsing, plus 18 credits for extraction.

FAQs

These questions cover credits, modes, rate limits, and insufficient credit responses.

How do credits work?

Each API request consumes credits based on the number of pages processed and the mode used. The response includes a usage field that shows the credits consumed and the remaining balance:

{
  "usage": {
    "data_extraction_credits": {
      "cost": 9,
      "remainingCredits": 850
    }
  }
}

Which mode should I choose?

Choose the mode based on the output your application needs:

• Use text mode for Markdown pipelines where you only need text content.
• Use structure mode when you need spatial element data, such as bounding boxes, table cells, or key-value pairs, at moderate cost.
• Use understand mode for complex documents with tables, forms, and multicolumn layouts, or when you need the highest extraction accuracy.
• Use agentic mode for the most complex documents that benefit from VLM-augmented visual understanding.

For a detailed comparison, refer to the processing modes guide.

How is the extract endpoint priced?

The extract endpoint bills a parse component at the parseConfig.mode rate, plus a fixed extract component per page. A page processed with understand parsing costs 27 credits: 9 credits for parsing plus 18 credits for extraction.

Use the usage.price_composition field in the response to review the parse and extract components for any request. For endpoint details, refer to the extract endpoint guide.

How do I check my remaining credits?

Every API response includes a usage field with your remaining credit balance. You can also check your balance in the Data Extraction API dashboard(opens in a new tab).

What happens when I run out of credits?

Requests return a 402 status code with a message that indicates insufficient credits. Purchase additional credits through the dashboard.

Is there a rate limit?

Yes. Rate limits depend on your subscription plan. Requests that exceed the limit receive a 429 status code. Contact the Sales team for higher rate limits.