# HALOWERK laufwerk Max Stops Readiness Check

> HALOWERK laufwerk Max Stops 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 a vehicle routing problem can be feasibly solved within a maximum stops-per-vehicle constraint, given jobs, vehicles, and a travel-time duration matrix.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/tours/max-stops-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-max-stops-readiness-check-52e31114
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7OKDu_0Af42IBORrahn7J

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-max-stops-readiness-check-52e31114 -d '<json body>'
```

Example prompt: Check if my 3 delivery vehicles can handle 10 jobs with a max of 5 stops each — jobs have demand, service times, and time windows spread over an 8-hour shift, and I have a travel-time matrix between all locations.

## When to prefer this

Use this endpoint when you want a fast feasibility or readiness check on a vehicle routing problem before committing to a full optimization solve. It is ideal for pre-validation pipelines where you need to confirm that stop limits, time windows, capacities, and travel durations are mutually compatible before investing in heavier computation. Prefer this over a full VRP solver when you want to fail fast and surface constraint violations early.

## Known failure modes

- Missing required job fields (id, point, demand, service_s, window) returns validation error
- Duration matrix dimensions do not match number of points causing rejection
- Max stops per vehicle exceeds job count or vehicle count constraints
- Time windows or shift windows outside allowed range (0–604800 seconds) rejected
- More than 20 jobs or more than 4 vehicles provided exceeds schema limits
- Null values in duration matrix for required point pairs may cause computation failure

## How this service works

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

## Output

A JSON response indicating whether the given vehicle routing configuration is feasible or ready to solve under the specified maximum stops-per-vehicle constraint, potentially including flags or details about why the configuration is or isn't solvable.

## 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_stops_per_vehicle": {
   "type": "integer",
   "maximum": 20,
   "minimum": 1
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

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