Stop Building Statute Data Infrastructure from Scratch
We have already indexed US primary law. Search the US Code, the CFR, and all 52 state and territory statute codes through a REST API, with section text, hierarchy, and amendment history. Plus an MCP server so AI agents can reach statute data natively.
The Problem Legal Tech Developers Face Today
Sourcing US Primary Law Is a Slog
The US Code, the CFR, and 50 separate state code trees live behind inconsistent government sites with different formats and update schedules. Assembling them into one clean corpus is months of work before you write a line of product.
Government Formats Are Brittle to Parse
Statute text ships as PDFs and XML with broken formatting, nested tables, and footnotes. Extracting clean, structured sections that survive across titles and states takes specialized parsing, not a generic loader.
Hierarchy and Amendment History Are Hard
A section is not just text. You need the title-chapter-section hierarchy, the citation, and the amendment history (substitutions, insertions, omissions) to show users what changed and when.
Data Freshness Is a Constant Battle
Official sources publish updates on their own cadence. Your pipeline needs continuous re-ingestion, re-chunking, and re-indexing. Miss an update and your users get stale law.
Search Infrastructure Adds Months of Engineering
Embedding the corpus, storing vectors, tuning retrieval, and ranking results is another long project before you can ship a usable statute search.
No Standard Protocol for AI Agent Integration
Your AI agent needs statute data but every source means custom HTTP clients, auth flows, and response parsing. There is no standard way to plug legal data into agent frameworks.
How Vaquill AI Helps Legal Tech Developers
Statute Search API
Search across the US Code, the CFR, and all 52 state and territory statute codes in one call. Filter by corpus and state, get relevance-ranked JSON with citations and links.
- ✓POST /api/v1/statutes/search with a query and optional corpus and state filters
- ✓Returns citation, title, excerpt, hierarchy, relevance score, and source links
- ✓Scope to USC, CFR, a single state, the Constitution, Federal Rules, or Executive Orders
- ✓Skip embeddings, indexes, and search tuning entirely
Section Metadata and Full Text
Pull metadata or the full text of any section by its actId, with hierarchy, edition year, and download links.
- ✓GET /api/v1/statutes/section/{actId} for citation, hierarchy, and links
- ✓GET /api/v1/statutes/section/{actId}/body for HTML and plain text
- ✓Amendment history available per section
- ✓Cite-ready output for documents and motions
Coverage Discovery
Discover which jurisdictions and codes are queryable before you call search, so your client knows the shape of the corpus.
- ✓GET /api/v1/statutes/states for jurisdictions and per-jurisdiction section counts
- ✓GET /api/v1/statutes/codes?state=tx to list a state’s distinct codes
- ✓Returned actId values plug straight into search filters
- ✓One round-trip discovery for your client
MCP Server - Native AI Agent Access
A Model Context Protocol server that exposes the statute endpoints as tools. Install once and any MCP-compatible agent (Claude, Cursor, VS Code, Windsurf) can search statutes and pull section text.
- ✓Install with pip install vaquill-mcp (or uvx vaquill-mcp)
- ✓Works with Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf
- ✓Standard protocol, no custom HTTP clients or auth flows
- ✓Tools for statute search, section lookup, coverage, and amendments
How It Works
Get started in minutes, not weeks.
Get Your API Key
Sign up and generate a vq_key_ token from the dashboard. Self-serve, no sales call required. Questions or higher volume, email contact@vaquill.ai.
Explore the Endpoints
Full API documentation with request and response examples for statute search, section lookup, section text, coverage, and codes.
Integrate in Hours, Not Months
Make your first call. Structured JSON responses mean you can parse and display results immediately. Or wire in the MCP server for agents.
Ship and Scale
Focus on your user experience. We handle sourcing, parsing, hierarchy, amendment history, and data freshness across 3.5M+ sections of US primary law.
Questions from Legal Tech Developers
What does the API cover?
The US Code, the Code of Federal Regulations, and the statute codes of all 52 US jurisdictions (50 states, DC, and Puerto Rico), plus the U.S. Constitution, the Federal Rules, and Executive Orders since 2015. About 3.5M+ sections of US primary law, with section-level citations and direct links to the official text.
How fresh is the data behind the API?
The corpus is re-ingested weekly for federal corpora (state regulations monthly) as official sources publish updates, with amendment history preserved per section. Presidential Documents come from the Federal Register.
What response format do the endpoints return?
All endpoints return JSON. Each result includes the section citation, title, full hierarchy, a relevance score, and direct links to the HTML, PDF, and official source so you can render or verify the exact provision.
What is the MCP server and why should I use it instead of REST?
MCP (Model Context Protocol) is a standard for connecting AI agents to external data. If you are building an AI agent or coding assistant, install vaquill-mcp and your agent gets statute tools without writing HTTP client code. For traditional backends, use the REST API directly.
Do I need an SDK or can I use raw HTTP?
Use the REST API directly with any HTTP client in any language, or wire in the MCP server for AI agents. Responses are plain JSON, so no SDK is required.
Build on US Statute Data
Stop building statute-data infrastructure. Search the US Code, the CFR, and all 52 state and territory codes through one API, already indexed and hosted.