# Blockchain Money Map – Response Completeness Drift Ledger

> Blockchain Money Map – Response Completeness Drift Ledger is a paid API for AI agents from api.blockchainmoneymap.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Records, compares, and verifies API response completeness drift facts against a tamper-evident ledger, tracking schema field presence over time.

## Facts

- Endpoint: POST https://api.blockchainmoneymap.com/api/x402/x402-paid-agent-response-completeness-drift-ledger?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockchain-money-map-response-completeness-drift-ledger-57de07cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_019fGi6iZNXrGn1QeqGGO

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 blockchain-money-map-response-completeness-drift-ledger-57de07cb -d '<json body>'
```

Example prompt: Take a snapshot of the response completeness for service 'abc123-service' — it has 18 present fields out of 22 required, with missing field codes ['addr','ts','sig','meta'], schema hash sha256:aabbcc...ff, and store it in ledger 'ledger-prod-agent-001' with record ID 'rec-2024-snapshot-001'.

## When to prefer this

Choose this endpoint when you need a tamper-evident, blockchain-anchored record of API response completeness over time — specifically to detect schema drift, audit field presence against a contract, or verify that a prior snapshot has not been altered. Prefer this over simple logging when cryptographic verifiability and notarized ledger entries are required for compliance or agent service SLA tracking.

## Known failure modes

- Invalid ledger_id or record_id format returns 400 validation error
- Missing required mode field causes request rejection
- schema_hash pattern mismatch (not sha256: prefix + 64 hex chars) causes validation failure
- idempotency_key collision returns cached prior result rather than new entry
- lookup_secret mismatch returns 403 unauthorized
- Payment failure via x402 protocol returns 402 with payment requirements
- Mismatched reference_facts in compare mode returns drift conflict error
- Missing present_field_count or required_field_count in snapshot mode may cause incomplete ledger entry

## How this service works

Tracks hash-only completeness snapshots for paid-agent response contracts across releases.

## Output

Returns a JSON object containing the ledger entry result — including confirmation of the stored or compared record, drift analysis (field count deltas, missing field codes), verification verdict, and any policy evaluation outcome. In compare mode, includes a diff of present vs reference facts. In verify mode, returns whether the stored record matches the declared contract hash.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mode": {
   "enum": [
    "snapshot",
    "compare",
    "verify"
   ]
  },
  "facts": {
   "type": "object",
   "required": [],
   "properties": {
    "schema_hash": {
     "type": "string",
     "pattern": "^sha256:[a-fA-F0-9]{64}$"
    },
    "version_label": {
     "type": "string",
     "maxLength": 500
    },
    "service_id_hash": {
     "type": "string",
     "pattern": "^sha256:[a-fA-F0-9]{64}$"
    },
    "missing_field_codes": {
     "type": "array",
     "maxItems": 50
    },
    "present_field_count": {
     "type": "number"
    },
    "required_field_count": {
     "type": "number"
    },
    "response_contract_hash": {
     "type": "string",
     "pattern": "^sha256:[a-fA-F0-9]{64}$"
    }
   },
   "additionalProperties": false
  },
  "policy": {
   "type": "object",
   "additionalProperties": true
  },
  "ledger_id": {
   "type": "string",
   "pattern": "^[A-Za-z0-9_-]{12,160}$",
   "maxLength": 160,
   "minLength": 12
  },
  "notary_id": {
   "type": "string",
   "pattern": "^[A-Za-z0-9_-]{12,160}$",
   "maxLength": 160,
   "minLength": 12
  },
  "record_id": {
   "type": "string",
   "pattern": "^[A-Za-z0-9_-]{12,160}$",
   "maxLength": 160,
   "minLength": 12
  },
  "lookup_secret": {
   "type": "string",
   "pattern": "^[A-Za-z0-9_-]{43,160}$",
   "maxLength": 160,
   "minLength": 43
  },
  "idempotency_key": {
   "type": "string",
   "pattern": "^[A-Za-z0-9_-]{32,160}$",
   "maxLength": 160,
   "minLength": 32
  },
  "reference_facts": {
   "type": "object",
   "required": [],
   "properties": {
    "schema_hash": {
     "type": "string",
     "pattern": "^sha256:[a-fA-F0-9]{64}$"
    },
    "version_label": {
     "type": "string",
     "maxLength": 500
    },
    "service_id_hash": {
     "type": "string",
     "pattern": "^sha256:[a-fA-F0-9]{64}$"
    },
    "missing_field_codes": {
     "type": "array",
     "maxItems": 50
    },
    "present_field_count": {
     "type": "number"
    },
    "required_field_count": {
     "type": "number"
    },
    "response_contract_hash": {
     "type": "string",
     "pattern": "^sha256:[a-fA-F0-9]{64}$"
    }
   },
   "additionalProperties": false
  },
  "retention_class": {
   "enum": [
    "short",
    "standard",
    "support"
   ],
   "type": "string"
  },
  "idempotency_scope_token": {
   "type": "string",
   "pattern": "^[A-Za-z0-9_-]{43,160}$",
   "maxLength": 160,
   "minLength": 43
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockchain-money-map-response-completeness-drift-ledger-57de07cb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockchainmoneymap.com](https://www.zero.xyz/host/api.blockchainmoneymap.com/llms.txt)