# Halowerk Job State Reachability Detector

> Halowerk Job State Reachability Detector is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-19).

Analyzes an asynchronous job's state machine to detect unreachable terminal states and outgoing transitions from declared final states

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/events/job-state-reachability?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-job-state-reachability-detector-57cff52a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DX6K9kZyV1pUweKvJjlWU

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-job-state-reachability-detector-57cff52a -d '<json body>'
```

Example prompt: Check my async job state machine for reachability issues — the initial state is 'queued', terminal states are ['done', 'failed', 'cancelled'], and the transitions are [['queued','running'],['running','done'],['running','failed']] — I need to know if any terminal states are unreachable or if any have outgoing transitions.

## When to prefer this

Use this endpoint when you need to formally verify that an async job or workflow state machine is well-formed — specifically to detect unreachable terminal states and illegal outgoing transitions from final states. Prefer this over generic graph analysis tools when your domain is job orchestration or pipeline state machines and you need targeted reachability evidence rather than general graph metrics.

## Known failure modes

- Missing required fields (initial, terminal, or transitions) returns a validation error
- Malformed transition arrays (non-string elements or exceeding maxItems) return schema errors
- Empty transitions array may yield all terminal states as unreachable
- Self-referencing terminal states with transitions flagged correctly but may produce unexpected results
- Payment failure returns 402 requiring x402 protocol compliance

## How this service works

An agent that implements asynchronous jobs needs evidence of unreachable terminal states and outgoing transitions from declared final states.

## Output

Returns evidence of structural defects in the job state machine: which declared terminal states are unreachable from the initial state given the provided transitions, and which terminal states have outgoing transitions (making them non-final in practice).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "artifact": {
   "type": "object",
   "required": [
    "initial",
    "terminal",
    "transitions"
   ],
   "properties": {
    "initial": {
     "type": "string",
     "maxLength": 16384
    },
    "terminal": {
     "type": "array",
     "items": {
      "type": "string",
      "maxLength": 16384
     },
     "maxItems": 2048
    },
    "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-job-state-reachability-detector-57cff52a/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)