# War Tracker Event-Type Hub Page

> War Tracker Event-Type 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 hub page aggregating all conflict events matching a specific classification slug (e.g. drone-strike, airstrike, skirmish), with embedded JSON-LD structured data pointing to the underlying event API.

## Facts

- Endpoint: GET https://war-tracker.com/event-type/: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-40b0aa2c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hQV6hf_SEAe3Xg0YSSGpA

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-40b0aa2c
```

Example prompt: Pull up the war-tracker hub page for the 'drone-strike' event type so I can see all aggregated incidents in that category along with the structured data links.

## When to prefer this

Use this endpoint when you need a human-readable or structured-data-enriched view of all events of a specific conflict type, or when you want both rendered HTML and JSON-LD metadata in one call. Prefer the /api/v1/events endpoint instead for raw paginated JSON data, but use this hub page when you need classification-scoped aggregation with embedded schema.org structured data or want to present a browsable view.

## Known failure modes

- Unknown or misspelled slug returns 404 or empty page with no events
- Slug with no recorded events returns a valid page but an empty event list
- Malformed slug (special characters) may cause a 400 or redirect
- JSON-LD may be absent or malformed if the page is not fully rendered
- Payment failure (x402) prevents page access entirely

## How this service works

Event-type hub page at /event-type/{slug}. Aggregates events matching one classification slug (e.g. drone-strike, airstrike, skirmish). HTML with embedded CollectionPage + Dataset JSON-LD pointing back at /api/v1/events?event_type={slug}.

## Output

An HTML page for the given event-type slug containing a rendered list of matching conflict events, plus embedded CollectionPage and Dataset JSON-LD objects that reference the /api/v1/events?event_type={slug} API endpoint for machine-readable access.

## Example request

```json
{
 "slug": "drone-strike"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/war-tracker-com-40b0aa2c/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)