--- name: filedproof description: Delegate primary-source SEC filing research to FiledProof. Use the paid disclosure-change operation when an upstream agent needs the new filing changes that deserve attention first, with deterministic prioritization, compact before/after evidence, exact SEC provenance, uncertainty, and retry-safe checkpoint state; use the free primitives for issuer resolution, coverage checks, evidence retrieval, verification, lineage, and lower-level comparison. compatibility: Requires network access to https://filedproof.davisvillelabs.com and an agent capable of calling MCP or HTTP APIs; when commerce is active, the client must be able to return an MPP payment credential through MCP metadata or HTTP headers. metadata: author: Davisville Labs version: "0.8.0" service: https://filedproof.davisvillelabs.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.davisvillelabs.com/mcp - Capabilities: https://filedproof.davisvillelabs.com/v1/capabilities - OpenAPI: https://filedproof.davisvillelabs.com/openapi.json - Service discovery: https://filedproof.davisvillelabs.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 when ticker, CIK, or exact issuer identity is uncertain. - `filedproof.list_filings`: establish canonical filing coverage and confirm relevant forms/checkpoints before a paid disclosure-change call. - `filedproof.search_evidence`: locate relevant filed language. - `filedproof.build_evidence_pack`: get a compact answer-ready set of SEC evidence. - `filedproof.verify_claim`: request a conservative filing-grounded verdict. - `filedproof.build_timeline`: organize evidence chronologically. - `filedproof.build_disclosure_lineage`: build or reuse one issuer's topic-specific historical disclosure state. - `filedproof.build_disclosure_matrix`: align the same topic across two to six issuers. - `filedproof.check_disclosure_changes`: configured $15.00 USD specialist result when runtime commerce is active. It finds new same-form filing changes relevant to a topic, ranks what deserves review, explains deterministic signals, returns compact before/after evidence with exact SEC provenance, states uncertainty, and preserves a retry-safe checkpoint. - `filedproof.compare_filings`: lower-level free structural comparison of two known accessions. It does not include the paid operation's prioritization, decision objects, or recurring checkpoint workflow. Prefer one operation that directly completes the specialist subtask instead of chaining low-level calls unnecessarily. ## What the $15 disclosure-change operation buys Use it when the upstream task is closer to "what meaningfully changed in this issuer's filed disclosure since my last checkpoint, what deserves attention first, and what exact SEC evidence supports that triage?" rather than "show me a redline." The result preserves the existing structural evidence and adds bounded decision compression: - deterministic change category and high/medium/low attention triage; - explainable signals such as numeric/date changes, negation and qualification shifts, obligation wording, and legal/regulatory, liquidity, debt, cyber, and risk-factor context; - compact before/after evidence references and SEC locators; - explicit uncertainty and recommended follow-up; - aggregate change counts and review order; - retry-safe checkpoint semantics for recurring use. The machine result contract is `monitor-check.v1`. Inspect `status`, `haltedOnFailure`, `truncated`, `remainingNewFilings`, `events[].change.changes[]`, before/after evidence, and `checkpoint.accession`. MCP publishes an `outputSchema` for the paid tool and OpenAPI publishes the same response schema with representative incomplete-result examples. Attention is not legal, accounting, economic, or investment materiality. Before/after lexical pairing is not proof of semantic equivalence. ## Free pre-purchase evaluation If coverage is uncertain, call `filedproof.resolve_issuer` and `filedproof.list_filings` first. Confirm the issuer resolves, the intended forms exist, and a prior same-form filing is available. Payment preflight also validates applicability before returning a payment challenge; a latest checkpoint with no new filing or a scope without a same-form baseline does not proceed to paid work. ## Evidence rules Preserve returned SEC source URLs, filing identity, evidence locators, and coverage bounds. 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 and attention ranking are 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. ## Recurring monitoring For `check_disclosure_changes`, save the returned `checkpoint.accession` and send it as `sinceAccession` on the next **new invocation**. FiledProof processes backlog oldest-first. A failed comparison does not advance a checkpoint past the failed filing. If the result tells you to continue from a returned checkpoint, that changes the payment-bound arguments and is a new invocation. Do not confuse that with delivery recovery, which repeats the identical request and credential. ## Commerce Machine commerce is active. `filedproof.check_disclosure_changes` costs $15.00 USD per authorized invocation that reaches paid work. Stripe card/Link is available and Tempo USDC.e stablecoin is also available. FiledProof performs free applicability preflight before the payment challenge. An invalid checkpoint, no newer monitored filing, or no same-form comparison baseline is rejected before paid specialist execution. Published non-commercial operations remain free. Payment status must never be treated as evidence correctness, confidence, materiality, or stronger proof. ### Payment handoff No human checkout flow is required. A payment-capable agent should follow the machine challenge directly. - MCP: read challenges from `error.data.challenges`, place the selected credential in `params._meta['org.paymentauth/credential']`, then retry the identical `tools/call`. Read the receipt from `result._meta['org.paymentauth/receipt']`. - HTTP: read the MPP challenge from `WWW-Authenticate`, retry the identical method/path/raw JSON body with `Payment-Authorization` (`Authorization` is accepted as a compatibility fallback), and read the receipt from `Payment-Receipt`. - Settled Stripe delivery recovery: the same signed request and same credential can recover a previously settled delivery for 86400 seconds without another settlement. Expired unpaid credentials remain invalid. - Invocation boundary: A delivery retry repeats the identical authorized request with the same payment credential. Changing sinceAccession or any other payment-bound argument starts a new invocation and, when commerce is active, requires a new authorization. Payment status must never be treated as evidence correctness. ## Reconcile one quarterly financial fact ($1) Use `filedproof.preflight_financial_fact` first when applicability is uncertain. It is free and does not reveal the value. Use `filedproof.reconcile_financial_fact` only for revenue, net income, or operating cash flow for one fiscal quarter anchored to one 10-Q or 10-K. Prefer direct quarter facts. Accept cumulative subtraction only when the returned validation checks establish compatible concept, currency, fiscal year, consolidated entity-wide Company Facts scope, contiguous/nested periods, source filing identity, and no unresolved amendment/recast conflict. Preserve the returned SEC URLs and arithmetic. If FiledProof abstains, do not infer the missing number from the paid operation. ## 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.