# War Tracker Per-Event Article (Share Page)

> War Tracker Per-Event Article (Share Page) is a paid API for AI agents from war-tracker.com, paid per call via x402, $0.001000/call, status unknown (last checked 2026-09-15).

Returns the full article for a single conflict event by ID and slug, either as SEO HTML with embedded JSON-LD or as a structured JSON payload.

## Facts

- Endpoint: GET https://war-tracker.com/share/:event_id/:slug
- Price: $0.001000/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/war-tracker-com-c2225316
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rpHWLXYXVKQQBDQ33iARZ

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-c2225316
```

Example prompt: Pull up the full article for war-tracker event ID 48271 (slug: 'drone-strike-kyiv-2024') — give me the structured JSON version with the NewsArticle, VideoObject, and FAQ data.

## When to prefer this

Use this endpoint when you need the full editorial article content for a specific known conflict event (by ID and slug), especially when you want the rich JSON-LD structured data (NewsArticle + VideoObject + FAQPage) or need the canonical shareable URL representation. Prefer this over the paginated /api/v1/events endpoint when you already have an event ID and want maximum content depth rather than a list of events.

## Known failure modes

- Event ID not found — 404 with no article body
- Invalid slug mismatch — may redirect to canonical URL or return 404
- Malformed event_id — 400 bad request
- Payment not provided or invalid — 402 Payment Required
- Content negotiation failure — unsupported Accept type returns default HTML

## How this service works

Per-event article at /share/{id}/{slug}. Default response is the SEO-canonical HTML page with an embedded JSON-LD @graph (NewsArticle + VideoObject + FAQPage). Content-negotiable: send `Accept: application/json` or `application/ld+json` to receive the same data as a pure JSON payload (the same shape as /api/v1/events/{id}). One payment covers either representation.

## Output

Either an HTML page (default) with embedded JSON-LD @graph containing NewsArticle, VideoObject, and FAQPage schemas, or — when Accept: application/json is sent — the same data as a pure JSON payload matching the shape of /api/v1/events/{id}. Includes event narrative, media references, and FAQ entries about the conflict event.

## Example request

```json
{
 "slug": "drone-strike-kyiv-2024",
 "format": "json",
 "event_id": "48271"
}
```

## More

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