# Karte Halowerk Trip Metrics

> Karte Halowerk Trip Metrics is a paid API for AI agents from karte.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Analyzes a GPS trace with timestamps to compute trip distance, moving/stopped time, individual stops, mean and max speed, and optional EV energy consumption per kilometre.

## Facts

- Endpoint: POST https://karte.halowerk.com/v1/trip-metrics?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/karte-halowerk-trip-metrics-7fa38e2a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XUPULQrA92hIB4MxRd-Kt

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 karte-halowerk-trip-metrics-7fa38e2a -d '<json body>'
```

Example prompt: Analyze this GPS trace from our delivery van today — here are the 200 fixes with timestamps — and tell me the total distance covered, how long it was moving versus stopped, any stops longer than 2 minutes with their locations, and the average and top speed. The van's battery is 75 kWh, and I've included the state of charge at each point so I also want the energy used and consumption per km.

## When to prefer this

Choose this endpoint when you have a raw GPS trace (ordered lat/lon/time fixes) and need structured trip analytics — especially for fleet telematics, EV energy accounting, or delivery operations where stop detection and distance accuracy matter. It is the right choice over generic mapping APIs when you need computed metrics like idle time, stop list, and consumption per km rather than just routing or geocoding.

## Known failure modes

- Fewer than 2 GPS fixes provided — rejected with validation error
- Timestamps go backwards between consecutive fixes — rejected as invalid trace
- A segment implies speed above max_speed_kmh threshold — that segment is excluded from totals
- Missing required lat/lon/time fields on any fix — validation error
- Battery capacity not supplied — energy reported in SoC percent only, not kWh
- More than 5000 fixes submitted — rejected by maxItems constraint

## How this service works

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

## Output

Returns a structured summary including total distance in km, elapsed and moving duration in seconds, stopped duration, a list of stops each with lat/lon, start time, and duration, mean and maximum speed in km/h, and (when SoC data and battery capacity are provided) total energy consumed in kWh and efficiency in kWh/km or percent/km.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "points": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "lat",
     "lon",
     "time"
    ],
    "properties": {
     "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude, WGS 84."
     },
     "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude, WGS 84."
     },
     "time": {
      "type": "string",
      "maxLength": 40,
      "minLength": 4,
      "description": "ISO 8601 timestamp of the fix. Must not go backwards from one fix to the next."
     },
     "soc_percent": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Battery state of charge at this fix, in percent. Optional, and may be present on only some fixes."
     }
    },
    "additionalProperties": false
   },
   "maxItems": 5000,
   "minItems": 2,
   "description": "The trace, in chronological order. At least two fixes."
  },
  "stop_min_s": {
   "type": "integer",
   "default": 120,
   "maximum": 86400,
   "minimum": 10,
   "description": "Minimum duration of standing time before it is reported as a stop."
  },
  "max_speed_kmh": {
   "type": "number",
   "default": 250,
   "maximum": 400,
   "minimum": 1,
   "description": "Plausibility limit. A segment implying more than this is rejected instead of summed."
  },
  "stop_speed_kmh": {
   "type": "number",
   "default": 2,
   "maximum": 30,
   "minimum": 0,
   "description": "At or below this speed a segment counts as standing."
  },
  "battery_capacity_kwh": {
   "type": "number",
   "maximum": 1000,
   "minimum": 0.1,
   "description": "Usable battery capacity. Without it, energy is reported in percent of charge only, never in kWh."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/karte-halowerk-trip-metrics-7fa38e2a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from karte.halowerk.com](https://www.zero.xyz/host/karte.halowerk.com/llms.txt)