Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.docpipe.ai/llms.txt

Use this file to discover all available pages before exploring further.

Each pipeline run consumes credits based on the nodes in your pipeline and the documents processed. This page lists the credit cost for every node type.

​
Triggers

Triggers accept documents into the pipeline. Upload, Email, and Webhook triggers each charge 1 credit per page ingested. The internal Forward trigger remains free.
NodeCost per page
Upload trigger1 credit
Email trigger1 credit
Webhook trigger1 credit
Email triggers create a separate pipeline run per attachment, so a single email with two 2-page attachments charges 2 attachments × 2 pages × 1 credit = 4 trigger credits. A single 5-page upload charges 5 × 1 = 5 trigger credits.

​
Actions

Actions process documents and data within the pipeline.

​
Parse

EngineCost per page
Standard1 credit
Vision2 credits
KeyValuePair1 credit + LLM cost
Chaining parse and extract on the same document runs OCR twice and bills both. Skip the parse node when extract is the next step; extract already handles OCR internally. Only chain them when you need the parsed text for a separate purpose (routing, archiving, multiple schemas off one OCR pass). See parse best practices.

​
Extract

EnginePrecisionCost per page
Engine 1Small1 credit
Engine 1Medium2 credits
Engine 1High3 credits
Engine 2Not applicable2 credits
Engine 2 has no precision setting; it’s a single-tier engine. Enabling Force OCR on Engine 1 adds 1 credit per page on top of the precision cost.

​
Classify

ModeCost per page
Rules0.5 credits
AI0.2 credits

​
Route

ConfigurationCost per page
Keep / Drop with a non-keyword filter0 credits
Group with a fixed page-count grouping0 credits
Keep / Drop with a keyword filter0.5 credits
Group by keyword on first or last page0.5 credits
The 0.5-credit tier kicks in only when the route node has to read text content to make its decision (keyword filters or keyword-based grouping). Filters that test on metadata or page numbers stay free.

​
Validation

ModeCost
Rules0 credits
Schema0 credits
Endpoint0 credits
Script0 credits
AI (Small)LLM pricing: Small tier
AI (Medium)LLM pricing: Medium tier
AI (High)LLM pricing: High tier

​
Other actions

NodeCost
Review0 credits
Transform0 credits
Merge0 credits
HTTP action0 credits
Variable0 credits
Loop0 credits

​
Outputs

Output nodes deliver results. All outputs are free.
NodeCost
Callback0 credits
Email output0 credits

​
Schema inference

Using the Generate button inside an extract node to infer a schema from a sample document also consumes credits. The charge is applied per page processed during generation.

​
Classification generation

Generating classifications on a forward trigger costs 0.2 credits per page for each reference document you select.

​
Worked examples

These examples show how to add up credits for realistic pipelines. Numbers assume single-page documents unless noted; multiply by the page count for longer documents.

​
Minimal extraction pipeline

A typical “submit a document, get structured data back” flow: 
Webhook trigger → Extract (Engine 1, Medium) → Callback
StepCost per page
Webhook trigger1 credit
Extract (Engine 1, Medium)2 credits
Callback0 credits
Total3 credits per page
A 5-page invoice runs in this pipeline for 15 credits.

​
Branching pipeline with classify, review, and validation

A pipeline that classifies documents, extracts on a focused schema, validates the result, and pauses uncertain runs for human review: 
Webhook trigger
  → Classify (AI)
      ├─ Invoices → Extract (Engine 1, Medium) → Validation (Rules) → Review (Unverified Fields) → Callback
      └─ Other     → Callback
For an invoice (matches the first branch):
StepCost per page
Webhook trigger1 credit
Classify (AI)0.2 credits
Extract (Engine 1, Medium)2 credits
Validation (Rules)0 credits
Review (Unverified Fields)0 credits
Callback0 credits
Total3.2 credits per page
For a non-invoice (matches the other branch):
StepCost per page
Webhook trigger1 credit
Classify (AI)0.2 credits
Callback0 credits
Total1.2 credits per page
The other branch never executes extract, so non-invoices cost a fraction of the matched ones.
DocPipe reserves credits upfront at run start based on the most expensive branch your pipeline could take, so the actual deduction matches the worst-case path even if a cheaper branch ends up running. Reference-document embeddings are billed separately when you upload references via a forward trigger, not on each run.
To estimate a monthly bill, multiply the per-page total for each branch by the average pages per document and the volume you expect to see in that branch.

​
Credit allocation

Credits are allocated monthly with your subscription plan. New organizations start with 200 welcome credits so you can build and test a pipeline before subscribing. See subscription for plan details and credit balances.

​
Per-pipe usage

Each pipe page shows a daily credits chart for the last 7 days, so you can spot which pipes are consuming the most credits and which days had spikes. Per-step credit usage is recorded on every run, so the run detail page also breaks down the cost by node.

Subscription

Plan tiers, monthly credit allotments, and balance

Alert rules

Get notified when your credit balance drops below a threshold

Parse best practices

Avoid double-OCR and pick the cheapest engine that works

Extract best practices

Match engine and precision to your documents