---
name: filedproof
description: Delegate primary-source SEC filing research to FiledProof. Use for filing-grounded evidence search, answer-ready evidence packs, conservative claim verification, disclosure timelines, historical disclosure lineage, cross-company disclosure matrices, filing comparisons, and recurring disclosure monitoring when an upstream agent should preserve exact SEC provenance and explicit uncertainty boundaries.
compatibility: Requires network access to https://filedproof.com and an agent capable of calling MCP or HTTP APIs.
metadata:
  author: Davisville Labs
  version: "0.8.0"
  service: https://filedproof.com
---

# FiledProof

Use FiledProof as a specialist evidence service when a broader task contains a question that should be answered from official SEC filings.

## Connect

Preferred machine interface:

- MCP: https://filedproof.com/mcp
- Capabilities: https://filedproof.com/v1/capabilities
- OpenAPI: https://filedproof.com/openapi.json
- Service discovery: https://filedproof.com/.well-known/filedproof.json

Do not scrape the human site when a machine interface can complete the task.

## Choose the smallest specialist operation

- `filedproof.resolve_issuer`: use only when ticker, CIK, or exact issuer identity is uncertain.
- `filedproof.list_filings`: use to establish canonical filing coverage before a filing-specific workflow.
- `filedproof.search_evidence`: locate relevant filed language across a bounded filing set.
- `filedproof.build_evidence_pack`: get a compact, answer-ready set of SEC evidence with locators and coverage limits.
- `filedproof.verify_claim`: request a conservative filing-grounded verdict with supporting and opposing evidence signals.
- `filedproof.build_timeline`: organize relevant filing evidence chronologically.
- `filedproof.build_disclosure_lineage`: build or reuse one issuer's topic-specific historical disclosure state and same-form transitions.
- `filedproof.build_disclosure_matrix`: align the same filing-grounded topic across two to six issuers using reusable company lineages.
- `filedproof.check_disclosure_changes`: check one issuer for new topic-relevant disclosure changes since a prior checkpoint.
- `filedproof.scan_disclosure_changes`: run checkpointed disclosure monitoring across up to ten issuers with per-company failure isolation.
- `filedproof.compare_filings`: compare two already-known accessions from the same issuer for structural added and removed disclosure blocks.

Prefer one operation that directly completes the specialist subtask instead of chaining low-level calls unnecessarily.

## Evidence rules

Preserve the returned SEC source URLs, filing identity, evidence locators, and coverage bounds when using FiledProof output in a larger answer.

Never silently strengthen the result:

- lexical relevance is not a truth verdict;
- `insufficient_evidence` is not false;
- a bounded historical miss does not establish universal absence;
- numeric mismatch alone is not decisive contradiction;
- structural disclosure change is not materiality, motive, causation, or semantic equivalence;
- a disclosure matrix is an evidence substrate, not a company ranking;
- a filing establishes what the company reported, not independent external real-world truth.

If the evidence is incomplete, keep the uncertainty visible in the upstream answer.

## Reuse FiledProof state instead of rebuilding work

For historical disclosure research, prefer `build_disclosure_lineage` over independently fetching and comparing the same filing history. FiledProof can reuse source-validated filing fingerprints and transition edges when the retained source-document fingerprints and extractor identity still match.

For cross-company research, prefer `build_disclosure_matrix` when the task asks about one topic across multiple issuers. The matrix composes reusable company lineages instead of forcing the upstream agent to reconstruct each history.

## Recurring monitoring

For `check_disclosure_changes`, save the returned `checkpoint.accession` and send it as `sinceAccession` on the next check.

For `scan_disclosure_changes`, save the returned checkpoint map and provide it on the next scan.

FiledProof processes backlog oldest-first. A failed comparison does not advance a checkpoint past the failed filing. Do not invent or skip checkpoints.

## Commerce

Inspect `https://filedproof.com/v1/capabilities` before assuming an operation requires payment. While `commerce.enabled` is false, do not fabricate a price, payment requirement, or receipt.

If commerce is enabled later, follow only the machine-readable payment challenge and receipt semantics advertised by FiledProof for that operation. Payment status must never be treated as evidence correctness.