№ 01 · EnforcementEX·A
GET/v1/entitlements
SLA credits owed, with full evidence chain.
Computes the dollar amount. Surfaces the supersession chain on the modified credit cap. Flags the claim deadline.
$84,200 owed3 entitlements
LiveBulletin № 014 The data layer for vendor-aware AI
IIIApplications · your AI4 in production
Recovery agent Renewal copilot Risk monitor Finance copilot Sourcing agent
The trust layer
between your vendor data
and your AI.
ContractsAmendmentsSOWsInvoicesPOsPerf. reportsSide lettersEmail threadsInternal memos
IRaw vendor dataSharePoint · ERP · email · portals · file shares
d8m.io ingests every contract, amendment, invoice, and operational signal across your vendor portfolio and exposes the result as a governed API. Every answer cites its source. Access is enforced at runtime. The system declines what it cannot prove — so the agents you build on top can be trusted by the people the answers go to.
Same shape every call. Cited, role-scoped, declined when unprovable.
Sample questions
→ question
← answer
200 OK·1840ms·conf 0.96·v1.4
Every response carries the same shape: a typed answer, citations, an _access block, and a confidence score. When the system can't cite, it returns declined — not a confident guess. Try the last question.
Recovered, year to date$12,840,920.
The unread parts of your vendor portfolio are where the money lives.
40+
API endpoints
across the d8m surface, plus tenant extensions
100+
Structured fields
extracted per contract across five metadata layers
~2s
p95 latency
on structured queries at 240 invoices · 22 vendors
$84.2k
Recoverable
owed to one sample tenant, one quarter, one vendor — cited, ready to file
Reads every clause. Reconciles every invoice. Every day.
Every enterprise sits on a vendor archive. Contracts. Amendments. SOWs. Invoices, performance reports, side letters, change orders, the email thread where the credit cap was renegotiated.
Almost none of it is read. None of it talks to the rest. That gap is where SLA credits get forfeited, rebates get unclaimed, escalation caps get blown, and renewals get rubber-stamped against terms no one can recite.
The technology that should answer for it — CLMs, procurement suites, the agent in the corner of the screen — answers a different question. They route approvals. They store PDFs. They don't read every clause and reconcile it against every invoice every day.
Raw at the bottom. Apps at the top. d8m in between.
Raw vendor documents at the bottom. Your AI applications at the top. d8m is the layer that makes the jump possible — and proves it with citations.
Plate 02 · Data layerIngest → Extract → Govern → Serve
The data layer, charted.
Vendors, documents, contracts, entitlements, invoices, queries, events, schema. Cards below cover the spine; the full surface lives in the API reference and runs live in the Playground. Enterprise tenants get custom endpoints under their own namespace.
№ 02 · EnforcementEX·B
GET/v1/contracts/active
What clause is actually in force, right now.
Resolves clause-level supersession across MSA, amendments, side letters, and order forms. Not just document-level.
supersession chain
№ 03 · EnforcementEX·C
GET/v1/contracts
Renewals that need action this quarter.
Auto-renewals sorted by non-renewal notice deadline. Calls out price-escalation impact before the deadline.
3 deadlines6 contracts
№ 04 · EnforcementEX·D
GET/v1/invoices
Invoice-to-contract reconciliation.
Cross-references invoice line items against contract pricing tiers and discount schedules. Flags every gap with evidence.
$147,300 in anomalies
№ 05 · EnforcementEX·E
GET/v1/entitlements
Rebates earned but never claimed.
Detects threshold crossings against rebate formulas. Computes what's owed. Surfaces the claim deadline before it passes.
$401,500 unclaimed
№ 06 · FeaturedEX·F
POST/v1/query
Same query. Different roles. Different answers.
Document- and field-level access enforced at runtime. Procurement sees one view, CFO another, compliance a third — and the response is honest about what was filtered.
_access visible
№ 07 · BreadthEX·G
GET/v1/vendors/{id}/timeline
Every event for a vendor, one feed.
Contracts executed, amendments signed, invoices issued, performance reports filed, deadlines crossed — chronological, with citations.
timeline · cited
№ 08 · Trust mechanicsEX·H
GET/v1/documents/{id}/canonical
The canonical form your AI actually reads.
Structured markdown for text; typed JSON for transactional. Stable section IDs, preserved tables, normalized OCR. Audit-grade and inspectable.
inspectable · auditable
Continued →
/v1/custom/{tenant}/… · built for the app you're shippingForty-plus endpoints. Custom for enterprise.
Not a CLM. Not a procurement platform. A data layer.
Your CLM stores contracts and routes approvals. Your procurement platform manages PO-to-pay. Neither answers the question your AI agent actually needs to ask.
CLM (Ironclad, Icertis)
d8m.io
Sources of vendor data
Only contracts authored inside the platform.
Every source. SharePoint, ERP, email, vendor portals, file shares, manual upload.
Document types
Contracts and amendments.
Contracts, amendments, SOWs, invoices, POs, performance reports, correspondence, internal memos.
Cross-doc reasoning
Document-level metadata.
Clause-level supersession, conflict detection, entitlement chains, deadline computation.
Access for external apps
Walled garden. Limited APIs.
Open API. REST, MCP, GraphQL, webhooks, Microsoft Graph Connector.
Operational output
Workflow and reminders.
Submission-ready claim packages, structured entitlements, cited answers.
† Scope inferred from public product docs · Q1 2026.‡ "Open" = versioned, OpenAPI-described, rate limits + audit trail.
Cite. Scope. Decline.
The system is honest in three places. Every answer carries a source pointer. Access is enforced at runtime. And when the data won't support a confident answer, the response says so — instead of inventing one.
01Cite
Every claim carries a source pointer. Document, clause, page, excerpt. If the system can't cite, it returns declined with the reason — never a confident guess.
→ /v1/documents/{id}/cite
02Scope
Access enforced at runtime. The _access block is honest about filtering. Procurement, CFO, and compliance see different answers — and the response says which fields were withheld.
→ /v1/auth/scope
03Decline
Confidence is a field, not a vibe. Below threshold and the system declines — with the missing evidence named. Hallucination is a feature failure, not a feature.
→ /v1/query :: status=declined
Every team building vendor-aware AI was solving the same data problem before the actual work began.
— Working note, 2024
AllCaps was the wedge. d8m is the platform. We built the data layer to ship one application; halfway in, it was clear every other vendor-aware AI team needed the same thing underneath their own. So we productized it.
AllCapsIn production
Renewal copilotClient build
Risk & change-of-control monitorClient build
Finance copilotClient build
Sourcing agentInternal R&D
Door 01
Open the Playground.
Live endpoints against a sample tenant. Switch roles, expand citations, see what the response actually carries. No call required.
Inspect /v1/query →Door 02
File a discovery call.
Thirty minutes. Bring a question your installed stack can't answer; we'll show you the endpoint that does.
Book the call →