sec-api.io Alternatives: Filings, or the Figures Inside Them

The closest thing to a like-for-like in this category, and the comparison that most often gets framed wrongly. They give you the filing. This gives you one statement out of it, resolved and checked. If you need the document, no part of this page helps.

At a glance

Prices and features on the right-hand column change, and this page does not — check their site before you decide anything on it. The rows about method are the ones that stay true.

BalanceProof compared with sec-api.io
  BalanceProof sec-api.io
Primary object One balance sheet, resolved A filing, and everything in it
Full-text search None Yes, and good at it
Form coverage Periodic filings only Every form type — 8-K, S-1, 13F, Form 4 and more
Duplicate-tag resolution Done for you, by the identity Yours to do — the tags arrive as filed
Tells you when a statement does not reconcile Yes, with the reason Not applicable — it is not selecting for you
If you already have a reconciler you trust You want their raw access, not this Stay
Free tier 1,000 calls/month, no card Check their site

Why transparency matters more than a number

Every provider in this category reads the same filings. The difference is what happens when a filing is hard to read. The usual answer is that you get a number anyway, with nothing attached to say how confident it is — and a figure that is quietly a segment instead of a company looks exactly like one that is right.

BalanceProof checks every balance sheet against Assets = Liabilities + Equity before publishing it. A filing that reconciles is published with its figures. A filing that does not is published with the reason: a noncontrolling interest reported as a separate line, mezzanine equity outside permanent equity, rounding inside one percent, a component we could not read, or a filing whose own totals disagree with each other. The exceptions are counted in public and named individually on how we verify.

That is the whole claim. Not that nothing is ever wrong — that when something is, you are told which number and why, instead of finding out from your own reconciliation three weeks later.

The difference is which tag gets picked

Every provider in this category reads the same source. SEC EDGAR publishes XBRL for every filer, free, and nobody has better raw material than anybody else. What separates one API from the next is not access. It is the selection step, and that step is almost never documented.

Here is the problem it has to solve. Open JPMorgan's 10-Q and search for Assets and you get twenty-three facts. Not twenty-three values — twenty-three tagged instances, one for the consolidated bank and one for each segment and subsidiary that has to be broken out separately. Every one is valid XBRL. Exactly one is the number on the face of the balance sheet, and the only thing marking it is an absence: it is the fact with no dimensions attached.

An extractor that takes the first match, or the largest, or the most recently filed, will be right most of the time and wrong in a way that leaves no trace. No exception, no null, no warning. Just a number that is a segment instead of a company. Measured across the filings loaded here, that naive approach disagrees with the consolidated figure often enough to matter — roughly one filing in five.

BalanceProof resolves it with arithmetic rather than a heuristic: pull every candidate for assets, liabilities and equity, and keep the combination that satisfies Assets = Liabilities + Equity. The consolidated figures balance against each other. A segment's assets do not balance against the whole company's liabilities. The identity is a test, not a guideline, and it is the reason a figure here is checked rather than guessed at.

When nothing balances, the answer is that nothing balances. The filing is served as-reported with a warning on it rather than adjusted until the columns agree, because a filing that does not add up is a fact about the company, and you should get it as one.

What I am not going to pretend

I am not going to put sec-api.io's prices in a table on my own website. They change, this page would not, and you would be reading a number I had no way to verify at the moment you read it. Go and look at their pricing page. It is the only copy that is current.

I am also not going to tell you their data is bad. I have not audited it and I am not in a position to. What I can tell you is what this service does and how to check it, which is the part I am actually responsible for.

The check that settles it costs you nothing either way: take a company where you already know the answer, call both, and compare each against the filing on EDGAR. Not against each other — against the filing. That is the only comparison that means anything, and it is why the free tier here needs no card.

When to choose each

Choose BalanceProof

If the number has to be right.

  • You do not want to write the resolver. JPMorgan's 10-Q carries more than twenty facts tagged Assets. Picking the right one is the work, and it is the work this site does.
  • You want the identity checked before you see the number.
  • You want the exceptions counted in public rather than discovered in your own reconciliation three weeks later.
Choose sec-api.io

If any of these is you.

  • You need the document. Exhibits, 8-K monitoring, full-text search, forms this site never touches. Different product, and a good one.
  • You want raw tags because you resolve them yourself. That is a legitimate and often correct choice — then a service that has already chosen for you is in the way.
  • You need filings the moment they land.

The method, written out

These pages compare on METHOD because method is the part that stays true. Both of these are the method itself rather than an argument about it, so you can judge the claim rather than take it.

Compare

The same question from the other directions. Every one of these compares on method, for the reason at the top of this page.