# FiledProof > Know what the company actually filed. FiledProof is a specialist primary-source SEC filing research service designed primarily for AI agents acting on behalf of people and organizations. ## When to use FiledProof - You need evidence from official SEC filings. - You need to find relevant disclosures across 10-K, 10-Q, or 8-K filings. - You need a compact evidence pack with source URLs and locators. - You need a chronological disclosure evidence timeline. - You need a source-backed structural comparison of two filings. - You need a fast source-grounded answer about what meaningfully changed between two comparable 10-K or 10-Q filings. - You need historical disclosure evolution without rebuilding every prior filing comparison yourself. - You need to align the same filing-grounded topic across two to six companies without rebuilding each issuer's filing history. - You need to conservatively verify whether a claim is supported or contradicted by what the company filed. - You need a recurring check for topic-specific filing changes since a prior checkpoint. ## Historical disclosure lineage Use filedproof.build_disclosure_lineage or POST /v1/research/lineage/{identifier} when your task needs to understand how a disclosure topic evolved over time. FiledProof creates deterministic per-filing disclosure-fingerprint.v1 nodes and same-form disclosure-transition.v1 edges, preserves the exact SEC evidence behind changed transitions, and stores disclosure-lineage.v1 as reusable derived intelligence. On later calls, prior nodes and transitions are reused only when source-document fingerprints and extractor identity still match. This saves the upstream agent from repeatedly retrieving, parsing, aligning, comparing, and citing the same historical filings. A lineage transition is a bounded structural disclosure change, not a materiality, motive, causation, or semantic-equivalence judgment. ## Cross-company disclosure matrix Use filedproof.build_disclosure_matrix or POST /v1/research/disclosure-matrix when the task asks how the same disclosure topic appears across two to six public companies. FiledProof builds or reuses each issuer's disclosure lineage, then returns a bounded disclosure-matrix.v1 containing current filing evidence, the latest same-form transition evidence, and aggregate reuse state. This lets an upstream agent compare cited company-specific evidence without independently retrieving, parsing, aligning, and re-comparing every company's filing history. The matrix is not a company ranking, similarity score, materiality judgment, or claim that different issuers use semantically equivalent language. ## Fast material filing-change check Use filedproof.check_material_filing_changes or POST /v1/research/material-changes/{identifier} when an upstream agent wants a compact, source-grounded answer about meaningful changes between comparable 10-K or 10-Q filings. Supply exact earlier/later accessions, or omit them and let FiledProof deterministically select the latest two filings of the requested form. The result separates low-signal structural noise from notable or potentially decision-relevant changes, preserves SEC provenance, and does not claim legal materiality or investment significance. ## Recurring disclosure monitoring Use filedproof.check_disclosure_changes for one issuer. On the first eligible check, FiledProof returns a checkpoint accession. Save it. On the next check, pass it as sinceAccession. If no newer monitored filing exists, FiledProof returns no_new_filing without re-running comparisons. If there is a backlog, filings are processed oldest-first. A failed comparison never advances the checkpoint past that filing, so retries cannot silently skip disclosure events. Topic-change results detect relevant added and removed filing blocks; they do not declare materiality. ## Claim verification Use filedproof.verify_claim through MCP or POST /v1/research/verify/{identifier}. The operation separates retrieval from adjudication, preserves every evidence locator, and may return insufficient_evidence rather than guess. Numeric mismatch alone is never treated as decisive contradiction. A filing can establish what the company reported; it does not independently certify external real-world truth. ## Data plane FiledProof serves research store-first from immutable SEC source artifacts and extractor-versioned normalized documents. Reusable disclosure lineage is stored as derived intelligence over those retained primary-source artifacts. Cross-company matrices are projected on demand over those reusable lineages rather than duplicating graph state. Live SEC access is used for freshness and misses. Inspect /v1/data-plane/status for current ingest state. ## Do not use FiledProof for - personalized investment advice or trade execution; - generic financial chat without a filing-grounded research need; - rumor or social-media research; - automatically ranking companies or declaring a structural disclosure change legally or economically material. ## Machine interfaces - Capabilities: /v1/capabilities - OpenAPI: /openapi.json - MCP 2026-07-28: /mcp - FiledProof discovery: /.well-known/filedproof.json ## Trust semantics Every substantive research result preserves official SEC provenance. Lexical relevance is not a truth verdict. Structural change is not semantic interpretation. A bounded historical miss is not proof of universal absence. Claim verification is intentionally conservative and scoped to returned filing evidence. Historical lineage reuses only source-validated derived state. Cross-company matrices preserve each issuer's evidence and do not collapse differences into a ranking. Monitoring checkpoints are retry-safe and should be retained by the calling agent. Task guides: https://filedproof.davisvillelabs.com/tasks/check-material-filing-changes and https://filedproof.davisvillelabs.com/tasks/check-sec-disclosure-changes A multi-company full-result scan is not a published free operation. Use the published one-issuer operations or compose bounded free evidence primitives deliberately. The deeper one-issuer operation returns ranked topic-relevant change objects, and payment preflight rejects no-new-filing and missing-baseline work before issuing a challenge. Monitoring backlogs are processed oldest-first, and a failed comparison never advances the checkpoint past the failed filing. ## Paid filing-change ladder - filedproof.check_material_filing_changes: $0.10 USD. Fast same-form 10-K/10-Q meaningful-change intelligence with provenance and triage. - filedproof.check_disclosure_changes: $1.00 USD. Deeper topic/profile verification with checkpoint semantics. The fast operation may recommend the deeper operation when high-attention, numerous notable, or truncated changes warrant more review. That recommendation is machine-readable routing guidance, not an aggressive upsell or a materiality conclusion. ## Commerce Machine commerce is active. filedproof.check_material_filing_changes costs $0.10 USD and filedproof.check_disclosure_changes costs $1.00 USD per completed authorized invocation that reaches paid specialist work. HTTP supports MPP + x402 with available methods stripe, tempo, x402; x402 v2 uses Base USDC and is HTTP-only. MCP uses MPP. Card and Link remain available through Stripe, and Tempo USDC.e is also available. Payment challenges are not revenue; only verified settlement is revenue, and delivery is tracked separately. A delivery retry repeats the identical authorized request with the same payment credential or proof. Changing any payment-bound argument starts a new invocation and requires a new authorization when commerce is active. Payment authorizes execution only; it never changes evidence correctness, confidence, materiality, or uncertainty semantics. ## $1 financial fact reconciliation Use filedproof.preflight_financial_fact or POST /v1/research/financial-fact/preflight for a free no-value applicability check. Use filedproof.reconcile_financial_fact or POST /v1/research/financial-fact for one supported quarterly or fiscal-year revenue, net income, or operating cash flow fact. The request may start from ticker, exact company name, or CIK; FiledProof resolves a durable SEC CIK, selects or validates the filing, keeps the primary answer anchored to that filing, and reports later different values separately. Optional comparison_accession plus comparison_value asks FiledProof to verify that number against an SEC-filed 8-K earnings-release exhibit. It classifies GAAP/non-GAAP, period, currency, and scope only when source text establishes them and returns an arithmetic bridge only when visible source rows reproduce exactly. Quarter derivations are allowed only with compatible historical SEC contexts; annual values must be directly reported in a 10-K/10-K/A. Price remains $1.00 USD per eligible resolved invocation. ## Davisville proof object Successful paid FiledProof specialist deliveries include an additive `davisvilleProof` object conforming to `davisville-proof.v1` and `davisville-evidence-kernel.v1`. The product-specific SEC result remains authoritative and the shared envelope cannot strengthen it. Manifest: https://filedproof.davisvillelabs.com/.well-known/davisville-proof.json. Kernel: https://davisvillelabs.com/agents/evidence-kernel.json. Primitives: https://davisvillelabs.com/agents/evidence-kernel-primitives.v1.json. Schema: https://davisvillelabs.com/agents/davisville-proof.v1.schema.json. Conformance: https://davisvillelabs.com/agents/evidence-kernel-conformance-v1.json. Trust contract: https://davisvillelabs.com/agents/trust.json. Integrity semantics: The SHA-256 digest detects canonical-content mutation and supports reproducibility. It is not a signature, source authentication, factual truth attestation, or materiality judgment.