Work
Our extensive catalog of public data gives us something to work with from the start. Each project also leaves behind useful pieces we can reuse. That is why the next hard question usually moves faster.
Contracts. Regulatory filings. Investment books. Bond ownership. Vendor spend. Different questions, same goal: get to an answer you can check and use.
Current work
Running means there is a working system. Building means we are still putting it together.
01 / Running
2026-08-13
Procurement
documents → narrow extraction → deterministic score → quoted evidence → portfolio re-score
A working contract-risk system separates reading from judgment. Change a policy lever and the portfolio re-scores without another model call.
02 / Building
2026-08-12
Banking / community development
five public data families → entity resolution → evaluation corpus → peer evidence → geography-level signal
The source universe is mapped. The hard part is joining incompatible identifiers, historical geography, lending data, and regulator narratives without losing the as-of date.
03 / Running
2026-08
Insurance / structured finance
statutory filings → layout fingerprint → deterministic parse → reconciliation gates → security and property holdings
The parser accepts a value only when the filing evidence and reconciliation checks support it. Partial and refused parses remain visible instead of being guessed through.
04 / Building
2026-07
Structured credit
fund filings + daily holdings + statutory sources → identity graph → holder observations → change signal
The visible holder base is scattered across incompatible sources. The work is to reconstruct the observable slice and make coverage explicit.
How we work
Find the right sources, make sense of them, show what supports the answer, and turn it into something the team can use again.
For the practitioner
Under the hood
Every problem should leave the practice more capable than it found it.
Past questions
Some became running systems. Some became reusable pieces. Some simply showed us where the public record stops.
Public corpus · 107+ providers · 169+ channels · 811+ tables
Public data often gets us most of the way. Add your contracts, positions, invoices, policies, or internal records and the answer becomes specific to you.
Source check
Loom is our question-answering service, built on public data. Each response shows the source, what changed, and the date the data was true. Ask for evidence and you can open the full source trail.
Public fixed-income data
A working structured-finance intelligence service built from public filings. Search deals, funds, and BDCs, then inspect the source trail behind each result.
Public SEC filings and remittance reports
Deals, funds, BDCs, and downloadable datasets
Procurement signal
We built this signal from public data in days. It combines energy prices, producer prices, and industry use to show when an increase may hold. A team's contract data makes it more precise.
Henry Hub, BLS PPI, and WTI, all public
213 scored events, 56.8% directional match
Contract risk
Executed statements of work, pulled from public SEC exhibits and scored against one policy: pass, review, or fail. Move a threshold and the whole book re-scores instantly. Every verdict carries a receipt back to the filing it came from.
Deterministic verdict
review · 0.55
quote evidence
source unchanged
policy re-score without another model call
Holder map
One class of a live auto ABS deal, traced through public filings. Two funds are named, together about 0.6% of the class. Sponsor risk retention accounts for roughly 5% more. No public filing names a holder for the rest — yet. Every source added closes the gap.
SEC 424B5, 10-D, N-PORT, and Reg RR
One class traced, sources still being added
SEC filing tools
A bounded SEC EDGAR tool surface that lets MCP-compatible agents query filing metadata inside governed workflows.
SEC EDGAR filing metadata
MCP-compatible clients
Public MCP server
Paste in commentary, an article, or text from Claude. The server checks the CMBS claims it supports, links to the SEC filings, and shows what it could not check.
Public verification surface
https://receipts.cmdrvl.com/mcpclaude mcp add --transport http receipts https://receipts.cmdrvl.com/mcpcodex mcp add receipts --url https://receipts.cmdrvl.com/mcpConnect, call quickstart, then send the text to verify_claims. Call coverage before reading an UNVERIFIED result.
Point-in-time benchmark
KnownBy is a point-in-time benchmark for financial systems. It tests whether a system can return the value, citation, and data date that were publicly available then, or correctly decline when the fact was not knowable. Arithmetic and schema validation score each response, and every answer key carries a recipe for rebuilding it from an official archive.
Point-in-time check
What was knowable on that date?
decline: post-cessation
96-task demo fixture
We will identify the sources, the evidence boundary, and the smallest working result worth building first.