# HALOWERK laufwerk — Tour Capacity Reserve Readiness

> HALOWERK laufwerk — Tour Capacity Reserve Readiness 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 fleet of vehicles has sufficient capacity reserve to feasibly serve all jobs within their time windows, given a travel-time duration matrix.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/tours/capacity-reserve-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-tour-capacity-reserve-readiness-6326adce
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JRLxHtWRl3_UEP2vNbt1u

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-capacity-reserve-readiness-6326adce -d '<json body>'
```

Example prompt: Check if my 3 delivery vans can handle all 10 scheduled stops today given their shift hours and delivery demands — I need at least a 200-unit capacity reserve across the fleet, and here's the travel time matrix between all locations.

## When to prefer this

Use this endpoint when you need a fast, pre-routing feasibility check specifically focused on capacity reserve thresholds — before running a full vehicle routing optimization. It is ideal for small fleets (up to 4 vehicles) and up to 20 job stops when you want to quickly determine whether dispatching is viable without the overhead of a full VRP solver. Prefer this over a full route optimizer when the primary concern is whether vehicle capacity buffers are adequate, not the actual route sequence.

## Known failure modes

- Missing required fields (jobs, vehicles, durations_s, minimum_capacity_reserve) returns validation error
- Duration matrix dimensions do not match number of jobs + vehicles, causing a schema or computation error
- Job demand or vehicle capacity values exceed allowed maxima (100,000), rejected
- Time window arrays with incorrect length (must be exactly 2 elements) fail validation
- More than 20 jobs or more than 4 vehicles submitted, exceeding array limits
- Payment failure via x402 protocol results in HTTP 402 before computation
- Null values in duration matrix may cause computation issues depending on routing logic

## How this service works

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

## Output

A JSON response indicating whether the fleet's aggregate or per-vehicle capacity reserve meets the specified minimum threshold given the jobs, their demands and time windows, and the travel duration matrix. Likely includes a readiness flag, computed reserve values, and potentially per-vehicle or per-job breakdown details.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "jobs": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "point",
     "demand",
     "service_s",
     "window"
    ],
    "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
     },
     "service_s": {
      "type": "number",
      "maximum": 604800,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20,
   "minItems": 1
  },
  "vehicles": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "capacity",
     "shift"
    ],
    "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
     }
    },
    "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
  },
  "minimum_capacity_reserve": {
   "type": "number",
   "maximum": 10000000,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-laufwerk-tour-capacity-reserve-readiness-6326adce/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)