# HALOWERK laufwerk — Pallet Readiness Check for Tour Planning

> HALOWERK laufwerk — Pallet Readiness Check for Tour Planning is a paid API for AI agents from lauf.halowerk.com, paid per call via x402, $0.007/call, status unknown (last checked 2026-10-10).

Checks whether a set of delivery jobs with pallet requirements can be feasibly served by available vehicles given their capacity, pallet slots, and time windows, using a precomputed travel-time matrix.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/tours/pallets-readiness?utm_source=zero.xyz
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-laufwerk-pallet-readiness-check-for-tour-planning-30a6d0e7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kv_dMOlqLEC64rblewkbe

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-laufwerk-pallet-readiness-check-for-tour-planning-30a6d0e7 -d '<json body>'
```

Example prompt: I have 3 vehicles — a truck with 20 pallet slots and 5000 kg capacity running a 6am–6pm shift, a van with 8 pallet slots and 2000 kg capacity running 7am–3pm, and a second van like the first — and 10 delivery jobs each needing between 1 and 5 pallets with various time windows throughout the day. Use the travel duration matrix I'll provide and check whether the pallet slots and capacities across the fleet are actually sufficient to cover all the jobs.

## When to prefer this

Choose this endpoint when you need a fast, pre-optimization feasibility check to determine whether your vehicle fleet's pallet slots and weight capacities can physically accommodate a set of delivery jobs within their time windows — before investing in a full route optimization run. It is particularly useful for logistics agents that want to catch infeasible plans early, right-size fleets, or validate planner inputs. Prefer it over a full VRP solver when you need a lightweight readiness signal rather than an optimized route assignment.

## Known failure modes

- Missing required job fields (id, point, demand, service_s, window, pallets) returns validation error
- Missing required vehicle fields (id, capacity, shift, pallet_slots) returns validation error
- Duration matrix dimensions do not match number of points — returns schema error
- More than 20 jobs or more than 4 vehicles submitted — exceeds max items limit
- Payment not made via x402 protocol results in HTTP 402 response
- Null values in duration matrix for required routes may cause computation failure
- Time window values exceeding 604800 seconds (one week) rejected

## How this service works

HALOWERK laufwerk — bezahlte Endpunkte nach x402. Preise in USDC auf Base Mainnet.

## Output

A JSON response indicating whether the set of delivery jobs can be feasibly served by the available vehicles given their pallet slot limits, weight capacities, shift windows, and travel times — likely including per-vehicle and per-job feasibility signals or a summary readiness status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "jobs": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "point",
     "demand",
     "service_s",
     "window",
     "pallets"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "point": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
     },
     "demand": {
      "type": "number",
      "maximum": 100000,
      "minimum": 0
     },
     "window": {
      "type": "array",
      "items": {
       "type": "number",
       "maximum": 604800,
       "minimum": 0
      },
      "maxItems": 2,
      "minItems": 2
     },
     "pallets": {
      "type": "integer",
      "maximum": 100000,
      "minimum": 0
     },
     "service_s": {
      "type": "number",
      "maximum": 604800,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20,
   "minItems": 1
  },
  "vehicles": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "capacity",
     "shift",
     "pallet_slots"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "shift": {
      "type": "array",
      "items": {
       "type": "number",
       "maximum": 604800,
       "minimum": 0
      },
      "maxItems": 2,
      "minItems": 2
     },
     "capacity": {
      "type": "number",
      "maximum": 100000,
      "exclusiveMinimum": 0
     },
     "pallet_slots": {
      "type": "integer",
      "maximum": 100000,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 4,
   "minItems": 1
  },
  "durations_s": {
   "type": "array",
   "items": {
    "type": "array",
    "items": {
     "anyOf": [
      {
       "type": "number",
       "maximum": 604800,
       "minimum": 0
      },
      {
       "type": "null"
      }
     ]
    },
    "maxItems": 21,
    "minItems": 2
   },
   "maxItems": 21,
   "minItems": 2
  },
  "matrix_source": {
   "type": "string",
   "maxLength": 200,
   "minLength": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-laufwerk-pallet-readiness-check-for-tour-planning-30a6d0e7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lauf.halowerk.com](https://www.zero.xyz/host/lauf.halowerk.com/llms.txt)