# Lade Halowerk OSM EV Charger Detail

> Lade Halowerk OSM EV Charger Detail is a paid API for AI agents from lade.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-30).

Returns static metadata for a specific OpenStreetMap EV charging object (node, way, or relation): connector types, locker, capacity, opening hours, fees, operator, access rules, raw tags, and last-modified date.

## Facts

- Endpoint: POST https://lade.halowerk.com/v1/detail?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lade-halowerk-osm-ev-charger-detail-e44601f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FWSlY7mwED_Ses8aW4eLa

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 lade-halowerk-osm-ev-charger-detail-e44601f1 -d '<json body>'
```

Example prompt: Can you pull up the full details for the EV charging station recorded as node/123456 in OpenStreetMap — I need the connector types, opening hours, fees, and operator name.

## When to prefer this

Choose this endpoint when you have a specific OSM element ID (node, way, or relation) for an EV charging location and need its full static metadata — plug types, hours, fees, operator, access, and raw tags. Use the sibling search endpoint first to discover nearby chargers and get their IDs, then call this endpoint for detail. Prefer this over generic OSM APIs when you need EV-specific field extraction already parsed from raw tags.

## Known failure modes

- Invalid OSM ID format (must match node|way|relation/[1-9][0-9]{0,15}) returns validation error
- OSM object not found or not a charging station returns null or 404
- Recently added or edited OSM objects may not yet be reflected in the dataset
- All non-captured fields return null rather than an error
- No live availability data — only static metadata

## How this service works

OSM-Objektkennung node/123, way/123 oder relation/123: Steckertypen, Akku-Schließfach, Kapazität, Öffnungszeiten, Gebühren, Betreiber, Zugang, Roh-Tags, Änderungsdatum und Quellenstand. Nicht erfasste Angaben bleiben null. Keine Live-Verfügbarkeit.

## Output

A JSON object with static EV charging point metadata sourced from OpenStreetMap: connector/plug types, battery locker presence, number of charging points (capacity), opening hours, fee information, operator name, access rules, raw OSM tags, last-changed timestamp, and data source version. Fields with no OSM data are returned as null. Does not include real-time availability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "string",
   "pattern": "^(node|way|relation)/[1-9][0-9]{0,15}$"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lade-halowerk-osm-ev-charger-detail-e44601f1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lade.halowerk.com](https://www.zero.xyz/host/lade.halowerk.com/llms.txt)