Entity Registration and Verification

government

Serving

Verify SAM.gov entity registrations: UEI, legal name, registration status, and expiration. POST /v1/entity with a {name} (or UEI) and get the matching records as one JSON object. Deterministic per record. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/entity-registration/v1/entity
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/entity-registration/v1/entity \
  -H 'content-type: application/json' \
  -d '{"name":"boeing"}'

Example response

The response this call returned, captured 2026-09-21 23:47:06 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "entity-registration",
    "schemaCheck": "unchecked"
  },
  "data": {
    "name": "boeing",
    "uei": "",
    "exclusions": [],
    "has_exclusions": false,
    "coverage_note": "Registration records (status, UEI activation, expiration) require the gated api.sam.gov entity endpoint (api_key). This v1 returns public exclusion data + honest coverage note.",
    "as_of": "2026-09-21",
    "source": "sam.gov search API (public index)"
  }
}

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 Entity Registration and Verification accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/entity`	read

Schemas

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

Request schema

{
  "type": "object",
  "description": "An entity to verify.",
  "properties": {
    "name": {
      "type": "string",
      "description": "Legal or DBA name to verify, e.g. Boeing."
    },
    "uei": {
      "type": "string",
      "description": "Optional UEI."
    }
  },
  "required": [
    "name"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/entity, a JSON object with the matching entity records (UEI, legal name, status, expiration). 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."
}