home
> GOVLAWS DEVELOPER PORTAL

Integrate source-backed U.S. legal data into an agent.

GovLaws exposes one shared legal-data contract through REST, remote MCP, MPP/Tempo, and x402/Base. Start with the free account lane for evaluation, or use a machine-payment lane when an autonomous agent should pay in-band without a signup flow. This portal is the canonical index for GovLaws developer resources.

01 / REST QUICKSTART

Create a free key with POST /api/signup, then send it as Authorization: Bearer or X-API-Key. The free plan is the live evaluation environment; GovLaws does not currently maintain a separate synthetic sandbox. Use non-sensitive test citations and the public status endpoint while validating an integration.

curl "https://govlaws.ai/api/resolve?citation=12+CFR+1026.43" \
  -H "Authorization: Bearer YOUR_API_KEY"
OPENAPI + SCHEMAS

The OpenAPI 3.1 document defines operation inputs, typed success responses, typed errors, authentication, rate-limit headers, and payment metadata.

open GovLaws OpenAPI →
REMOTE MCP

Install https://govlaws.ai/mcp in an MCP client and authenticate with a GovLaws API key. Available read-only tools are resolve, search, and changes.

read MCP setup →
MPP + X402

Call the MPP routes for Tempo pathUSD payment challenges, or the separate x402 routes for exact Base USDC payments. Invalid requests are rejected before a charge challenge.

machine-payment docs →
02 / AUTHENTICATION

Recurring-account endpoints use GovLaws API keys. Keep keys server-side, give separate workloads separate keys, and rotate them through POST /api/keys/rotate. MPP and x402 use their payment credentials instead of API keys. OAuth 2.0 is not currently offered; GovLaws will only publish authorization-server metadata after a standards-compliant issuer and client lifecycle are operational.

03 / VERSIONING + DEPRECATION

The current contract version is 2026-04-27. Flat /api/* paths remain canonical for backward compatibility, and responses expose GovLaws-API-Version. Additive fields and endpoints may ship within the current version. A breaking change receives a new contract version and at least 90 days of notice. Deprecated operations will be marked in OpenAPI and return standards-based Deprecation,Sunset, and successor Link headers during the migration window.

MACHINE-READABLE INDEX
llms.txtllms-full.txtOpenAPIstatuscollectionsfreshnesssitemap