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.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
Extract
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
Filter
Split
The 0.5-credit tier kicks in only when the node has to read text content to make its decision (keyword matching, or auto boundary detection). Rules that test only on page numbers stay free.
Validation
Other actions
Outputs
Output nodes deliver results. All outputs are free.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:
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:
For a non-invoice (matches the
other branch):
The
other branch never executes extract, so non-invoices cost a fraction of the matched ones.
Ingestly 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.
Credit allocation
Credits are allocated monthly with your subscription plan. New organizations start with 150 welcome credits so you can build and test a pipeline before subscribing. See subscription for plan details and credit balances.Per-pipeline usage
Each pipeline page shows a daily credits chart for the last 7 days, so you can spot which pipelines 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.Related
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