Verification infrastructure
for financial claims
Audex is a neurosymbolic verification engine for SEC filings. It extracts financial claims using an LLM, then routes every output through a deterministic verification stack — mathematical consistency checks, XBRL taxonomy validation, multi-pass consensus scoring, and Z3 constraint solving — before emitting a verified assertion with a full audit trail.
The product is not a dashboard or a score. It is a verified assertion with a traceable reject reason — something defensible enough to act on.
Filing: 0000320193-25-000079 | Period: CY2025
Running 6-layer verification pipeline...
The 6-layer verification stack
A claim that fails any layer is rejected with a specific, machine-readable reason code. No layer trusts the layer above it. LLMs live only in Layer 1 — everything else is deterministic.
Structured Extraction
Anthropic Claude + Pydantic v23x multi-pass extraction at temperature=0. Every LLM output parsed into a typed Pydantic model. If it can't be parsed, it's a reject. Consensus scoring across passes.
Mathematical Consistency
Pure PythonBalance sheet equation holds. Segment revenues sum to consolidated total. Income statement flows consistently. No LLM involvement — deterministic arithmetic only.
XBRL Ground Truth
SEC EDGAR XBRL APIEvery extracted value cross-referenced against the company's own XBRL-tagged data. XBRL is treated as canonical. Discrepancies produce a reject with the exact delta.
Multi-Pass Consensus
Divergence scoringField-level agreement across all extraction runs. Claims where any numeric value disagrees across passes are flagged with the specific divergence.
Domain Rules Engine
Extensible Python rulesGrowing library of GAAP-specific verification rules. Revenue recognition consistency, segment completeness, asset positivity. Rules are append-only and versioned.
SMT Constraint Verification
Z3 theorem proverFormal mathematical proof that the set of extracted claims is internally consistent. Z3 returns an unsat core when constraints conflict — identifying exactly which claims are in tension.
What the output looks like
Every claim produces a VerifiedAssertion or RejectedClaim — never a probability without context. Each includes the full audit trail: every layer result, the raw LLM responses from all 3 extraction passes, the XBRL ground truth values used for comparison, which rules triggered, and a confidence score with a traceable decomposition.
This audit trail is the product. It's what separates a probabilistic signal from a defensible claim.
Request early access
Audex is in pre-release. We're looking for quantitative researchers and alternative data teams who want to test the verification pipeline on their real filings. Free access in exchange for honest feedback.
CLI + API access. No dashboard, no screenshots of things that don't exist yet.