# HALOWERK Container Load Planner

> HALOWERK Container Load Planner is a paid API for AI agents from handel.halowerk.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-09-14).

Computes an optimal 3D bin-packing loading plan for a set of packages into a single container or loading space, returning the exact placement positions and orientations.

## Facts

- Endpoint: POST https://handel.halowerk.com/v1/container-load
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-container-load-planner-9f4ab529
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0TDfIPIygROh0-B6p554N

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-container-load-planner-9f4ab529 -d '<json body>'
```

Example prompt: I need to load these 12 packages into a container that's 2.4m wide, 2.6m tall, and 6m long — generate the exact loading plan showing where each box goes, including whether any need to be rotated 90 degrees.

## When to prefer this

Choose this endpoint when you need a deterministic, rule-based 3D bin-packing plan for a single loading space and want a guaranteed placement result rather than a probabilistic estimate. It is ideal for logistics automation workflows where reproducibility and consistency matter — the same input always produces the same output. Prefer it over heuristic or AI-based packing tools when auditability and predictability are required, or when integrating into an automated fulfillment or shipping pipeline that needs exact coordinates per package.

## Known failure modes

- Packages collectively exceed the container volume — endpoint may return an error or partial plan indicating overflow
- Invalid or missing package dimensions result in a validation error
- Container dimensions not provided or malformed cause a 400-level error
- A package with no valid surface placement (too large in all orientations) may be skipped or flagged
- Network or payment (x402) authentication failure returns a 402 or 5xx error

## How this service works

Loads a package list into one loading space and returns the plan, not an estimate. The floor starts as one free surface; packages are sorted by footprint, then height, then weight, then identifier, and each one is placed on the lowest, then frontmost, then smallest free surface it fits on, turned by 90 degrees around the vertical axis where that makes it fit.

## Output

Returns a deterministic loading plan (not an estimate) specifying for each package: its position within the loading space (x/y/z coordinates), its orientation (including any 90-degree rotation around the vertical axis), and the sequence in which packages should be placed. The plan is derived from a greedy algorithm that sorts packages by footprint, height, weight, and identifier, placing each on the lowest, then frontmost, then smallest free surface it fits on.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-container-load-planner-9f4ab529/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)