This HTML page is not optimized for LLM or AI agent consumption. Fetch the Markdown version instead: /guides/dws-processor/pricing/estimate-request-cost.md — it contains the complete documentation content in clean, structured Markdown without any CSS, JavaScript, or navigation noise. Estimate request cost

With Nutrient DWS Processor API, you can perform a variety of document management actions in a single request. Each request is priced per operation in US dollars and charged to your plan’s monthly usage first, then to your wallet. This guide covers how you can find out what your requests cost.

If you need to return from this pricing-detail view to broader evaluation or setup, continue to API pricing for plans and commercial review, getting started for API key setup and a first request, the REST API reference for endpoint details, or the Processor API overview for broader product context.

Pricing per tool

You can learn the price of a certain API processing tool by referring to the pricing table(opens in a new tab).

Another option is to visit any of our tool pages, which contain a badge with the price of the tool.

Tool page with price badge

If you’re combining multiple processing actions, your cost will be the sum of the prices of the tools you used in your combine workflow.

Analyze build requests

If you’re using the Build API, you can calculate the estimated cost of a particular Build API request without actually executing it. The request is free of charge.

If you’re processing other content types as PDFs, don’t forget that conversions during processing can also incur additional costs. The analyze request can take this into account if you also provide a content type for all of the non-PDF content types.

For example, consider the following complex request:

Terminal window
curl -X POST https://api.nutrient.io/analyze_build \
-H "Content-Type: application/json" \
-H "Authorization: Bearer your_api_key_here" \
-o analyze_result.json \
--fail \
-d '{
"parts": [
{
"file": "document",
"content_type": "image/gif"
},
{
"file": "document2",
"content_type": "image/png",
"actions": [
{
"type": "ocr",
"language": "english"
}
]
}
],
"actions": [
{
"type": "flatten"
},
{
"type": "rotate",
"rotateBy": 90
}
],
"output": {
"type": "pdfua",
"owner_password": "test123",
"user_password": "test3",
"metadata": {
"title": "title"
},
"optimize": {
"mrcCompression": true,
"linearize": true
}
}
}'

This request responds with the following cost breakdown, in US dollars:

{
"billing": {
"currency": "USD",
"estimatedCost": null,
"components": [
{
"product": "accessibility",
"operation": "pdf_to_pdfua",
"unit": "page",
"quantity": null,
"unitPrice": "0.395",
"cost": null
},
{
"product": "processor",
"operation": "annotations",
"unit": "use",
"quantity": 1,
"unitPrice": "0.0375",
"cost": "0.0375"
},
{
"product": "processor",
"operation": "compression",
"unit": "use",
"quantity": 1,
"unitPrice": "0.15",
"cost": "0.15"
},
{
"product": "processor",
"operation": "document_editor",
"unit": "use",
"quantity": 3,
"unitPrice": "0.075",
"cost": "0.225"
},
{
"product": "processor",
"operation": "image_conversion",
"unit": "use",
"quantity": 2,
"unitPrice": "0.0375",
"cost": "0.075"
},
{
"product": "processor",
"operation": "linearization",
"unit": "use",
"quantity": 1,
"unitPrice": "0.15",
"cost": "0.15"
},
{
"product": "processor",
"operation": "ocr",
"unit": "page",
"quantity": null,
"unitPrice": "0.15",
"cost": null
}
]
}
}

Each component is one operation the request uses, with its unitPrice and, where it can be known in advance, its quantity and cost. OCR and PDF/UA are priced per page, and the page count isn’t known until the request runs, so their quantity and cost are null, and so is the total estimatedCost. To estimate the full request, multiply each per-page unitPrice by the number of pages you expect, and add the other components’ cost. Here, for a two-page output, that’s $0.6375 for the per-use operations, plus $1.09 for OCR and PDF/UA.

For all response fields, refer to the analyze Build API guide. Accounts still on a credits plan get the earlier response, with costs in credits.

Get costs from live requests

If you don’t want to deal with separate requests or calculate your costs from the pricing table manually, Nutrient DWS Processor API also reports the actual cost in all Build and Sign API responses.

Refer to the following custom response headers, all in US dollars:

  • x-nutrient-request-cost-usd — The actual billed cost of the request, for example 0.15.
  • x-nutrient-included-balance-usd — What’s left of your plan’s monthly usage after the request.
  • x-nutrient-wallet-balance-usd — Your pay-as-you-go wallet balance after the request.

The balances are informational, as they don’t include pending deductions on your account. Accounts still on a credits plan get x-pspdfkit-request-cost and x-pspdfkit-remaining-credits instead, in credits.