# HALOWERK laufwerk — Tours Waiting Readiness Optimizer

> HALOWERK laufwerk — Tours Waiting Readiness Optimizer 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 vehicle routing feasibility by computing whether jobs can be served within time windows given maximum waiting time constraints, returning readiness scores for tour planning.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/tours/waiting-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-tours-waiting-readiness-optimizer-bafe4af9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qOXmF3iLnXpVfbeZY96ST

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-tours-waiting-readiness-optimizer-bafe4af9 -d '<json body>'
```

Example prompt: Check if my 2 delivery vehicles with capacity 500 each, working shifts from hour 0 to 28800, can handle these 3 jobs — stop 1 at point 2 needing 50 units with a 2-hour service window from 3600 to 7200, stop 2 at point 5 needing 30 units from 5400 to 10800, stop 3 at point 8 needing 80 units from 7200 to 14400 — using the provided 3x3 travel-time matrix, with a max waiting time of 1800 seconds.

## When to prefer this

Use this endpoint when you need to pre-validate vehicle routing feasibility before committing to a dispatch plan, specifically to check whether waiting times between jobs remain within acceptable bounds given real travel durations. Prefer this over general VRP solvers when the primary concern is waiting-time readiness rather than optimal route generation.

## Known failure modes

- Invalid or missing required fields (id, point, demand, window, service_s) cause 400 validation error
- Duration matrix dimensions do not match number of jobs plus vehicles, causing computation failure
- Job demand exceeds vehicle capacity, resulting in infeasibility flag
- Time windows violate shift boundaries, causing constraint rejection
- Max waiting time set to 0 may make most tours infeasible
- Payment not received or insufficient USDC balance triggers 402 Payment Required

## How this service works

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

## Output

Returns a JSON object indicating whether the given set of jobs and vehicles passes waiting-readiness validation — including feasibility status, computed waiting times, and any constraint violations per job or vehicle across the tour.

## 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
  },
  "max_waiting_s": {
   "type": "number",
   "maximum": 604800,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-laufwerk-tours-waiting-readiness-optimizer-bafe4af9/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)