# HALOWERK laufwerk — Driving Readiness / Vehicle Routing Feasibility

> HALOWERK laufwerk — Driving Readiness / Vehicle Routing Feasibility 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 set of delivery or service jobs can be feasibly assigned to a fleet of vehicles given time windows, capacity constraints, and a travel-time matrix

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/tours/driving-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-driving-readiness-vehicle-routing-feasibility-ae6c05d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__40pwnjBAePDA_Fk3CXNw

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-driving-readiness-vehicle-routing-feasibility-ae6c05d4 -d '<json body>'
```

Example prompt: I have 2 delivery vans (each with capacity 500 kg, working 8am–6pm) and 5 jobs with their time windows and a travel-time matrix — can you check if my fleet can realistically cover all those jobs today, with no single driver exceeding 8 hours of driving?

## When to prefer this

Choose this endpoint when you need a fast, pre-dispatch feasibility check for small fleet routing problems (up to 4 vehicles, up to 20 jobs) before committing to a full route optimization. It is ideal for validating logistics plans against time windows and driving-hour constraints without needing a full VRP solver. Use it when you already have or can compute a travel-time matrix externally.

## Known failure modes

- Invalid or missing required fields (id, point, demand, window, service_s for jobs; id, capacity, shift for vehicles) return a 422 validation error
- Duration matrix dimensions must match number of points (up to 21×21); mismatched dimensions cause errors
- More than 20 jobs or more than 4 vehicles exceeds schema limits and will be rejected
- Null values in the duration matrix for required routes may cause infeasibility or errors
- Payment not processed (x402 protocol failure) results in a 402 response
- Overlapping or impossible time windows may cause the solver to return no feasible solution

## 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 jobs can be feasibly assigned to the provided vehicles, respecting time windows, vehicle capacities, shift hours, and the maximum allowed driving time. May include assignment details, unserved jobs, or schedule feasibility indicators.

## 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_driving_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-driving-readiness-vehicle-routing-feasibility-ae6c05d4/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)