get a key
steadybase-$ docs receipts
rulea verbatim quote with a receipt, or nothing
sampled50 receipts, no key, 2026-09-18
opened17 anonymously
keyed22 need a key
blocked11 public page, refused our fetcher
kinds
publica filing on sec.gov, an investor relations page, a deck at its page numberopens for anyone, no key
keyedapi.steadybase.io/v1/receipt/<id>?start=&end=, the exact character range in a transcript401 without a key; the most precise receipt there is
blockeda public page whose host refuses an automated fetchopens in a browser, refuses a script
opening a keyed one
curl -s 'https://api.steadybase.io/v1/receipt/<transcript_id>?start=5128&end=5262' \
  -H 'Authorization: Bearer $STEADYBASE_KEY'

start and end are character offsets into the transcript, so the receipt resolves to the exact sentence rather than the top of a document. Without a key the same URL answers 401, which is why every page here labels that link as needing one.

measured, per lane
lanesampledopenedrate
call_signals_verified 88 39 44.3%
call_te_lexical 56 0 0%
filing_passages 97 96 99%
deck_statements 92 82 89.1%
ai_signals 77 72 93.5%
web_announcements 43 39 90.7%
filing_relationships 81 80 98.8%

Those rates are published because a receipt that does not open is not a receipt. The two low lanes point at keyed or stored objects rather than public URLs, and are being moved.

coverage/our-data/
docs/docs/
steadybase-$