Understand how credits are consumed by each node type in your pipelines.
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 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.
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.
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.
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.
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.
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.
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.
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.
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.