Use case
Legal tech developers
Stop building statute data infrastructure from scratch.
Statutes API
US Statutes API: US Code, CFR and state codes
The US Code, the CFR and every state and territory code through one self-serve API: REST, MCP or SQL. Every section is cited and linked to its official source.
Build the pipeline yourself, or make one call.
The hard way
Build the pipeline yourself
- ✗Dozens of government sites, each in its own format
- ✗PDFs and XML with broken tables and footnotes
- ✗Section hierarchy, amendments and metadata
- ✗A search index you build and keep in sync
- ✗Re-scrape it all, forever, as the law changes
Weeks of setup. Maintenance that never ends.
The API
Or make one call
- ✓Indexed and normalized to one schema
- ✓Cited, with a link to the official source
- ✓Relevance-ranked; filter by state or corpus
- ✓Refreshed on a per-source schedule
One API key.
Endpoints you will use most
A selection of the endpoints listed on the public page. Try any of them in the playground (mock responses).
Section lookup
| Method | Path | What it does | Credits |
|---|---|---|---|
| GET | /api/v1/us/statutes/resolve | Resolve a citation straight to its section. | 1 |
| GET | /api/v1/us/statutes/section/{act_id} | Section metadata: citation, title, hierarchy. | 1 |
| GET | /api/v1/us/statutes/section/{act_id}/body | Full section text as HTML and plain text. | 2 |
| GET | /api/v1/us/statutes/section/{act_id}/related | The sections immediately before and after. | 1 |
| GET | /api/v1/us/statutes/sections | Batch metadata for up to 50 sections. | 5 |
Discover the corpus
| Method | Path | What it does | Credits |
|---|---|---|---|
| GET | /api/v1/us/statutes/laws | Catalog the bodies of law available, by jurisdiction. | 0 |
| GET | /api/v1/us/statutes/divisions | Walk the statutory hierarchy one level at a time. | 0 |
| GET | /api/v1/us/statutes/coverage | Self-describing coverage matrix. | 0 |
Search
| Method | Path | What it does | Credits |
|---|---|---|---|
| POST | /us/statutes/search | Relevance-ranked search; filter by corpus, state, title. | 2 |
Alerts
| Method | Path | What it does | Credits |
|---|---|---|---|
| POST | /api/v1/watches | Create a watch on a source; webhook and/or email. | 0 |
| GET | /api/v1/watches | List your watches. | 0 |
Pricing
| Method | Path | What it does | Credits |
|---|---|---|---|
| GET | /api/v1/pricing | Current credit pricing (no auth). | 0 |
Who builds on it
Teams use the API instead of scraping and normalizing government sources themselves.