Answer policy questions from a service desk
Load approved leave, travel and expense policy; return an answer with the source page cited.
Use Cases › API Integration
A chat window is one way to use ZenithAI. The other is to call it from code — from inside the ERP, the trading platform, the inbox or the onboarding flow your teams already run — so reading, drafting and reasoning happen at the exact moment the work does. Below are four applications already built this way, the API routes behind them, and the pattern for building your own.
The integration pattern
The same shape repeats across every integration below: your application sends a specific, authorised task; ZenithAI reads, drafts or extracts on infrastructure you control; your application validates the result and carries the workflow to completion. AI never has the last word.
Four applications, one API
These are documented integrations, not hypotheticals — four products already calling ZenithAI in production to move paperwork, email and onboarding forward, with a person reviewing the result before it becomes a record.
A compliance team handles deadline reminders, consent notices, signed agreements and bank statements every day. ZenithAI is embedded at seven points in e-Filix — drafting communications and reading documents inside the workflow an administrator already uses, instead of a separate tool.
A broker note, a payment advice and a Bill of Lading describe the same transaction three different ways. Data Ingenious’s commodity trading platform uses ZenithAI to read free-form trade documents and return structured fields to the purchase or sale screen, where the trader checks the draft before saving.
IntelliMail turns an ambiguous inbox into a decision-ready view: category, urgency with a reason, extracted facts, a one-line summary and an editable reply. Clear-cut messages take a fast rules path; only unresolved messages go to ZenithAI — so the model is used where judgment is actually needed.
Godil applies ZenithAI to identity and address document reading during customer onboarding. The model reads printed fields from an uploaded image or PDF — without being told the values it’s being checked against — and application rules compare the reading to the customer’s submission before routing to auto-verification, rejection or a reviewer’s queue.
Match the task to the route
The same API that powers the ZenithAI chat interface is what these four applications call directly. Full reference and a live sandbox are on the API playground.
| Capability | Route | Typical use | Integration note |
|---|---|---|---|
| Drafting & structured image reading | POST /generate | Templates, extracted fields from a photo or screenshot, vision-assisted reading. | Choose a compatible deployed model; validate returned fields against your schema. |
| Attachment-based conversation | POST /chat | Document summaries, questions over a PDF, audio-to-text. | Confirm supported file types and size limits on your deployment. |
| Text-layer PDF extraction | POST /pdf | Read text and tables from native (non-scanned) PDFs. | Detect scans up front and route them to OCR instead. |
| Scanned PDF & image OCR | POST /ocr GET /ocr/jobs/<id> | Background reading for scans and image-only documents. | Poll for completion; handle failure, timeout and manual fallback. |
Every request authenticates with an X-API-Key header, issued and scoped per workspace. Model availability and exact fields depend on your deployed version — this table is a capability map, not a full specification.
Building your own integration
The four applications above didn’t get resilience by accident. The same five choices show up in each of them.
X-API-Key server-side, apply your own user permissions, and send only the data a task is authorised to use.Beyond these four
These follow the same integration pattern and published API surface, applied to a use case we haven’t yet built and measured together — each one needs workflow design and validation on your material before go-live.
Load approved leave, travel and expense policy; return an answer with the source page cited.
Specifications, scope and approved commercial inputs in; a proposal draft out, ready for review before release.
Computed totals and comparisons with a narrative explanation — reconciled back to the source register.
A change brief referencing the relevant passages, for a specialist to interpret and approve.
A cited answer and draft reply from your own product and support documents, integrated with ticket permissions.
A transcript-based draft of decisions and action items, with names, owners and dates confirmed afterward.
See the complete set, filterable by function, on the use-case library.
Bring your own application
Bring the workflow, the document types and a handful of real examples. We’ll walk through which routes apply, what stays in your application logic, and what a first pilot would measure.