Federal Register Search

government

Serving

Search Federal Register rulemaking: new and changed rules, comment windows, and docket links. POST /v1/federal with a {query} and get matching documents as one JSON object. Deterministic per document. Pay per request in USDC; no account, no API key.

Endpoint: POST https://test.agent.pocket.network/v1/federal-register
Price per call: $0.005 USD
Networks payable on: Base Sepolia (eip155:84532)
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

Derived from the published request schema.

curl -X POST https://test.agent.pocket.network/v1/federal-register \
  -H 'content-type: application/json' \
  -d '{"query":"encryption"}'

Example response

This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.

{}

Try it

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

No browser wallet found. Install MetaMask 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 Federal Register Search accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/federal`	read

Schemas

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

Request schema

{
  "type": "object",
  "description": "A search over Federal Register documents.",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search terms, e.g. encryption."
    }
  },
  "required": [
    "query"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/federal, a JSON object whose `documents` array lists matching rules with comment windows and docket links. 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."
}

Request body used in the example: { "query": "encryption" }