# Karte Emergency Coverage

> Karte Emergency Coverage 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-13).

Returns the nearest emergency facility of each type (hospitals, defibrillators, fire stations, etc.) with distance and details, facility count within a radius, and density per km² for a given location

## Facts

- Endpoint: POST https://karte.halowerk.com/v1/emergency-coverage?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/karte-emergency-coverage-fad1978a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r04qAV5OhSsk77hOJBYuw

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-emergency-coverage-fad1978a -d '<json body>'
```

Example prompt: What emergency coverage looks like within 1 kilometre of 51.5074° N, 0.1278° W — I need the nearest hospital with an emergency department, the nearest defibrillator (only outdoor or publicly accessible ones), the nearest fire station, and how many of each are in that radius.

## When to prefer this

Choose this endpoint when you need a structured summary of emergency infrastructure around a specific point — combining nearest-facility lookup, count, and density in a single call. It is particularly valuable when the practical availability of a facility matters (e.g. hospital must have an ER, defibrillator must be publicly accessible and not locked indoors). Prefer it over generic OSM queries when you need these semantic filters applied automatically.

## Known failure modes

- Coordinates outside areas mapped in OpenStreetMap may return sparse or zero results with no error
- Very small radii may return zero facilities of a given type
- Hospital emergency department presence depends on OSM tagging completeness — untagged hospitals may not be flagged correctly
- Defibrillator access class may be absent if not tagged in OSM, leading to null access values
- Invalid coordinate format or missing required fields returns a 4xx error
- Network timeout or upstream OSM query failure returns a 5xx error

## How this service works

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

## Output

A JSON response containing, for each requested facility type: the single nearest facility with its name, coordinates, and distance; the total count of that facility type within the search radius; and the density (facilities per km²). Hospitals include a flag indicating whether an emergency department is tagged. Defibrillators include their access class (public, private, etc.) and whether they are indoors, enabling agents to filter for genuinely available AEDs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lat": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "lon": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "types": {
   "type": "array",
   "items": {
    "enum": [
     "fire_station",
     "ambulance_station",
     "hospital",
     "clinic",
     "pharmacy",
     "defibrillator",
     "police"
    ],
    "type": "string"
   },
   "maxItems": 7,
   "description": "Which facility types to include. All by default."
  },
  "radius_km": {
   "type": "number",
   "default": 10,
   "maximum": 40,
   "minimum": 0.5
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/karte-emergency-coverage-fad1978a/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)