# Halowerk Async Job Runner

> Halowerk Async Job Runner is a paid API for AI agents from agent.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-16).

Runs a sequence of HTTP steps in the background and POSTs the collected results to a callback URL when all steps complete.

## Facts

- Endpoint: POST https://agent.halowerk.com/v1/job-runner
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-async-job-runner-f18e969b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9l40XUR3BTwXrVyOe1xEM

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-async-job-runner-f18e969b -d '<json body>'
```

Example prompt: Run these three HTTP calls in the background as a single job — GET https://api.example.com/users/42, GET https://api.example.com/orders?user=42, and GET https://api.example.com/preferences?user=42 — and POST all the results to https://myapp.com/webhook/results when they're done.

## When to prefer this

Choose this endpoint when you need to fire multiple independent HTTP requests without blocking your own response time, want guaranteed per-step result reporting even on partial failures, and need results delivered to a webhook rather than waited on synchronously. Prefer it over sequential in-process calls when steps are independent and latency of the full set matters, or when your runtime cannot hold a connection open long enough for all steps to complete.

## Known failure modes

- Individual steps fail but do not abort remaining steps — all results are still delivered
- Callback URL is unreachable, preventing delivery of results
- Step target URL is not publicly accessible, causing that step to fail
- Request body or step definitions are malformed, resulting in rejection at submission
- Payment of 0.003 USDC per step is not satisfied, blocking job submission
- Response body exceeds 256 KB truncation limit, delivering partial content

## How this service works

For work that outlives one HTTP response. You submit steps, each an HTTP request against a public address; the job is acknowledged at once and runs in the background, and the collected results are POSTed to your callback URL when finished. Every step reports its status, timing, response headers and body up to 256 KB, and a failing step never aborts the others. Price is 0.003 USDC per step, quoted before payment.

## Output

An immediate job acknowledgement is returned at submission time. When all steps finish, a POST is sent to the provided callback URL containing each step's status, timing, response headers, and up to 256 KB of response body — regardless of whether individual steps succeeded or failed.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-async-job-runner-f18e969b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.halowerk.com](https://www.zero.xyz/host/agent.halowerk.com/llms.txt)