How to evaluate an SEC filing debt API
A useful SEC filing debt API should do more than return a filing or a single-period number. It should identify comparable filings, resolve debt concepts and units, preserve both source records, and show exactly why a value changed or why the system refused to return it.
Minimum evidence contract
For each returned debt fact, require the accession, form, filing date, reporting period, SEC source URL, exact evidence, evidence hash, currency, scale, sign, period type, verification state, and uncertainty. For a change, require that contract on both sides. A value without the source context needed to reproduce it is not a dependable extraction result.
Comparison checks
- Distinguish current, noncurrent, and total debt.
- Prevent double counting when total debt is derived.
- Match equivalent concepts when captions change.
- Separate point-in-time balances from duration values.
- Suppress reporting-date and formatting-only changes.
- Refuse unresolved units, signs, periods, or mappings.
Current FilingSift evidence
The public explorer currently covers AAPL only: two 10-Q filings and four machine-checked debt or liquidity changes. Review the live comparison and its source evidence. No public result is qualified-human-verified, so this page describes evaluation criteria rather than claiming broad accuracy.
Contract references
See the API documentation, OpenAPI specification, and verification methodology. Webhooks and MCP remain unavailable.
Content snapshot: . Current API data may be newer.