# war-tracker.com Region Hub Page

> war-tracker.com Region Hub Page is a paid API for AI agents from war-tracker.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns an HTML page with embedded JSON-LD (CollectionPage + Dataset) aggregating conflict events for a specific geographic region identified by slug

## Facts

- Endpoint: GET https://war-tracker.com/region/:slug
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/war-tracker-com-ecddcd03
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3Nf3iYYl6EOVELFJOWoTS

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 war-tracker-com-ecddcd03
```

Example prompt: Pull the war-tracker conflict event aggregation for the Middle East region — give me the embedded JSON-LD dataset so I can see what the /api/v1/events pointer looks like for that region slug.

## When to prefer this

Use this endpoint when you need a structured overview of conflict events scoped to a continent, sub-continent, or maritime bounding box, and want machine-readable JSON-LD metadata without calling the raw events API directly. Prefer this over the /api/v1/events endpoint when you need the structured CollectionPage/Dataset context or want to discover the correct region-scoped API pointer. Use instead of country-level endpoints when the area of interest spans multiple nations or is a maritime zone.

## Known failure modes

- Invalid or unrecognized region slug returns 404
- Slug format mismatch causes no JSON-LD to be embedded in response
- Payment of $0.001 USDC not fulfilled causes 402 response via x402 protocol
- Region with no events returns empty dataset in JSON-LD
- Slow page load or timeout if region aggregation is large

## How this service works

Region hub page at /region/{slug}. Aggregates conflict events for a single region (continent, sub-continent, or maritime bbox). HTML with embedded CollectionPage + Dataset JSON-LD that points back at /api/v1/events?region=… so agents can read the JSON-LD instead of scraping the DOM.

## Output

An HTML page for the requested region containing embedded JSON-LD structured data (CollectionPage + Dataset types) that summarizes conflict events for that region and provides a back-reference to the /api/v1/events?region=… endpoint for machine-readable JSON data, allowing agents to extract structured conflict event metadata without scraping the DOM.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/war-tracker-com-ecddcd03/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from war-tracker.com](https://www.zero.xyz/host/war-tracker.com/llms.txt)