Resources
Guide · for product and engineering leads at software companies
A practical architecture for adding evidence-linked document analysis to a software product with an asynchronous API, including a worked example, integration decisions and real limits.
Guide · for legal operations and in house counsel
Build a small, fair evaluation set from your own playbook and agreements before trusting any contract review API, with a worked request, scoring criteria and real limits.
Guide · for procurement teams and buyers
Compare vendor proposals row by row against your requirements, with the quote behind every cell.
Guide · for anyone shipping ai output with citations
Locating a source passage is different from showing that it supports a conclusion. How to tell the difference in your product.
Guide · for product designers and engineers
Design your interface so that a withheld or incomplete result is useful rather than a dead end.
Guide · for evaluation and ml engineers
How to compare a multi-role workflow with a strong single model without stacking the deck.
Guide · for product managers and finance partners
A simple model for estimating what an analysis feature will cost to run, using measured per-run figures.
Guide · for operators and team leads
Turn a review you do every week into an engine configuration with rules, hard cases and examples.
Guide · for ctos and engineering leads
When a model API alone is enough, when an orchestration framework fits, and when a managed workflow is worth it.
Developer guide · for backend developers
Submit a run, track it, handle released, incomplete and failed results, and retry safely.
Developer guide · for backend developers
How Encevra signs webhook deliveries and how to verify them.
Checklist · for teams running a scoped evaluation
A reusable checklist for evaluating any document analysis API on your own representative tasks.
Sample inputs for every engine are on each engine page, labelled as authored illustrations, and collected together in the sample pack.
