US Code and CFR Regulations

government

Serving

US Code and CFR section lookup plus legislative bill tracking from govinfo. POST /v1/us with a {title} (and optional section) and get the regulation text and structure as one JSON object. Deterministic per compilation. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/us-code-cfr/v1/us
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/us-code-cfr/v1/us \
  -H 'content-type: application/json' \
  -d '{"title":1}'

Example response

The response this call returned, captured 2026-09-21 23:50:00 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "us-code-cfr",
    "schemaCheck": "unchecked"
  },
  "data": {
    "title": {
      "number": 1,
      "name": "General Provisions",
      "latest_amended_on": "2022-12-29",
      "latest_issue_date": "2026-08-10",
      "up_to_date_as_of": "2026-09-18",
      "reserved": false
    },
    "as_of": "2026-09-21",
    "note": "section-level text: /api/versioner/v1/full/<date>/title-N.xml",
    "source": "ecfr.gov API (public domain)"
  }
}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods US Code and CFR Regulations accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/us`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "A US Code or CFR title (and optional section) to fetch.",
  "properties": {
    "title": {
      "type": "integer",
      "description": "Title number, e.g. 1."
    },
    "section": {
      "type": "string",
      "description": "Optional section within the title."
    }
  },
  "required": [
    "title"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/us, a JSON object with the title structure and section text. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}