How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Vaquill AI US Statutes API

Search and retrieve US primary law. Covers the United States Code and the Statutes at Large, the Code of Federal Regulations and its annual editions, state statutory codes and administrative regulations, federal and state constitutions, court rules, Federal Register rules and Presidential documents, federal and state agency guidance, agency adjudications, state Attorney General opinions, the Sentencing Guidelines and US tax treaties. Scope a search with the `corpusType` filter, and call `/us/statutes/coverage` for the live jurisdiction-by-corpusType list.- **Search**: Search across all USC, CFR, state, and regulatory sections- **Section**: Get metadata, citation, hierarchy, and source links for a specific section- **Body**: Get the full text of a section- **Enactments**: Which state session laws a publisher's own tables list against a section (supported jurisdictions only, never a complete history)

Vaquill AI US Statutes API is one of 26 APIs that Vaquill AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 18 JSON Schema definitions.

Tagged areas include US Statutes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, a changelog, and 18 JSON Schemas.

This API exposes 15 operations across 14 paths, and defines 52 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.vaquill.ai.

15 operations 14 paths 52 schemas 11 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.vaquill.ai/api/v1
Authentication
HTTP Bearer, API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

Vaquill AI US Statutes API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (vq_key_*) (ApiKeyAuth). An API key is passed in the header as X-API-Key (ApiKeyHeader). An API key is passed in the query as api_key (ApiKeyQuery). By default, every request must be authenticated.

  • ApiKeyAuth — API key issued from the developer dashboard. Pass as Authorization: Bearer vqkey... (preferred).
  • ApiKeyHeader — The same API key as a bare header value: X-API-Key: vqkey.... Equivalent to the Bearer form.
  • ApiKeyQuery — The same API key as a query parameter: ?apikey=vqkey.... Use only where you cannot set a header. A URL can end up in proxy and server logs, browser history and…

Paths & Operations 15

Across 14 paths, the API surfaces 15 operations — 11 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

US Statutes 15

Search and retrieve US primary law.

POST
/api/v1/us/statutes/search
Search US statutes, constitutions, court rules, and executive actions
search_statutes_api_v1_us_statutes_search_post body → 200402422
GET
/api/v1/us/statutes/section/{act_id}
Get statute section metadata
get_section_api_v1_us_statutes_section__act_id__get 1 param → 200404422
GET
/api/v1/us/statutes/resolve
Resolve a citation to its section
resolve_statute_citation 3 params → 200400401402429422
POST
/api/v1/us/statutes/resolve
Resolve many citations at once
resolve_statute_citations_batch body → 200401402422429
GET
/api/v1/us/statutes/section/{act_id}/related
Get the sections around this one
get_section_neighbors_api_v1_us_statutes_section__act_id__related_get 2 params → 200401402404429422
POST
/api/v1/us/statutes/sections
Get metadata for many statute sections
get_sections_batch_api_v1_us_statutes_sections_post body → 200401402422429
GET
/api/v1/us/statutes/section/{act_id}/body
Get statute full text
get_section_body_api_v1_us_statutes_section__act_id__body_get 4 params → 200404422
POST
/api/v1/us/statutes/count
Count the sections in a scope
count_statute_sections_api_v1_us_statutes_count_post body → 200401402422429
GET
/api/v1/us/statutes/coverage
Coverage matrix by jurisdiction and corpusType
list_statutes_coverage_api_v1_us_statutes_coverage_get → 200401403429
GET
/api/v1/us/statutes/divisions
Browse the statutory hierarchy
list_statute_divisions_api_v1_us_statutes_divisions_get 10 params → 200401402422429
GET
/api/v1/us/statutes/section/{act_id}/changes
Get this section's change history
get_section_changes_api_v1_us_statutes_section__act_id__changes_get 6 params → 200401402404429422
GET
/api/v1/us/statutes/section/{act_id}/enactments
Which acts a state publisher lists against this section
get_section_enactments_api_v1_us_statutes_section__act_id__enactments_get 1 param → 200401402404429503422
GET
/api/v1/us/statutes/section/{act_id}/cited-by
Find the sections that cite this one
get_section_cited_by_api_v1_us_statutes_section__act_id__cited_by_get 2 params → 200401402404429422
GET
/api/v1/us/statutes/section/{act_id}/definitions
Get the defined terms that govern this section
get_section_definitions_api_v1_us_statutes_section__act_id__definitions_get 1 param → 200401402404429422
GET
/api/v1/us/statutes/section/{act_id}/cross-state
Compare this provision against other states
get_section_cross_state_api_v1_us_statutes_section__act_id__cross_state_get 2 params → 200401402404429422

Schemas 52

The contract defines 52 schemas that model the data the API accepts and returns. The most detailed are StatuteResult (148 properties), StatuteSearchRequest (24 properties), StatuteBodyResponse (20 properties), SectionEnactment (17 properties). Each schema is shown below with its type and property counts.

FrRelatedDocument
object
One other Federal Register document sharing a RIN with this one. A Regulation Identifier Number (RIN) tracks one regulatory action through its lifecycle -- a p…
5 properties 1 required
SessionLawDenominator
object
How many laws a session is supposed to hold, and where that number comes from.
3 properties 2 required
UsFreeCallMeta
object
meta on a free discovery endpoint.
2 properties 1 required
UsStatutesCoverageEnvelope
object
What GET /us/statutes/coverage returns: the matrix under data. Declared because the route used to return a hand-built dict with no responsemodel, so its publis…
2 properties 2 required
SessionLawCitationCandidate
object
One session law a citation names.
14 properties 5 required
StatuteNeighborsResponse
object
Response for GET /us/statutes/section/{actid}/related.
7 properties 1 required
StatuteBodyResponse
object
Full text of a statute section in HTML and/or plain text.
20 properties 1 required
SessionLawDate
object
One printed date on a session law.
5 properties
StatuteCrossStateNeighbor
object
One out-of-state provision that addresses the same subject.
3 properties 3 required
ApiDetailError
object
Error envelope the API actually returns. Every error (400/401/402/403/404/405/422/429/5xx) carries a detail string, e.g. {"detail": "Insufficient API credits."…
2 properties 1 required
StatuteSectionResponse
object
Detailed section metadata (no full text, use /body for that).
4 properties 1 required
BodyFigure
object
One figure, equation or form image inside a rendered section body.
13 properties 1 required
EnactmentCoverage
object
What this answer is read from, and what it is not.
3 properties 1 required
StatuteSectionsResponse
object
Response for POST /us/statutes/sections.
7 properties
SessionLawSessionCoverage
object
One legislative session's session-law coverage.
13 properties 3 required
HTTPValidationError
object
1 property
StatuteSearchResponse
object
13 properties
StatuteChangeEvent
object
One time this section was added, amended, or removed by its publisher. An OBSERVED change, not a publisher-declared one. It exists because a refresh of the sou…
9 properties 4 required
UsJurisdictionCoverage
object
One row of the /us/statutes/states response.
8 properties 5 required
SessionLawCitationMatch
object
A citation that names a STATE session law rather than a code section.
16 properties 1 required
StatuteSearchRequest
object
24 properties 1 required
StatuteResult
object
A single statute section from search results.
148 properties 1 required
StatuteCitedByResponse
object
Response for GET /us/statutes/section/{actid}/cited-by.
8 properties 1 required
StatuteResolveResponse
object
Response for GET /us/statutes/resolve.
9 properties 2 required
StatuteResolveBatchItem
object
One citation's verdict inside a batch response. Deliberately the same field names as StatuteResolveResponse minus the per-request bookkeeping, so a caller migr…
7 properties 2 required
SectionEnactment
object
One printed entry of a publisher's table: this act, against this section.
17 properties 6 required
UsStatutesDivisionsResponse
object
Response for GET /us/statutes/divisions.
11 properties 2 required
UsDivisionNode
object
One child division in a GET /us/statutes/divisions listing. Interior nodes (titles, chapters, parts, codes, articles) carry a sectionCount and isLeaf: false; d…
6 properties 3 required
StatuteSectionsNotFoundDetail
object
Why one actId missed, and what to send instead. A bare id in notFound is ambiguous between the two things a caller most needs to tell apart: an id they built b…
3 properties 2 required
StatuteCrossStateResponse
object
Response for GET /us/statutes/section/{actid}/cross-state.
8 properties 1 required
StatuteChangesResponse
object
Response for GET /us/statutes/section/{actid}/changes.
11 properties 2 required
SectionIdentifierResolution
object
How the identifier you sent was matched, when it was not an exact actid. Present only when the input did NOT match as sent. Absent (null) means the section is…
4 properties 3 required
SectionEnactmentsResponse
object
Response for GET /us/statutes/section/{actid}/enactments.
11 properties 3 required
StatuteResolveBatchRequest
object
Batch citation resolution. See POST /us/statutes/resolve. /resolve took 1,159 calls in the 16 days to 2026-08-31, second only to search, and every one of them…
3 properties 1 required
ApiFieldError
object
One rejected field in a 422 response.
3 properties 3 required
UsCorpusTypeInfo
object
One entry in the coverage legend: what a corpusType token means.
6 properties 3 required
StatuteCountResponse
object
Response for POST /us/statutes/count.
5 properties
SessionLawJurisdictionCoverage
object
A jurisdiction's state session laws (acts as enacted), by session.
8 properties 3 required
StatuteSectionNotFoundError
object
The 404 from any /us/statutes/section/{actid}/... route.
4 properties 3 required
EnactmentSession
object
One legislative session of the jurisdiction whose code-section tables are read.
3 properties 1 required
StatuteDefinitionTerm
object
One defined term drawn from a chapter's definitions section.
3 properties 2 required
CitationOutsideFilters
object
A citation that names a real section the caller's own filters exclude. Both /search and /resolve treat a filter as a promise: a citation outside it is not forc…
6 properties 1 required
SubsectionNode
object
One node in a section's subsection tree (see /body?structured=true).
6 properties 2 required
StatuteResolveBatchResponse
object
Response for POST /us/statutes/resolve.
5 properties
SessionLawSession
object
The legislative session a law was enacted in.
4 properties 1 required
StatuteDefinitionsResponse
object
Response for GET /us/statutes/section/{actid}/definitions.
8 properties 1 required
StatuteCountRequest
object
Filter-only section count. See POST /us/statutes/count. Deliberately takes NO query. A count of "sections matching this query" does not exist: ranking runs ove…
9 properties
ValidationError
object
5 properties 3 required
UsStatutesCoverageResponse
object
Response for GET /us/statutes/coverage. A self-describing matrix: a legend of every corpusType token plus, for each jurisdiction, the per-corpusType ingested-d…
6 properties 4 required
StatuteSectionsRequest
object
Batch metadata lookup. See POST /us/statutes/sections.
2 properties 1 required
AsOfProvenance
object
Where an asOf body came from, and how far the evidence reaches. Every field but text on the parent exists so this answer cannot be over-read. The corpus holds…
12 properties 5 required
BodyTable
object
One table inside a rendered section body.
5 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vaquill-ai-us-statutes-api-openapi.yml Raw ↑

Other APIs Vaquill AI publishes across the network.

Vaquill AI Board Watches API
Vaquill AI Chronology API
Vaquill AI Clients API
Vaquill AI Comparisons API
Vaquill AI Compliance API
Vaquill AI Credits API
Vaquill AI Documents API
Vaquill AI Drafting API
Vaquill AI Facts API
Vaquill AI Folders API
Vaquill AI India Credits API
Vaquill AI India Pricing API
Where this information came from

This is an independent, third-party profile of Vaquill AI US Statutes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.