# War Tracker Event Article (Share Page)

> War Tracker Event Article (Share 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-15).

Returns a full SEO article page or structured JSON payload for a single conflict event by ID, including embedded NewsArticle, VideoObject, and FAQPage schema.org data.

## Facts

- Endpoint: GET https://war-tracker.com/share/:event_id
- Price: $0.001/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-d27c93fe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XhClt4TdI3WfJfdTKiVdP

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

Example prompt: Pull up the full article and structured data for war-tracker event ID 48271 — I want the NewsArticle, any embedded video, and FAQ details about that incident.

## When to prefer this

Use this endpoint when you need rich, structured article-level data for a single specific conflict event, especially when you want schema.org-compatible JSON-LD (NewsArticle + VideoObject + FAQPage) or a human-readable HTML article. Prefer this over the paginated /api/v1/events endpoint when you already have a specific event ID and want full event detail rather than a list.

## Known failure modes

- Event ID not found returns 404
- Invalid or malformed event_id returns 400
- Slug mismatch may redirect or 404
- Payment not included or invalid returns 402
- Server error returns 500

## 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 a server-rendered HTML page with embedded schema.org JSON-LD @graph (containing NewsArticle, VideoObject, and FAQPage nodes) or, when Accept: application/json is sent, the same data as a pure JSON payload matching the /api/v1/events/{id} shape — covering event details, media references, and structured Q&A.

## More

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