# HALOWERK laufwerk — Breaks Readiness Check

> HALOWERK laufwerk — Breaks 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-10).

Checks whether vehicle break schedules are feasible and compatible with a given set of delivery jobs, time windows, and a travel-duration matrix for route optimization.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/tours/breaks-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-breaks-readiness-check-72c36112
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yfM7AugFA35DqXvJbO8dB

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-breaks-readiness-check-72c36112 -d '<json body>'
```

Example prompt: Check whether our driver break windows are feasible for today's delivery schedule: we have 2 vehicles (capacity 500 each) with shifts from 0 to 28800 seconds, each with a mandatory break between 14400–16200 seconds, and 5 jobs with demand ranging from 10 to 80, service times of 300 seconds each, and time windows between 0–28800. Use the provided 7x7 travel duration matrix.

## When to prefer this

Use this endpoint when you need a lightweight feasibility pre-check specifically for vehicle break scheduling before committing to a full vehicle routing optimization run. It is ideal for fleet operators who need to validate driver rest compliance, detect scheduling conflicts early, or dynamically re-check feasibility after a break window changes — without running an expensive full optimization. Prefer this over a full VRP solver when you only need a yes/no readiness signal about break compatibility.

## Known failure modes

- Invalid or mismatched matrix dimensions relative to number of points — returns validation error
- Break window outside vehicle shift bounds — returns constraint violation
- Job time window impossible to satisfy given service duration — returns infeasibility
- More than 20 jobs or 4 vehicles submitted — returns schema validation error
- Null entries in duration matrix for required routes — may return infeasibility or error
- Missing required job or vehicle fields — returns 400 bad request

## How this service works

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

## Output

Returns a JSON object indicating whether the configured vehicle break windows are feasible (ready) given the jobs, time windows, service durations, vehicle capacities, and travel duration matrix — likely including per-vehicle or per-job feasibility flags and any conflict 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",
     "breaks"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "shift": {
      "type": "array",
      "items": {
       "type": "number",
       "maximum": 604800,
       "minimum": 0
      },
      "maxItems": 2,
      "minItems": 2
     },
     "breaks": {
      "type": "array",
      "items": {
       "type": "array",
       "items": {
        "type": "number",
        "maximum": 604800,
        "minimum": 0
       },
       "maxItems": 2,
       "minItems": 2
      },
      "maxItems": 10,
      "minItems": 1
     },
     "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
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-laufwerk-breaks-readiness-check-72c36112/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)