Changelog
Product releases affecting the API, the pipeline engine and the review surfaces. Breaking changes are announced at least 90 days ahead and never ship in a minor release.
Parse, Split, Classify and Extract documented in depth
New reference pages break each Parse-side stage down to its sub-stages — the Parse phase (layout, language, OCR), Split, Classify, and Extract — with the confidence and routing behaviour each one carries.
Accounts and billing docs
Added guides for the three account surfaces: generating a scoped API key, how credits are metered (reserve, settle, release) and how to top up, and bringing your own LLM key so inference runs on your provider account.
Embeddable review canvas
The exception workstream can now be embedded chromeless in your own application. Configure allowed origins and a scoped embed token in Admin → Embeds.
Stage errors split from exceptions
Hard stage failures now surface on their own view in Jobs rather than mixing into review queues. job.failed carries failed_stage; a document that merely needs a human is unaffected.
Documents API
GET /v1/documents ships with lifecycle attributes, lineage and a per-document event ledger. Previously only reachable through the parent job.
Per-operator coverage rows
Verification coverage moved from a percentage on the rule to a flat list of rows on the person. A correction's coverage is the highest percentage among matching rows.
Field-value rule conditions
Coverage rules can now key off an extracted field value — total ≥ 50000, class = credit_memo — in addition to operator and exception attributes.
Removed from the rules API. Reads return null; writes are rejected. Migrate to per-person coverage rows before 1 October 2026.
Pages replace credits in billing
Usage is metered and displayed in pages and dollars. Credit balances were converted at the published rate; the credits field on the usage endpoint is retained as a read-only alias until 2027.
Taxonomy creation from a folder upload
Upload a folder tree and IDPForge derives classes, codes and sample documents from it — folders become classes, contents become few-shot examples.
Pipeline versions are immutable
Editing a published pipeline now creates draft edits; publishing mints the next version. In-flight jobs finish on the version they started with, and every job records its version.
Idempotency keys on job submission
Idempotency-Key is honoured on POST /v1/jobs for 24 hours.