# HALOWERK laufwerk — Tour Volume Readiness Check

> HALOWERK laufwerk — Tour Volume Readiness Check 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-11).

Checks whether a set of vehicles (by weight capacity and volume) can feasibly handle a given set of delivery jobs within their time windows, using a provided travel-duration matrix.

## Facts

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

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-tour-volume-readiness-check-1c30d728 -d '<json body>'
```

Example prompt: I have 2 delivery vans — van A can carry 500 kg and 8000 L, van B can carry 400 kg and 6000 L, both working 8am–6pm — and 5 jobs with volumes between 200 and 1500 L and time windows spread across the day. Can you check whether the fleet is realistically able to handle all these deliveries by volume and capacity using this travel-time matrix?

## When to prefer this

Use this endpoint when you need a fast feasibility pre-check for a vehicle routing problem before investing in full optimization — specifically when volume (liters) and weight capacity constraints are both relevant. It is ideal for logistics agents that need to quickly validate whether a fleet configuration can physically serve a job list before committing to a more expensive planning step. Prefer it over full VRP solvers when you only need a go/no-go readiness signal rather than actual route sequences.

## Known failure modes

- Invalid or mismatched durations_s matrix dimensions relative to number of jobs and vehicles
- Job or vehicle ID exceeds maxLength of 80 characters
- demand or volume_l values exceed allowed maxima
- window or shift arrays with incorrect number of elements
- Too many jobs (>20) or vehicles (>4) submitted
- Null entries in the duration matrix causing incomplete route coverage
- Service time or window values exceeding 604800 seconds (one week)
- Payment failure via x402 resulting in 402 response

## How this service works

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

## Output

A JSON response indicating whether the given set of vehicles is feasibly able to serve all provided jobs within the stated time windows, weight capacities, and volume limits — likely including per-vehicle or aggregate feasibility indicators, potential conflicts, and readiness status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "jobs": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "point",
     "demand",
     "service_s",
     "window",
     "volume_l"
    ],
    "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
     },
     "volume_l": {
      "type": "number",
      "maximum": 10000000,
      "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",
     "volume_l"
    ],
    "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
     },
     "volume_l": {
      "type": "number",
      "maximum": 10000000,
      "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-tour-volume-readiness-check-1c30d728/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)