# Halowerk Cross-Chain Supply Reconciliation

> Halowerk Cross-Chain Supply Reconciliation is a paid API for AI agents from stable.halowerk.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-20).

Analyzes caller-supplied on-chain supply metrics to classify cross-chain token supply consistency, flagging mismatches and bridge gaps with explicit confidence thresholds.

## Facts

- Endpoint: POST https://stable.halowerk.com/v1/cross-chain-supply-reconciliation?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-cross-chain-supply-reconciliation-01897630
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FTynLzpWoVy42E5Te0jRZ

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 halowerk-cross-chain-supply-reconciliation-01897630 -d '<json body>'
```

Example prompt: Check cross-chain supply reconciliation for token address 0xAbC123 — I'm seeing a supply_mismatch_pct of 2.3%, 4 bridge gaps, and 1 stale chain as of 2024-06-10T12:00:00Z from my Etherscan query. Tell me how confident you are and whether any signals are missing.

## When to prefer this

Choose this endpoint when you have already gathered cross-chain supply metrics (mismatch percentages, bridge gap counts, stale chain counts) from your own data sources and need an independent, threshold-based classification with explicit confidence and missing-signal reporting. It is not a chain query tool — prefer it when you need auditable, evidence-driven reconciliation analysis rather than live on-chain data retrieval. Ideal for automated audit pipelines, compliance workflows, or agent loops that collect evidence from multiple indexers and need a structured verdict.

## Known failure modes

- Missing required 'evidence' array or empty evidence returns a 400 validation error
- strict:true rejects requests where any documented metric (supply_mismatch_pct, bridge_gap_count, stale_chain_count) is absent from the evidence
- Evidence items exceeding 50 entries are rejected
- Metric values outside expected numeric ranges may produce low-confidence classifications with explicit warnings
- Malformed ISO-8601 timestamps cause evidence item rejection
- Payment failure (x402) prevents the call from being processed

## How this service works

Cross-Chain Supply Reconciliation analyses only the evidence supplied by the caller. It does not claim to query a chain, identify a legal status or replace an independent audit. Missing signals lower confidence and are listed explicitly; every classification includes the exact thresholds used.

## Output

Returns a cross-chain supply reconciliation classification (e.g. consistent, mismatch detected, low confidence) with the exact thresholds applied, a confidence score, an explicit list of missing or absent signal types, and the correlation context labels provided by the caller. Does not query chains directly — it evaluates only the evidence submitted.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "strict": {
   "type": "boolean",
   "default": false,
   "description": "Reject unless all documented metrics are supplied."
  },
  "context": {
   "type": "object",
   "description": "Optional non-secret labels returned unchanged for correlation.",
   "maxProperties": 20,
   "additionalProperties": {
    "type": [
     "string",
     "number",
     "boolean",
     "null"
    ]
   }
  },
  "subject": {
   "type": "string",
   "maxLength": 256,
   "minLength": 1,
   "description": "Address, transaction, protocol, asset, proposal or other subject being assessed."
  },
  "evidence": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "metric",
     "value"
    ],
    "properties": {
     "note": {
      "type": "string",
      "maxLength": 500
     },
     "value": {
      "type": [
       "number",
       "boolean"
      ]
     },
     "metric": {
      "enum": [
       "supply_mismatch_pct",
       "bridge_gap_count",
       "stale_chain_count"
      ],
      "type": "string"
     },
     "source": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "Evidence source or query identifier."
     },
     "timestamp": {
      "type": "string",
      "maxLength": 40,
      "minLength": 10,
      "description": "ISO-8601 observation time."
     }
    },
    "additionalProperties": false
   },
   "maxItems": 50,
   "minItems": 1,
   "description": "Caller-supplied observations. Repeated metrics form a time series; the newest timestamp is assessed."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-cross-chain-supply-reconciliation-01897630/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stable.halowerk.com](https://www.zero.xyz/host/stable.halowerk.com/llms.txt)