# dep.halowerk.com Registry Health Summarizer

> dep.halowerk.com Registry Health Summarizer is a paid API for AI agents from dep.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Summarizes caller-supplied registry observations and withdrawal history into a structured health report, returning null for missing facts and disclosing derivation methods for computed values.

## Facts

- Endpoint: POST https://dep.halowerk.com/v1/registry-health
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dep-halowerk-com-registry-health-summarizer-fdb3aa91
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S8xUarXp1tsATCKVcKJhF

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 dep-halowerk-com-registry-health-summarizer-fdb3aa91 -d '<json body>'
```

Example prompt: Can you summarize the health of this registry based on my last 50 observations — I have timestamps, HTTP status codes, latencies in milliseconds, and whether each check showed a withdrawal?

## When to prefer this

Use this endpoint when you have already collected raw registry probe data (status codes, latencies, withdrawal flags) and need to aggregate it into a structured health summary with transparent derivation metadata. It is purpose-built for dependency registry health assessment and pairs well with other dep.halowerk.com endpoints for a full software supply chain audit. Prefer this over generic analytics tools when you need null-safe outputs with explicit unavailable_fields reporting and disclosed computation methods.

## Known failure modes

- Empty or malformed observations array returns validation error
- Observations missing required fields (observed_at, status, latency_ms, withdrawn) cause rejection
- Status codes outside 100–599 or negative latency values fail schema validation
- Exceeding 10,000 observations may be rejected
- Payment failure or insufficient USDC balance blocks the call

## How this service works

Summarizes caller-supplied registry observations and withdrawal history. Missing facts are returned as null and named in unavailable_fields where applicable. Derived values disclose their method; source-backed values disclose source, time window and age. 

## Output

A structured health summary derived from the supplied observations, including availability statistics, latency aggregates, withdrawal counts, and derived metrics with disclosed computation methods. Missing data points are returned as null and listed in an unavailable_fields array. Source-backed values include their source, time window, and age.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "observations": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "observed_at",
     "status",
     "latency_ms",
     "withdrawn"
    ],
    "properties": {
     "status": {
      "type": "integer",
      "maximum": 599,
      "minimum": 100,
      "description": ""
     },
     "withdrawn": {
      "type": "boolean"
     },
     "latency_ms": {
      "type": "integer",
      "maximum": 1000000000000,
      "minimum": 0,
      "description": ""
     },
     "observed_at": {
      "type": "string",
      "format": "date-time"
     }
    },
    "additionalProperties": false
   },
   "maxItems": 10000,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dep-halowerk-com-registry-health-summarizer-fdb3aa91/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dep.halowerk.com](https://www.zero.xyz/host/dep.halowerk.com/llms.txt)