# HALOWERK Return Disposition Engine

> HALOWERK Return Disposition Engine is a paid API for AI agents from handel.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-14).

Evaluates returned products against four disposition routes (resell, repair-and-resell, recover, dispose) and returns the optimal decision per return with supporting arithmetic.

## Facts

- Endpoint: POST https://handel.halowerk.com/v1/return-disposition
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-return-disposition-engine-77779631
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vMcVkCWZ8gXWvohWDnKbQ

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-return-disposition-engine-77779631 -d '<json body>'
```

Example prompt: We got 50 returns back from last week's orders — for each one I have the resale value, restocking cost, repair cost, repair success probability, refurbished value, and salvage value. Run them through the disposition engine and tell me whether to resell, repair, recover, or dispose of each item, along with the expected value calculation that drove the decision.

## When to prefer this

Choose this endpoint when you need a structured, auditable per-return disposition decision backed by explicit expected-value arithmetic across all four standard reverse logistics routes. It is especially valuable when your own systems already hold the financial figures (resale value, costs, probabilities) and you need a deterministic decision engine rather than a heuristic or rule-based script. Prefer it over general-purpose ML return classifiers when transparency of arithmetic is required for compliance or finance teams.

## Known failure modes

- Missing required financial figures (resale value, costs, probabilities) cause validation errors
- Probabilities outside 0–1 range rejected with input error
- Malformed or empty return list returns 400-level error
- Downstream timeout if very large batches exceed per-call limits
- Insufficient USDC balance causes x402 payment failure before processing

## How this service works

Takes a list of returns with the figures your own systems already hold and returns one decision per return, with the arithmetic that produced it. Four routes are valued: reselling as is, at the resale value weighted by the probability that it actually sells and less the restocking cost; repairing and reselling, at the refurbished value weighted by the repair success probability plus the salvage value on the failure branch, less the repair cost, which is incurred either way; recovering value…

## Output

One structured decision record per submitted return, indicating the recommended disposition route (resell as-is, repair-and-resell, recover value, or dispose) and the arithmetic breakdown showing the expected value computed for each of the four routes, so the caller can audit or override the recommendation.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-return-disposition-engine-77779631/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from handel.halowerk.com](https://www.zero.xyz/host/handel.halowerk.com/llms.txt)