Vaquill AI vs OpenLaws: US legal data API comparison

Both Vaquill AI and OpenLaws are APIs for US primary law. This is a factual, side-by-side comparison of coverage, endpoints, retrieval, output, and access. Every figure for Vaquill AI comes from our coverage page; every claim about OpenLaws links to their own public documentation.

Data coverage

CorpusVaquill AIOpenLaws
US Code (federal statutes)54,853 sectionsYes (exact count unpublished)
Code of Federal Regulations219,447Yes (exact count unpublished)
Federal Register (proposed + final agency rules)384,794Not in the API
Federal agency guidance (IRS notices, SSA rulings)2,584No
Executive orders3,901Yes (exact count unpublished)
Federal Rules of Procedure541Partial (under court rules)
US Constitution74Yes (exact count unpublished)
US Supreme Court RulesIn DB, getting reviewed before adding to APIPartial (under court rules)
DOJ + FTC Merger Guidelines (2023)In DB, getting reviewed before adding to APINot in the API
DOJ Antitrust Leniency PolicyIn DB, getting reviewed before adding to APINot in the API
US Copyright Office CircularsIn DB, getting reviewed before adding to APINot in the API
US Sentencing GuidelinesIn DB, getting reviewed before adding to APINot in the API
US Tax TreatiesIn DB, getting reviewed before adding to APINot in the API
Tax Treaty Technical ExplanationsIn DB, getting reviewed before adding to APINot in the API
DOJ Justice ManualIn DB, getting reviewed before adding to APINot in the API
USCIS Policy ManualIn DB, getting reviewed before adding to APINot in the API
USPTO MPEPIn DB, getting reviewed before adding to APINot in the API
USPTO TMEPIn DB, getting reviewed before adding to APINot in the API
FAR / DFARS (federal government contracting)Coming by end of September 2026Not in the API
Federal Reserve / OCC / FDIC guidance (banking regulation)Coming by end of September 2026Not in the API
FinCEN administrative rulings (BSA/AML)Coming by end of September 2026Not in the API
NLRB Advice Memos and GC MemorandaComing by end of September 2026Not in the API
CFTC guidanceComing by end of September 2026Not in the API
HHS / OCR guidance (HIPAA)Coming by end of September 2026Not in the API
BIS export control guidance + State Dept ITAR (DDTC)Coming by end of September 2026Not in the API
CPSC guidanceComing by end of September 2026Not in the API
NAIC model laws / state insurance regulationComing by end of September 2026Not in the API
FCC / FERC / DOE guidanceComing by end of September 2026Not in the API
State statutes~2.0M across 52 jurisdictions (50 states + DC + PR)50 states + DC + PR
State administrative regulations~1.16M across 45 statesYes (exact count unpublished)
State constitutions~7,700 across 51 jurisdictionsYes (exact count unpublished)
State court rules~11,900 across 10 statesLimited, more on roadmap
Case law opinionsAvailable in the platform, not the data API10.3M opinions across 6,000+ courts
Reported primary-law total4.8M+ sections~4.51M statute and regulation documents

Section counts are distinct provisions. For retrieval, Vaquill AI splits longer sections and documents into passages, so the searchable index holds over 9.8M passages across those 4.8M+ sections, with the Federal Register's long agency rules accounting for more than half.

Vaquill AI uniquely serves the federal administrative-law layer through the API: the Federal Register, agency guidance, and executive orders. OpenLaws uniquely serves case law through the same API.

Loading diagram...

Endpoints and capabilities

OpenLaws exposes 10 read-only GET endpoints. Vaquill AI matches every one of its statute-and-law endpoints (search, citation resolution, hierarchy browse, section text, the law catalog) and adds neighboring-section lookup, batch metadata, a structured subsection tree, and an AI endpoint; OpenLaws adds case-law endpoints (courts and opinions) that Vaquill AI does not expose in the data API.

CapabilityVaquill AIOpenLaws
Full-text searchPOST /statutes/search (semantic + keyword)GET /jurisdictions/{j}/laws/search (keyword)
Search within one law or codecorpusType + state + code filtersGET /jurisdictions/{j}/laws/{law}/search
Search within a hierarchy subtreechapter / part filters (feed a result's parent back)within_division_path param
Resolve a Bluebook citationGET /statutes/resolve (statutes, regulations, constitutions, court rules; annotated U.S.C.A./U.S.C.S. forms)GET /jurisdictions/{j}/laws/citations
Catalog the bodies of lawGET /statutes/laws (all or per-jurisdiction)GET /laws, GET /jurisdictions/{j}/laws
Browse the hierarchyGET /statutes/divisionsGET /jurisdictions/{j}/laws/{law}/divisions/{path}
Section metadataGET /statutes/section/{id}Returned within a division
Full section textGET /statutes/section/{id}/bodyReturned within a division
Structured subsection treeGET /statutes/section/{id}/body?structured=trueMarkdown in the division
Neighboring sectionsGET /statutes/section/{id}/relatedNot available
Rulemaking history for a Federal Register documentfrRelatedDocuments on GET /statutes/section/{id}: its proposed rule, final rule, and corrections, linked by RINNot available (no Federal Register in the API)
Batch metadata (up to 50)POST /statutes/sectionsNot available
Coverage discoveryGET /statutes/states, /codes, /coverage, /lawsGET /jurisdictions, /laws
Case law by citationNot in the data APIGET /jurisdictions/{j}/opinions/citations
CourtsNot in the data APIGET /jurisdictions/{j}/courts
AI question answering and groundingPOST /askNot available

Search and retrieval

Vaquill AIOpenLaws
MethodHybrid: semantic (vector) + keywordKeyword; semantic in user research
Match operatorsany / all / phraseor / and / phrase
Configurable excerpt lengthexcerptChars (100 to 4000)Full division content
Navigable resultparent object per hit (feed back to search or browse its container)Path + ancestors on the division
Plain-language queriesMatch without exact termsBest with exact terms
Citation-first lookupYesYes
Hierarchical (path) lookupYesYes

Text and output formats

Vaquill AIOpenLaws
HTMLYesYes (styled HTML on Enterprise)
Plain textYesYes
MarkdownYesYes
Formatted citation per resultEvery result carries a ready-to-use Bluebook citation and citationShort (e.g. 42 U.S.C. § 1983)Division carries display_name / identifier / path; format the citation yourself (no citation field)
Structured subsection tree (JSON)Yes: label, pincite, type, full pinpoint citation per nodeMarkdown with pincite identifiers
Deep link targetOfficial government source (govinfo.gov, state legislatures)Official government source (source_url, e.g. ecfr.gov) plus an OpenLaws-hosted page

Section metadata and provenance

Every section carries structured metadata, not just text.

Vaquill AIOpenLaws
Amendment credit linesourceCreditannotations
Parsed amendment historyamendmentYears, lastAmendedYear, amendmentsCountNot structured (inside the annotations string)
Public Laws referencedpublicLawsNot structured
Federal Register citationsfederalRegisterCitationsNot structured
CFR cross-referencescrossReferencesCfrIn the markdown body
USC cross-referencescrossReferencesUscIn the markdown body
Enabling statute for a regulationstatutoryAuthority: the USC citations that authorize the rule, parsed from its Authority noteNot structured
Regulations implementing a statuteimplementingRegulations: the CFR parts that implement a USC section, a reverse index built from every regulation's own authority citationNot available
Federal Register rulemaking metadatafrRegulationIdNumbers (RIN), frDocketIds, frCommentsCloseOn, frEffectiveOn, frSignificantNot in the API
Federal Register correctionsfrCorrectionOf, frCorrectionsNot in the API
Status and currencyactStatus, goodLawStatus, currencyNote, renumberedTo / transferredTois_repealed, is_reserved, renumbered, current_as_of
Provenance identifiersgranuleId, packageId (govinfo)source_url

Access and API surface

Vaquill AIOpenLaws
OnboardingSelf-serve API key, first call in minutesRequest access + a session
AuthenticationBearer tokenBearer token
API shapeREST (GET + POST)REST (10 read-only GET)
AI layerYesNo
Case law in the APINo (in platform)Yes

Data model

Vaquill AI scopes by corpusType (13 tokens such as USC, CFR, STATE, REGULATION, FEDERAL_REGISTER) plus a 2-letter state. Each section has a stable actId.

OpenLaws scopes by jurisdiction (FED, CA, FL) containing Laws (law_key such as FED-CFR, FL-STAT) made of Divisions addressed by path; case law is Courts and Opinions.

Summary

  • Vaquill AI covers the full federal administrative-law stack (Federal Register, agency guidance, executive orders), runs hybrid semantic plus keyword search, resolves citations across statutes, regulations, constitutions, and court rules, returns structured amendment provenance per section, includes an AI grounding endpoint, and is self-serve.
  • Vaquill AI's regulatory-tracking depth goes beyond having the Federal Register at all: statutoryAuthority and implementingRegulations link every regulation to the statute that authorizes it and back, and frRelatedDocuments follows one rulemaking's RIN from proposed rule to final rule to any later correction, none of which OpenLaws' API can do without Federal Register coverage.
  • OpenLaws covers case law in the same API (10.3M opinions), reports a larger total statute and regulation corpus, and uses one unified jurisdiction data model.
  • Both provide Bluebook citation resolution, hierarchical browse, a catalog of the bodies of law, structured subsection data, official government source links, and the US Code, CFR, state statutes, state regulations, and constitutions.

Sources: OpenLaws figures and limits from their coverage, capabilities, and API reference; Vaquill AI figures from our coverage page.

The most complete US primary law API.
Every US statute, regulation, constitution, and executive order through one REST and MCP API. 4.8M+ sections, section-level citations, and links to the official source. Plus a free open dataset.
10 min read

New legal AI guides, weekly.

Priyansh Khodiyar

Priyansh Khodiyar

Co-Founder & CTO

Priyansh leads engineering and AI at Vaquill, from the matter workbench to drafting, document comparison, document matrix, and citation-verified research.