# Halowerk Freeze Event Monitor

> Halowerk Freeze Event Monitor 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-21).

Analyzes caller-supplied evidence signals to classify freeze events for a blockchain address, asset, or protocol subject, returning a confidence-scored assessment with explicit thresholds and missing-signal disclosure.

## Facts

- Endpoint: POST https://stable.halowerk.com/v1/freeze-event-monitor?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-freeze-event-monitor-508faabc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yOSbuFlzu5ZrkBrwweAS7

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-freeze-event-monitor-508faabc -d '<json body>'
```

Example prompt: Can you run a freeze event risk assessment on the address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 using these three signals I have: freeze_event_count of 2 observed yesterday, frozen_supply_pct at 0.15, and authority_change_risk at 0.8 — and tell me the confidence level and any missing metrics?

## When to prefer this

Choose this endpoint when you have caller-supplied evidence signals about freeze events and need a structured, threshold-transparent classification without querying a blockchain node directly. It is ideal when you already have aggregated metrics (frozen supply %, event count, authority change risk) and need a reproducible, auditable risk verdict. Prefer it over raw chain queries when you want explicit disclosure of missing signals and confidence degradation. Not suitable when you need live on-chain data retrieval, legal compliance opinions, or independent audit conclusions.

## Known failure modes

- Missing required 'evidence' array or fewer than 1 item returns a validation error
- Setting 'strict: true' without all documented metrics (freeze_event_count, frozen_supply_pct, authority_change_risk) causes rejection
- Invalid metric enum values return a schema validation error
- Evidence timestamps in non-ISO-8601 format are rejected
- More than 50 evidence items triggers a max-items validation error
- Subject string exceeding 256 characters is rejected
- Payment not included or insufficient USDC causes x402 payment-required response

## How this service works

Freeze Event Monitor 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 freeze event classification with a confidence score, the exact thresholds applied to reach the verdict, a list of any missing or incomplete signals that would have improved confidence, and an echo of any caller-supplied context labels for correlation.

## 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": [
       "freeze_event_count",
       "frozen_supply_pct",
       "authority_change_risk"
      ],
      "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-freeze-event-monitor-508faabc/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)