--- name: war-tracker.com description: war-tracker.com provides structured data on classified conflict events worldwide, including military strikes, airstrikes, skirmishes, and political incidents. It exposes a paginated REST API for querying events by country, region, type, confidence tier, and date range, as well as per-event detail endpoints returning machine-readable JSON or SEO HTML with schema.org JSON-LD. Coverage spans a live corpus of conflict incidents with geolocation, media links, and classification metadata. host: war-tracker.com --- # war-tracker.com war-tracker.com is a conflict event data host serving agents and applications that need structured, queryable records of global military and security incidents. It is distinct from news aggregators in that it classifies events by type, confidence tier, and location, and exposes both a bulk paginated API and individual event lookup endpoints. It does not provide real-time streaming feeds or raw media files, but does link to media assets and embed rich semantic metadata in its responses. ## When to use this host Use war-tracker.com when an agent needs structured, classified records of global conflict events — military strikes, airstrikes, skirmishes, security incidents — filterable by geography, event type, confidence, and date. It is the right choice for building event timelines, country-level incident summaries, or enriching a known event ID with full metadata. Do not use it for real-time or streaming situational awareness; it is a query-on-demand API, not a live feed. Do not use it to retrieve raw image or video bytes; it provides media URLs but not the media files themselves. For general news search or unclassified incident reporting, a news API would be more appropriate. For geopolitical analysis or forecasting beyond raw event records, this host provides inputs but not analytical outputs. ## Capabilities ### Event Discovery and Filtering Enables bulk retrieval and filtering of conflict events across countries, regions, event types, confidence tiers, and date ranges, with cursor-based pagination for large result sets. - **`fetch-conflict-events`** — Returns a paginated list of classified conflict events (up to 200 per call) ordered most-recent first, filterable by country, region, event type, confidence tier, and date range. ### Event Type Hub Pages Provides server-rendered HTML hub pages for specific conflict event-type slugs, embedding JSON-LD CollectionPage and Dataset metadata that points agents to the structured API for deeper querying. - **`fetch-event-type-hub`** — Returns a server-rendered HTML hub page for a given conflict event-type slug, embedding CollectionPage and Dataset JSON-LD that links to the structured /api/v1/events endpoint for machine consumption. ### Single Event Detail Retrieval Returns full structured or HTML records for a specific conflict event by ID, including classification, geolocation, media URLs, FAQ, transcript, and schema.org metadata. - **`fetch-war-tracker-event`** — Returns the full machine-readable record for a specific conflict event by ID, including classification, location, description, media URLs, FAQ, transcript, and schema.org JSON-LD metadata. - **`fetch-war-tracker-share-article`** — Returns the canonical per-event article for any event id: SEO HTML with embedded schema.org JSON-LD, or the same JSON as /api/v1/events/{id} when Accept is application/json. ## Workflows ### Discover and Detail Conflict Events *Use when an agent needs to find recent conflict events matching specific criteria and then retrieve full structured details for one or more of those events.* 1. **`fetch-conflict-events`** — Query the paginated events API with desired filters (country, event_type, date range, etc.) to obtain a list of matching events and their IDs and URLs. 2. **`fetch-war-tracker-event`** — For each event ID of interest from the previous step, retrieve the full machine-readable record including classification, geolocation, media links, and schema.org metadata. ### Event Type Overview to Structured Data *Use when an agent needs a human-readable summary of a conflict event type category and then wants to follow up with structured API queries for that event type.* 1. **`fetch-event-type-hub`** — Fetch the hub page for a given event-type slug to obtain a summary, recent headlines, affected countries, 30-day counts, and the embedded JSON-LD Dataset distribution URL. 2. **`fetch-conflict-events`** — Use the event_type filter (matching the hub slug) to retrieve paginated structured event records for that category from the API. ### Event List to Article Retrieval *Use when an agent needs to retrieve the human-readable article or Open Graph metadata for specific events found via a bulk query.* 1. **`fetch-conflict-events`** — Query for events matching desired filters to obtain a list of event IDs and URL slugs. 2. **`fetch-war-tracker-share-article`** — For selected events, fetch the canonical per-event article using the event_id and slug, retrieving SEO HTML with JSON-LD or JSON depending on the Accept header. ## Skill reference ### `fetch-event-type-hub` **Drone Strike Tracker Hub** — Returns a server-rendered HTML hub page for a given conflict event-type slug, embedding CollectionPage and Dataset JSON-LD that links to the structured /api/v1/events endpoint for machine consumption. *Use when:* Use when an agent needs a summary of tracked conflict events for a specific event type (e.g. drone-strike, airstrike, skirmish) including recent event headlines, affected countries, 30-day counts, and a pointer to the structured JSON API for deeper querying. *Not for:* Do not use to retrieve raw structured event data directly; follow the embedded JSON-LD Dataset distribution URL (/api/v1/events?event_type={slug}) for machine-readable JSON event records instead of parsing this HTML response. **Inputs:** - `slug` (string, required) — Event-type slug in lowercase dash-separated format. Valid values include drone-strike, airstrike, skirmish, naval-engagement. See /api/v1/event-types for the canonical taxonomy. **Returns:** Returns an HTML page with embedded JSON-LD listing 84 drone-strike events in the last 30 days, recent NewsArticle entries with headlines and publish dates, and a Dataset distribution URL pointing to the structured JSON API. **Example:** `GET https://war-tracker.com/event-type/drone-strike` --- ### `fetch-conflict-events` **War Tracker Events** — Returns a paginated list of classified conflict events (up to 200 per call) ordered most-recent first, filterable by country, region, event type, confidence tier, and date range. *Use when:* Use when an agent needs structured data on recent conflict events — military strikes, security incidents, political developments — for a specific country, region, or date window, or when paginating through a large event corpus using a cursor. *Not for:* Do not use for real-time streaming event feeds or live situational awareness; this is a single-shot paginated query. Do not repeat filter parameters when paginating — pass only the cursor from the previous response. **Inputs:** - `country` (string) — ISO-3166-1 alpha-2 country code, uppercase. Filters events to a single country. - `region` (string) — Region slug from /api/v1/regions. Filters events to a named region. - `event_type` (string) — Event-type display string, case-insensitive. Filters to a specific event category. - `confidence` (string) — Classifier confidence tier: LOW, MEDIUM, HIGH, or ALL (default). HIGH means multiple corroborating signals or human review; LOW means single-source or ambiguous. - `from` (string) — ISO-8601 lower bound on event date (inclusive). - `to` (string) — ISO-8601 upper bound on event date (exclusive). - `cursor` (string) — Opaque pagination cursor from the previous response's next_cursor. Pass verbatim; do not also include filter parameters when paginating. - `limit` (integer) — Page size between 1 and 200. Defaults to 200. **Returns:** Returns an events array of up to 200 objects each containing id, url, date, modified, event_type, location, country, country_name, lat, lng, has_media, is_video, source_url, confidence, and description fields (several nullable in practice). **Example:** `GET https://war-tracker.com/api/v1/events?country=RU&event_type=Military+Strike&confidence=HIGH&from=2026-05-01&to=2026-05-18&limit=50` --- ### `fetch-war-tracker-share-article` **War-Tracker Share Article** — Returns the canonical per-event article for any event id: SEO HTML with embedded schema.org JSON-LD, or the same JSON as /api/v1/events/{id} when Accept is application/json. *Use when:* Use when you have an event_id and slug from GET /api/v1/events (each row's url field) and need the human-readable article, Open Graph metadata, or JSON-LD graph for that event. Works for any classified conflict incident in the live corpus, not only one historical story. *Not for:* Do not use to list or search events (use fetch-conflict-events). Do not use for raw photo or video bytes (use /media/{event_id}). Prefer /api/v1/events/{id} when you only need JSON without HTML. **Inputs:** - `event_id` (string, required) — Numeric event id from /api/v1/events (integer in the path). - `slug` (string) — URL slug from the event's canonical url field; cosmetic (server canonicalises to the stored slug). - `Accept` (string) — Use application/json for the same payload as /api/v1/events/{id}; default text/html for the rendered article. - `x402-payment` (string, required) — x402 payment header containing a USDC payment of 1000 atomic units (0.001 USDC) on Base (eip155:8453), scheme exact, maxTimeoutSeconds 60. **Returns:** The endpoint returned a successful 200 response with a specific, content-rich report matching the requested topic: the military withdrawal in Qasrak, Syria. The page includes the event summary, timing, location, classification, and related metadata. Response size is acceptable fo **Example:** `GET https://war-tracker.com/share/{event_id}/{slug}` --- ### `fetch-war-tracker-event` **War Tracker Event Lookup** — Returns the full machine-readable record for a specific conflict event by ID, including classification, location, description, media URLs, FAQ, transcript, and schema.org JSON-LD metadata. *Use when:* Use when an agent needs structured details about a specific conflict event by its numeric ID, including event type, geolocation, confidence rating, article text, media links, and super-event context. *Not for:* Do not use to retrieve full media bytes (video/image files); use the /media/{event_id} endpoint instead. Not suitable for searching or listing events — this is a single-event lookup by known ID. **Inputs:** - `Accept` (string) — Response format header. Defaults to application/json; the endpoint always returns JSON regardless of value. **Returns:** Returns a JSON object with event id, headline, date, location, country, lat/lng, event_type, confidence, description, tldr, article_paragraphs, faq, media_url, thumbnail_url, transcript, super_event metadata, and a schema.org JSON-LD graph. **Example:** `GET https://war-tracker.com/api/v1/events/397003` ---