Version 2.1.5May 2026

Justinian now surfaces the 157 billion-record legal and policy corpus, 13.125 billion court records, a full coverage catalog, cleaner agent routes, and tighter corpus navigation from the Justinian page.

157B
Legal and policy records
13.125B
Court records
137
Corpus types

The corpus scale is clear

The database claim now matches how teams actually inspect the corpus: records, court systems, jurisdictions, and policy datasets in one connected surface.

157 billion records

Justinian now presents the corpus as 157 billion legal and policy records across primary law, courts, legislation, municipal codes, and adjacent public-agency datasets.

13.125 billion court records

Court coverage sits in the same record-scale database as the rest of Justinian, connected to the statutes, regulations, dockets, filings, and opinions that legal teams need to inspect together.

Record-scale counts throughout

Coverage surfaces public-facing volume in record-scale terms, so source families, corpus cards, and court coverage all use the same field-level framing.

The corpus manifest

The release now exposes the source families behind the 157 billion-record database: federal law, state law, local codes, courts, and the adjacent regulatory datasets agencies use to make, enforce, and audit rules.

The federal corpus

Federal authority is available as record-scale primary law and agency material.

  • 224M regulations (CFR)
  • 19.775M Federal Register documents
  • 15.365M agency guidance documents
  • 5.74M Statutes at Large law sections
  • 4.165M codified statute sections (U.S. Code)

The state corpus - all 50 + DC

Every state corpus is represented across statutes, regulations, registers, acts, guidance, and legislation.

  • 196M agency guidance documents
  • 150.5M act sections
  • 112M codified statutes
  • 94.5M regulations
  • 52.5M state register documents
  • 24.85M acts
  • 20.895M register-derived documents
  • State bills across all states going back to 2009

The local corpus

Municipal codes are available across all 50 states.

  • Municipal codes across all 50 states

The court record

Court records sit beside the legal authority they interpret.

  • 13.125B state court records - dockets, opinions, entries, filings

The adjacent regulatory universe

Justinian also reads the operational datasets that agencies generate around the law: finance, health, labor, education, energy, environment, safety, transportation, agriculture, disclosures, and more.

  • 26.565B public finance records (appropriations, awards, obligations, procurement, campaign finance)
  • 17.22B CMS health records (provider, claims, enforcement)
  • 13.125B state court records
  • 12.32B agriculture records (FSA payments, USDA programs)
  • 4.76B BLS labor observations
  • 4.76B policing records
  • 4.06B K-12 education metrics
  • 4.025B FERC energy transactions
  • 3.15B EPA environmental records
  • 2.835B federal energy grid records
  • 2.765B FEC campaign finance records
  • 1.925B federal budget records
  • 1.505B federal regulation atomic texts (cross-indexed)
  • 1.365B FCC license records
  • 1.26B federal payroll records
  • 1.05B ERISA Form 5500 filings
  • 945M FEMA disaster records
  • 910M NFIP flood insurance records

Plus the rest of the regulatory map

The corpus also includes BTS transportation, FMCSA carrier safety, NHTSA recalls and crashes, EPA SDWA water systems, USDA SNAP, IRS 990 nonprofit filings, CFPB consumer complaints, NLRB labor cases, EEOC charges, FBI UCR, ATF licensee data, NIH RePORTER, DEA registrants, HUD housing, FAA airports, FTA transit, NAIC insurance, BLS labor markets, EIA energy facilities, VA veterans facilities, federal infrastructure approvals, NRCS easements, Census ACS, and more.

Coverage is easier to inspect

The corpus is no longer buried inside a long product-page explanation. The full ledger now has a dedicated route and a cleaner scan path.

Expanded coverage page

The coverage page now leads with 157 billion records and organizes the corpus across legal authority, courts, local codes, finance, health, environment, energy, labor, education, transportation, agriculture, disclosures, and state operational data.

Corpus cards on Justinian

The Justinian page now uses concise corpus cards that point to the full coverage catalog instead of forcing every source family into one dense section.

Latest corpus additions surfaced

Recent additions are visible as a source-update signal, including new public and reporting tables added to the accessible catalog.

The agent route is cleaner

Justinian is an agent, so the canonical page now lives where users expect it.

Canonical /agents route

The Justinian page is now available at /agents/justinian, with legacy /products/justinian URLs redirecting to the agent route.

Agent links updated

Navigation, product cards, Slack setup, release links, demo destinations, and student-access routes now point to the agent path.

Metadata and feeds refreshed

Site metadata, RSS, news sitemap, public sitemap, and structured routes now reflect the current Justinian positioning and corpus scale.

The page is tighter

The Justinian product page now scans like a product page instead of a manifest pasted into a layout.

Hero simplified

The hero now centers the 157 billion-record claim and uses compact coverage cards for law, courts, and policy data.

Corpus section condensed

The corpus section now gives the reader a clean path into coverage instead of repeating the entire source ledger inline.

Layout overflow fixed

The full coverage card and coverage-page manifest cards now span and wrap correctly, avoiding compressed columns and text overflow.

Ready to explore?

I am available now in Justinian 2.1.5. Bring a source-heavy matter, a folder of research materials, or a visual artifact and see how the workflow holds together.

This page’s interactive features did not load. Reloading usually fixes it. You can email sales@vulcan.ai for demos or support@vulcan.ai for help, and download Justinian for macOS or Windows directly.