# HALOWERK laufwerk — Tour Tools Readiness Check

> HALOWERK laufwerk — Tour Tools 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-11).

Checks whether a fleet of vehicles has the tools required to service a set of jobs within their time windows, given a travel-time duration matrix.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/tours/tools-readiness?utm_source=zero.xyz
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-laufwerk-tour-tools-readiness-check-85cdf810
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TD9GZi56LLfxnuJOJu4qR

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-tools-readiness-check-85cdf810 -d '<json body>'
```

Example prompt: Before I run the route optimizer, check if my 3 vehicles are actually equipped with the right tools for all 10 service jobs — here are the job requirements, vehicle tool lists, and the travel-time matrix between all locations.

## When to prefer this

Use this endpoint as a pre-flight check before running a full vehicle routing or tour optimization to ensure tool requirements are satisfiable — saving compute cost and avoiding infeasible routes. Prefer this when jobs have specialized tool requirements and not all vehicles carry identical equipment, especially in field service, utilities, or specialized delivery contexts.

## Known failure modes

- Missing required fields (id, point, demand, service_s, window, required_tools) returns validation error
- Duration matrix dimensions don't match number of jobs+vehicles — likely returns error or null travel times
- Exceeding max jobs (20) or vehicles (4) triggers schema validation failure
- Null entries in durations_s matrix may cause incomplete feasibility results
- Malformed time windows (not exactly 2 elements) rejected by schema
- Tool set format mismatch between jobs and vehicles may yield unexpected results

## How this service works

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

## Output

A JSON response indicating which jobs can be serviced by available vehicles based on tool compatibility, time windows, and capacity — effectively a feasibility/readiness report flagging any mismatches between required job tools and vehicle inventories before route optimization is run.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "jobs": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "point",
     "demand",
     "service_s",
     "window",
     "required_tools"
    ],
    "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
     },
     "required_tools": {
      "$ref": "#/$defs/m449da1d025"
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20,
   "minItems": 1
  },
  "vehicles": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "capacity",
     "shift",
     "tools"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "shift": {
      "type": "array",
      "items": {
       "type": "number",
       "maximum": 604800,
       "minimum": 0
      },
      "maxItems": 2,
      "minItems": 2
     },
     "tools": {
      "$ref": "#/$defs/m449da1d025"
     },
     "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-tour-tools-readiness-check-85cdf810/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)