MPPtempoquality 0.92

Recent U.S

Recent U.S. Federal Register change events via pay-per-request MPP, filtered by agency, citation, or lookback window.

Price
$0.03 / call
Protocol
mpp
Verified
no

What it does

The GovLaws `/api/mpp/changes` endpoint returns recent regulatory change events from the U.S. Federal Register. Agents can filter results by agency name, CFR citation prefix, or a lookback window of 1–90 days (default 30). Each change event includes the citation, change type (amendment, final_rule, proposed_rule, correction), effective date, detecting timestamp, agency, Federal Register document number, URL, summary, and a full provenance object with trust signals and citation-suitability metadata. The endpoint requires no API key; payment is handled via the Machine Payments Protocol (MPP) using Tempo stablecoin on chain 4217.

Pricing is $0.03 per request (30,000 base units of pathUSD with 6 decimals). On the first unauthenticated call the endpoint returns HTTP 402 with a `WWW-Authenticate: Payment` header containing a Tempo challenge. The agent pays the challenge amount and replays the request with the resulting credential to receive the data. Provenance fields on every response distinguish official Federal Register notices (suitable for legal filings) from unofficial eCFR-derived text (suitable for research and reference only). Data is refreshed on a 4-hour cycle from the official Federal Register API.

GovLaws also offers equivalent API-key-authenticated access at `/api/changes` under subscription plans (Free 10 req/mo, Developer $49/mo for 5,000 req, Pro $499/mo for 100,000 req). The MPP lane is designed for autonomous agents that prefer stateless pay-per-call without account management.

Capabilities

federal-register-changesagency-filtercitation-prefix-filterlookback-windowprovenance-metadatatrust-signalschange-type-classificationmpp-pay-per-requesttempo-stablecoin-settlementcfr-change-detection

Use cases

  • Compliance agents monitoring specific agencies or CFR titles for new final rules and amendments
  • Legal research assistants surfacing recent regulatory changes relevant to a client matter
  • Autonomous policy-tracking bots that pay per call without managing API keys
  • Risk management systems detecting proposed rules that may affect regulated entities
  • News or briefing agents summarizing recent federal rulemaking activity

Fit

Best for

  • AI agents needing structured, provenance-rich federal regulatory change data
  • Stateless autonomous agents that prefer pay-per-request over subscription accounts
  • Compliance workflows that need to filter changes by agency or citation prefix

Not for

  • State or local regulation tracking (federal only)
  • Full-text retrieval of regulation sections (use the resolve endpoint instead)
  • High-volume batch ingestion where subscription pricing is more economical

Quick start

# 1. Send unauthenticated GET — receive 402 challenge
curl -i "https://govlaws.ai/api/mpp/changes?agency=CFPB&days=30"
# HTTP/2 402  WWW-Authenticate: Payment method=tempo ...

# 2. Pay the Tempo challenge, then replay with credential
curl "https://govlaws.ai/api/mpp/changes?agency=CFPB&days=30" \
  -H "Authorization: Payment <credential>"

Example

Request

{
  "url": "https://govlaws.ai/api/mpp/changes?agency=CFPB&citation=12+CFR+1026&days=30",
  "method": "GET"
}

Response

{
  "total": 1,
  "period": {
    "to": "2026-03-19",
    "from": "2026-02-17"
  },
  "changes": [
    {
      "url": "https://www.federalregister.gov/documents/2026-04567",
      "title": "Ability to Repay",
      "agency": "Consumer Financial Protection Bureau",
      "source": "Federal Register",
      "citation": "12 CFR 1026.43",
      "provenance": {
        "trust": {
          "disclaimer_code": "FR_NOTICE",
          "citation_suitability": [
            "research",
            "reference",
            "legal_filing"
          ]
        },
        "currency": {
          "as_of": "2026-03-19T12:00:00Z",
          "effective_date": "2026-02-28",
          "reflects_current_text": false
        },
        "source_system": "federal_register",
        "is_official_edition": true,
        "official_artifact_url": "https://www.federalregister.gov/documents/2026-04567"
      },
      "change_type": "final_rule",
      "detected_at": "2026-03-19T12:00:00Z",
      "effective_date": "2026-02-28",
      "document_number": "2026-04567"
    }
  ]
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.92/ 1.00

Full OpenAPI 3.1 schema with detailed component definitions, example responses, provenance model, and clear pricing. Live 402 MPP challenge was captured and matches the documented payment info. The only gap is the absence of a dedicated docs page (404 at /docs), but the OpenAPI spec and homepage content are comprehensive.

Warnings

  • The /docs page returns 404; all documentation is derived from the OpenAPI spec and homepage.
  • Provenance metadata distinguishes unofficial eCFR text from official Federal Register notices — agents should check trust.citation_suitability before citing in legal filings.

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 15:46:46Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access