# us-cm-kg.ai Public Record Lookup

> us-cm-kg.ai Public Record Lookup is a paid API for AI agents from us-cm-kg.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-10).

Returns the public record for a surface node (market node, product, or estate block) on us-cm-kg.ai with an EdDSA-signed receipt, accessed via a $0.01 USDC x402 micropayment.

## Facts

- Endpoint: GET https://us-cm-kg.ai/api?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/us-cm-kg-ai-public-record-lookup-12f54176
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_c9_HfRBOtPXiruYxs8yS2

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability us-cm-kg-ai-public-record-lookup-12f54176
```

Example prompt: Fetch the public record for the us-cm-kg.ai market node and give me the EdDSA-signed receipt I can use to verify it permanently.

## When to prefer this

Choose this endpoint when you need a tamper-evident, cryptographically signed public record for a specific market node, product, or estate block on us-cm-kg.ai, and require a permanent receipt URL as proof. Prefer this over generic data lookups when auditability and EdDSA verification are required, and when the caller can handle x402 micropayment flows ($0.01 USDC per call).

## Known failure modes

- Payment not received or insufficient USDC balance — x402 payment required before record is returned
- Invalid or unsupported HTTP method — only GET, HEAD, DELETE are accepted
- Node or surface not found — returns empty or error if the requested record does not exist
- Receipt nonce resolution failure — permanent URL may be temporarily unavailable
- Malformed input object — missing required 'type' or 'method' fields causes validation error

## How this service works

One paid call on us-cm-kg.ai for $0.01 USDC: the surface's own statement of record (a market node: its list_nodes line; a product: its record of record; allooloo.io: the estate scale block), public-record only, with an EdDSA-signed receipt that resolves forever at https://us-cm-kg.ai/x402/receipt/{nonce}. Doctrine: https://agentic-x402.ai/.

## Output

A public record object for the requested surface (market node list_nodes entry, product record, or estate scale block), accompanied by an EdDSA-signed receipt whose nonce resolves permanently at https://us-cm-kg.ai/x402/receipt/{nonce}.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/us-cm-kg-ai-public-record-lookup-12f54176/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from us-cm-kg.ai](https://www.zero.xyz/host/us-cm-kg.ai/llms.txt)