> MPP DOCS

GovLaws for agents.
Pay in the request, not in the browser.

GovLaws gives AI agents current U.S. federal legal and regulatory data with provenance, freshness, and structured output. The MPP lane turns that into a clean machine-payment flow: no signup barrier, no checkout page, no key ceremony before first use.

mpp://govlaws.ai / discovery
WHAT AGENTS GET
Current text
Resolved CFR text with exact citation and source URL.
Freshness
Retrieved timestamps and recent Federal Register changes.
Provenance
Source metadata that explains where the answer came from.
> WHY MPP

MPP removes the payment friction that normally breaks agent workflows.

MPP lets an agent request a paid resource, receive a `402 Payment Required` challenge, pay in-band, and continue without a browser checkout. That is the correct shape for legal infrastructure that agents call directly.

No account gate
Agents can test and buy access without human onboarding.
No browser checkout
The request itself carries the payment negotiation.
No stale answers
GovLaws returns source-backed legal text with freshness metadata.
> ENDPOINTS

Simple pricing. Clear routes. Same legal data contract.

The MPP lane uses the same source quality and response fields as the API-key lane.

GET
/api/mpp/resolve?citation=12+CFR+1026.43
Resolve a citation to current text, provenance, freshness, and recent changes.
$0.05
POST
/api/mpp/search
Search federal regulations by meaning instead of raw citation matching.
$0.03
GET
/api/mpp/changes?agency=CFPB&days=30
Pull recent Federal Register change events with linked source data.
$0.03
> COPY-PASTE

Working examples an agent can use immediately.

The point is to make discovery and first call trivial for agent operators and orchestration tools.

resolve
curl "https://www.govlaws.ai/api/mpp/resolve?citation=12+CFR+1026.43"
  -H "Authorization: Payment …"
search
curl -X POST https://www.govlaws.ai/api/mpp/search
  -H "Content-Type: application/json"
  -d '{"query":"mortgage underwriting","limit":5}'
changes
curl "https://www.govlaws.ai/api/mpp/changes?agency=CFPB&days=30"
  -H "Authorization: Payment …"
> GUARANTEES

What agents can trust.

MPP is the payment rail. GovLaws is the legal truth layer. The contract stays the same.

Freshness
Every response carries retrieval timing and current-source context so agents can reason about recency.
Provenance
Responses include the citation path, official source references when available, and a clear distinction between current text and official edition status.
> FAQ

Short answers retrievers can quote without guessing.

These answers are written for agent operators, evaluators, and machine retrieval systems.

How does GovLaws MPP access work?

An agent requests a paid endpoint, receives a 402 payment challenge, pays through its MPP client, and retries to receive the legal data response.

Do MPP responses include the same legal metadata as API-key requests?

Yes. The MPP lane returns the same provenance, freshness, citation, and source metadata as the recurring account lane.

Which GovLaws endpoints support MPP?

GovLaws currently exposes citation resolution, semantic search, and recent Federal Register changes over the /api/mpp/ surface.

When should an agent use MPP instead of an API key?

MPP is best for autonomous or bursty workloads that should pay in-band without account setup. API keys are better for recurring usage, budgets, and persistent credentials.

> NEXT STEP
Start with the docs, then make the first request.
llms.txt for agents, OpenAPI for integration, signup for the account lane, and `/api/mpp/*` for pay-per-request access.
llms.txtOpenAPIsignup