# Halowerk Offline Event Workflow Validator

> Halowerk Offline Event Workflow Validator is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-19).

Validates an offline event workflow artifact by checking state reachability, retry-window bounds, replay timing, correlation lineage, and sequence continuity in a single submission.

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/events/profile?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-offline-event-workflow-validator-bd58db12
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dcEB5nJrUxErkmIP9xgeg

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-offline-event-workflow-validator-bd58db12 -d '<json body>'
```

Example prompt: Can you profile this event workflow artifact and check whether all states are reachable, the retry policy with 5 attempts, 200ms base, factor 2, 30000ms max interval, and 86400000ms retention is within bounds, replay timing is correct, and event correlation lineage and sequence continuity are intact — the current time is now_ms 1720000000000, the window is 60000ms, with events starting at sequence position 1 and ending at 50?

## When to prefer this

Choose this endpoint when you need a single-call, comprehensive correctness check of an offline event workflow artifact — particularly when you need simultaneous coverage of state reachability, retry policy compliance, replay timing, correlation lineage, and sequence continuity rather than checking these properties individually with separate tools.

## Known failure modes

- Missing required artifact fields (initial, terminal, transitions, policy, now_ms, window_ms, events, first, last, sequence) returns a validation error
- Events array exceeding 2048 items or sequence array exceeding 2048 items is rejected
- Invalid retry policy parameters (non-numeric attempts, base_ms, factor, max_interval_ms, retention_ms) cause schema rejection
- Malformed parent-child event references (non-null parent IDs that don't match any event ID) may produce lineage errors
- Payment not included or insufficient USDC triggers x402 payment required response

## How this service works

An agent that validates an offline event workflow needs state reachability, retry-window bounds, replay timing, correlation lineage and sequence continuity in one supplied artifact.

## Output

A structured validation profile report covering: state reachability analysis (whether all states are reachable from the initial state), retry-window bound compliance, replay timing correctness, correlation lineage integrity across parent-child event links, and sequence continuity gaps — surfacing any violations or anomalies found in the submitted artifact.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "artifact": {
   "type": "object",
   "required": [
    "initial",
    "terminal",
    "transitions",
    "policy",
    "now_ms",
    "window_ms",
    "events",
    "first",
    "last",
    "sequence"
   ],
   "properties": {
    "last": {
     "type": "number"
    },
    "first": {
     "type": "number"
    },
    "events": {
     "type": "array",
     "items": {
      "type": "object",
      "required": [
       "id",
       "signed_ms",
       "parent",
       "correlation"
      ],
      "properties": {
       "id": {
        "type": "string",
        "maxLength": 16384
       },
       "parent": {
        "type": [
         "string",
         "null"
        ]
       },
       "signed_ms": {
        "type": "number"
       },
       "correlation": {
        "type": "string",
        "maxLength": 16384
       }
      },
      "additionalProperties": true
     },
     "maxItems": 2048
    },
    "now_ms": {
     "type": "number"
    },
    "policy": {
     "type": "object",
     "required": [
      "attempts",
      "base_ms",
      "factor",
      "max_interval_ms",
      "retention_ms"
     ],
     "properties": {
      "factor": {
       "type": "number"
      },
      "base_ms": {
       "type": "number"
      },
      "attempts": {
       "type": "number"
      },
      "retention_ms": {
       "type": "number"
      },
      "max_interval_ms": {
       "type": "number"
      }
     },
     "additionalProperties": true
    },
    "initial": {
     "type": "string",
     "maxLength": 16384
    },
    "sequence": {
     "type": "array",
     "items": {
      "type": "number"
     },
     "maxItems": 2048
    },
    "terminal": {
     "type": "array",
     "items": {
      "type": "string",
      "maxLength": 16384
     },
     "maxItems": 2048
    },
    "window_ms": {
     "type": "number"
    },
    "transitions": {
     "type": "array",
     "items": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 16384
      },
      "maxItems": 2048
     },
     "maxItems": 2048
    }
   },
   "additionalProperties": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-offline-event-workflow-validator-bd58db12/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from detect.halowerk.com](https://www.zero.xyz/host/detect.halowerk.com/llms.txt)