# cm-record.ai Public Record Lookup

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

Retrieves the public record entry for a given surface (market node, product, or estate-scale block) and returns an EdDSA-signed receipt permanently resolvable by nonce.

## Facts

- Endpoint: GET https://cm-record.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/cm-record-ai-public-record-lookup-b49d52b7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jbn9ifVMLG4UUcemLjt_H

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 cm-record-ai-public-record-lookup-b49d52b7
```

Example prompt: Pull the public record for the cm-record.ai market node and give me the EdDSA-signed receipt with the permanent nonce URL I can use to verify it later.

## When to prefer this

Choose this endpoint when you need a cryptographically verifiable, permanently resolvable public record for a specific surface (market node, product, or estate block) on the cm-record.ai network. It is ideal when auditability and tamper-evident proof matter — the EdDSA-signed receipt with a permanent nonce URL distinguishes it from generic data lookups. Prefer it when operating within the x402 agentic payment ecosystem and when a sub-cent cost per lookup is acceptable.

## Known failure modes

- Payment not submitted or insufficient USDC — returns 402 Payment Required
- Invalid or unsupported HTTP method (only GET, HEAD, DELETE accepted) — returns 405 Method Not Allowed
- Requested surface or record not found — returns 404 Not Found
- Network or upstream availability issue — returns 503 Service Unavailable
- Malformed input object missing required 'type' or 'method' fields — returns 400 Bad Request

## How this service works

One paid call on cm-record.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://cm-record.ai/x402/receipt/{nonce}. Doctrine: https://agentic-x402.ai/.

## Output

Returns the surface's public record entry (e.g. a market node's list_nodes line, a product's record of record, or an estate scale block entry) along with an EdDSA-signed receipt. The receipt includes a nonce that resolves permanently at https://cm-record.ai/x402/receipt/{nonce}, providing tamper-evident proof of the record at the time of the call.

## 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/cm-record-ai-public-record-lookup-b49d52b7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cm-record.ai](https://www.zero.xyz/host/cm-record.ai/llms.txt)