- Type
- not stated
- Format
- Structured JSON over a RESTful/RPC API (session, master bill list, bill detail, bill text including base64-encoded bodies, amendments, roll calls, sponsors, legislators, full-text search) plus weekly bulk ZIP dataset archives and a Push API that POSTs change payloads on a 15-minute-to-4-hour cadence; a published entity-relationship diagram lets a buyer load it into their own warehouse
- Volume
- All 50 states, DC and the US Congress across every session, with full bill text, amendments, action histories, roll-call votes and legislator profiles; the public corpus is described as 200,000+ pieces of legislation tracked per release cycle, and the weekly bulk dataset archives ship getBill, getRollCall and getPerson record sets for every state and Congressional session
- Users
- Free public service plus paid subscribers - est. low thousands of accounts (inferred from a free tier of 30,000 API queries per month, per-state GAITS Pro pricing at roughly $5 per state per month, and an unfunded 1-10 person company serving public agencies, associations and enterprises)
- History
- not stated
- Update frequency
- not stated
- Growth
- Mature and stable rather than scaling — a continuously maintained corpus with an active API product and ongoing documentation, but an unfunded, ~1-10 person company with no funding rounds and a revenue band around $5.1M that has held for years
- Launched
- 2010 (company founded and led by the same owner since then; the platform's own positioning also cites over two decades of experience serving public agencies, associations and corporations, which refers to predecessor legislative-data work rather than the LegiScan product itself)
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated