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 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.
GovLaws keeps Tempo as the primary MPP rail for true microtransactions. The x402 lane uses Coinbase CDP on Base USDC so agents can discover and pay through x402 Bazaar and Amazon Bedrock AgentCore Payments.
profile_61UaOKlpBFHxP0R5pA6UaOKk7KSQvQPU9rJGTEP6GNCq. Stripe pricing is 1.5% per successful machine-payment charge, rounded to the nearest cent; current $0.03-$0.15 calls stay on Tempo.The MPP and x402 lanes use the same source quality and response fields as the API-key lane.
The point is to make discovery and first call trivial for agent operators and orchestration tools.
MPP is the payment rail. GovLaws is the legal truth layer. The contract stays the same.
These answers are written for agent operators, evaluators, and machine retrieval systems.
An agent requests a paid endpoint, receives a 402 payment challenge, pays through its MPP client, and retries to receive the legal data response.
Yes. The MPP lane returns the same provenance, freshness, citation, and source metadata as the recurring account lane.
GovLaws currently exposes citation resolution, semantic search, and recent Federal Register changes over the /api/mpp/ surface.
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.