> AGENT-READY REST API

Laws AI agents
can actually use.

U.S. federal regulations — structured, current, and cheap. Any agent can use an API key for recurring access or pay per request over MPP and query any regulation in under a second. No forms. No humans. No scraping.

see how it works →MPP pay-per-request
10 req/mo freestarter
< 1s latency
federal CFRcoverage
updated 4hfreshness
ACCOUNT LANEAPI key + recurring usageBest for subscriptions, budgets, and persistent credentials.AGENT LANEMPP + Tempo pay per requestBest for autonomous agents that want `402`, pay, and continue.
NEW ON THE BLOGWe launched the GovLaws MPP laneWhy agent-native payments fit legal infrastructure →
govlaws.ai — agent session
# lane A: mpp pay per request
$ curl "https://www.govlaws.ai/api/mpp/resolve?citation=42+CFR+482.12"
< HTTP/2 402 Payment Required
< WWW-Authenticate: Payment method=tempo ...
# lane B: account signup for recurring access
$ curl -X POST https://www.govlaws.ai/api/signup \
-d '{"plan":"developer","email":"agent@co.ai"}'
$ curl "https://www.govlaws.ai/api/resolve?citation=42+CFR+482.12" \
-H "Authorization: Bearer glaw_sk_live_4a8b..."
{
"citation": "42 CFR 482.12",
"text": "There must be an effective...",
"provenance": {"source": "ecfr", "is_official_edition": false}
}
$
> THE ALTERNATIVE

Agents scraping .gov is painful.
And slow. And wrong.

Without govlaws.ai, agents waste thousands of tokens navigating fragmented .gov sites, following redirects, parsing malformed HTML, and hoping the content is still current.

without govlaws.ai
# agent searching for 42 CFR 482.12
> searching regulations.gov...
↳ timeout after 8.2s — retry 1/3
↳ following 4 redirects...
↳ gov.hhs.gov → ecfr.gov → ...
↳ parsing unstructured HTML (847 nodes)
↳ content freshness: unknown
ERROR: 429 Too Many Requests
ERROR: no provenance metadata
ERROR: last source update: 2023-04-12
tokens consumed: 18,432
data confidence: unknown
time elapsed: 31.4s
with govlaws.ai
# same query via API
$ curl "https://www.govlaws.ai/api/resolve?citation=42+CFR+482.12" \
-H "Authorization: Bearer glaw_sk_..."
< HTTP/2 200 OK
< X-RateLimit-Remaining: 4999
{
"citation": "42 CFR 482.12",
"text": "There must be an effective...",
"provenance": {"source": "ecfr", "is_official_edition": false}
}
tokens consumed: 1
data confidence: verified
time elapsed: 143ms
> HOW IT WORKS

From zero to first call in 60 seconds.

01Get an API key

No sign-up form. No email verification. No sales call. POST to /api/signup, verify a payment method via Stripe, then poll for your key.

step 01 — auth
$ curl -X POST www.govlaws.ai/api/signup \
-d '{"email":"agent@co.ai"}'
{ "checkout_url": "https://checkout.stripe.com/..." }
02Resolve a citation

Pass any CFR citation — get current regulatory text, provenance metadata, and recent changes. Updated every 4 hours from eCFR.

step 02 — resolve
$ curl "www.govlaws.ai/api/resolve?citation=12+CFR+1026.43" \
-H "Authorization: Bearer glaw_sk_..."
{ "citation": "12 CFR 1026.43", "text": "..." }
03Search regulations

Natural language semantic search across all federal regulations. Ask a question, get ranked results with citations and snippets.

step 03 — search
$ curl -X POST www.govlaws.ai/api/search \
-d '{"query":"mortgage underwriting"}'
{ "results": [...] }
> FEATURES

Built for agents, not humans.

> API-FIRST
Every feature is an endpoint
No dashboard required. Sign up, query, and track usage — all via API. If it can't be automated, it doesn't exist here.
> SEMANTIC SEARCH
Natural language queries
Ask questions in plain English. Vector search over all federal regulations returns ranked results with citations, scores, and snippets.
> ZERO-FRICTION ONBOARDING
Two access lanes, same data plane
Use /api/signup when you want recurring API-key access, budgets, and account management. Use /api/mpp/* when you want agent-native pay-per-request over Tempo with no account ceremony.
> PROVENANCE
Every response is traceable
Every call returns a provenance object: canonical citation, upstream source URL, official artifact URL, freshness timestamp, and whether it's from an official legal edition.
> CHANGE DETECTION
Know when regulations change
Track Federal Register changes by agency or citation. New rules, proposed rules, and amendments — updated every 4 hours from the official Federal Register API.
> ALWAYS CURRENT
Updated every 4 hours
Automated ingestion from eCFR and Federal Register runs on a 4-hour cycle. Every response includes a freshness timestamp so agents know exactly how current the data is.
> PRICING

Simple, usage-based pricing.
Start free. Scale when you need to.

Every plan includes full API access, provenance metadata, and semantic search. Pick the volume that fits.

FREE
Free
10 req / month
✓Full API access
✓Citation resolve + search
✓Change detection
✓Provenance on all responses
get started →
DEVELOPERPOPULAR
$49/month
5,000 req / month
✓Everything in Free
✓Semantic search
✓Priority data freshness
✓Email support
subscribe →
PRO
$499/month
100,000 req / month
✓Everything in Developer
✓Higher rate limits
✓Priority support
✓Usage analytics
subscribe →
ENTERPRISE
Custom
Volume pricing
✓Everything in Pro
✓Pay-as-you-go billing
✓Volume discounts
✓Dedicated support
contact us →

All plans include full API access, provenance metadata, and semantic search. Rate limit headers returned on every response.

Prefer not to manage an account? GovLaws also supports agent-native MPP pay-per-request access for resolve, search, and changes. See /mpp.

> FAQ

Direct answers for crawlers, operators, and agent builders.

These are the questions we expect retrievers and human evaluators to check before they cite or integrate GovLaws.

What does GovLaws provide for AI agents?

GovLaws gives AI agents structured access to current U.S. federal regulation data, semantic search, change feeds, provenance metadata, and agent-friendly billing options.

Does GovLaws use official government sources?

GovLaws anchors every response to official government sources such as eCFR, Federal Register, and GovInfo when available, and it distinguishes current text from official-edition status.

Can agents use GovLaws without a human signup flow?

Yes. Agents can use GovLaws over the Machine Payments Protocol for pay-per-request access, or they can use API keys for recurring usage and account controls.

What metadata does GovLaws return with legal answers?

Responses include citations, source URLs, freshness timestamps, recent changes, and provenance fields so agents can reason about trust and recency.

Machine-readable discovery lives at /llms.txt, integration docs live at /api/openapi.json, and plan details live at /pricing.