# Halowerk Location Heatmap

> Halowerk Location Heatmap is a paid API for AI agents from research.halowerk.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-09-15).

Extracts geographic places mentioned in news coverage of a topic, returning each location with article count, source count, and coordinates — distinguishing where events occurred from where they were merely referenced.

## Facts

- Endpoint: POST https://research.halowerk.com/v1/location-heatmap
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-location-heatmap-15d03268
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cjxxbcjTFZ3pMnaidD-th

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-location-heatmap-15d03268 -d '<json body>'
```

Example prompt: Can you map the geographic locations mentioned in news coverage of the EU carbon border adjustment mechanism — I want to see which places appear most, how many articles mention each, and how many distinct sources are citing them?

## When to prefer this

Choose this endpoint when you need to understand the geographic distribution of media coverage for a topic — particularly when you want to distinguish where events are actually occurring versus where they are merely referenced. It is ideal for building news heatmaps, tracking regional media attention, or doing geopolitical research where location-event attribution matters. Prefer it over generic geocoding services because it operates on the news corpus itself rather than on a user-supplied text.

## Known failure modes

- Topic query too vague returns very broad or noisy location sets
- No articles found for niche or very recent topics returns empty results
- Coordinates absent for ambiguous or lesser-known place names
- Place name disambiguation errors when a name refers to multiple locations
- High volume of coverage may return truncated result sets

## How this service works

Returns the geographic places named in coverage of a topic, each with the number of articles mentioning it, the number of distinct sources, and coordinates where the source supplies them. The distinction the service is built on is between mention and occurrence: an article about a decision taken in Brussels affecting mining in Chile names both places, and reading the resulting map as an event map puts the decision in Chile and the mining in Brussels.

## Output

A list of geographic places found in news coverage of the queried topic, each with the place name, number of articles mentioning it, number of distinct sources referencing it, and coordinates (latitude/longitude) where available. The data distinguishes between places where events occurred versus places merely referenced in passing, enabling accurate event-location mapping.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "integer",
   "default": 50,
   "maximum": 200,
   "minimum": 5
  },
  "topic": {
   "type": "string",
   "maxLength": 200,
   "minLength": 3
  },
  "timespan": {
   "type": "string",
   "default": "7d",
   "maxLength": 6
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-location-heatmap-15d03268/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from research.halowerk.com](https://www.zero.xyz/host/research.halowerk.com/llms.txt)