Without NDI
Acme Industries may have misrepresented inventory. Several documents discuss inventory condition, but the specific claim could not be verified.
No source returned

Perception and context in a single API. Parse complex files with pixel-level evidence, build persistent workspaces, and let AI agents search your entire corpus.
PDF, image, spreadsheet, presentation, email, or text.
Turn the file into layout-aware Markdown while preserving tables, reading order, and page structure.
Files are temporary and automatically expire.
[ capabilities ]
Reading order
Layout-aware markdown that keeps columns, headers, and reading order intact.
Tables stay tables
Tables can come back as table HTML. Spreadsheets are read cell by cell, not OCR'd.
Located blocks
Blocks carry real page and box locations when you ask for them.
Optional chunking
None, page, or section. Chunks are an optional output, never the unit of truth.
Parse selected. POST /v1/parse
Create a job, wait or poll, retry with an idempotency key.
parse formats
Scans, packets, email, spreadsheets, slides, audio, video.
.pdf.doc.docx.docm.ppt.pptx.txt.log.htm.html.xls.xlsx.xlsm.csv.xml.eml.msg.png.jpg.jpeg.tif.tiff.webp.vsd.vsdx.flac.m4a.mp3.mpga.oga.ogg.wav.avi.mkv.mov.mp4Every number on this page cites a public dataset or our own runnable eval.
Tables
rd-tablebench · teds score
92.4%
NDI
Layout & Parsing
omnidocbench · structure accuracy
94.8%
NDI
Grounding & Evidence
realdoc-bench · bounding-box precision
98.1%
NDI
Multimodal
ndi crossmedia bench · docs, audio & video
91.6%
NDI
Enterprises hold terabytes of documents no model can read reliably. RAG pilots demo well and fail on real files — scans, packets, ledgers, calls. When the answer cannot be traced to a page, a cell, or a timestamp, nobody in a regulated function can use it.
“Was Acme Industries inventory misrepresented?”
Acme Industries may have misrepresented inventory. Several documents discuss inventory condition, but the specific claim could not be verified.
No source returned
Yes. CEO Harold Gillis knew the inventory was defective before the signing date, and shipments continued for six weeks after.
3 sources cited
Two layers on one path. Perception makes a file legible; Context makes the corpus answerable. One /v1 API covers both.
You do not have to adopt the whole path. Bring raw files and stop at located data, or bring data you already parsed and go straight to grounded answers.
Turn any file into structured, grounded data. Files enter from upload, URL, or workspace, and parse runs per type — documents, sheets, media. Every block, field, and cell keeps a locator. Nothing is stored as “the model said so.”
Parse · Ground · Classify · Split · Extract
Turn that data into a corpus your team can question. Hybrid search runs over the corpus: fact search is fixed, deep search is the bounded agent. Synthesis happens only after evidence, citations ride along, and a miss stays a miss.
Workspaces · Upload · Search · Grounded QA
Use either layer on its own. Most teams use both.
Read the /v1 referenceHolds the files. Retrieves the evidence. Returns a claim you can open.
A bounded corpus, not a folder. Roles, access labels, a domain, and a retention policy travel with every file. Upload, connectors, and bulk backfill all land inside the same boundary.
Keyword and semantic, not keyword alone. Fact search returns in seconds. Deep search sends a bounded agent when the question needs one. Withheld hits are reported, never silently dropped.
Every claim opens to its source. Answers come back with locators — page and box, sheet and cells, or timestamp — plus coverage of what was left out. Table answers can return the SQL.
Workspace UI, CLI, API, and MCP. Analysts work without filing a ticket, data engineers backfill from CI, product teams embed /v1, and agent builders connect from Claude, Cursor, or any MCP client.
Microsoft Entra ID SSO, with owner, admin, and member roles. Invites replace shared passwords, access labels are frozen on the workspace, and the audit log keeps job history, key mint and revoke, and who asked what.
Same /v1 API, same X-API-Key. Run managed or inside your own VPC. Keep documents in a managed bucket or bring your own, and let a workspace TTL expire them on policy rather than on request.
Chat is not the public product. Grasp, NAVI, or your own app owns that experience.
Review the deployment shapeMove from a single hard document to the whole matter without losing the page, cell, or timestamp behind the answer.
Question
Was inventory misrepresented?
Grounded answer
Yes. The contract, board call, and inventory register agree that defective stock was known before signing.
No. NDI is a permissioned evidence base. Your product, Grasp, or NAVI owns the chat experience.
No. You can use Perception or Context independently. Most teams use both, and parse does not require a workspace.
The APIs return honest states. Ground locates text without judging it, and Extract can return not_found or ambiguous instead of forcing an answer.
Yes. Cloud and on-prem expose the same /v1 API. A customer VPC is a deployment shape, not a separate product.
Yes. Use REST, SDKs, or hosted and local MCP from Claude, Cursor, and other MCP clients.
Read the MCP docsAccess labels are data, not prompt instructions. Coverage is reported, and restricted graph nodes are not walkable.
NDI parses 36 formats across documents, sheets, email, images, diagrams, audio, and video.
Poll today. Webhooks are not currently part of the public job contract.