BATTLEBYTES
LIVE --:--:--Z

For AI agents

AI agents, crawlers and researchers are welcome on BattleBytes. Everything on the Site is static and machine-readable. This page lists what is available and what we ask in return.

Start here

  • /llms.txt — a plain-text map of the Site for language models: what each section is and where the data lives.
  • Markdown mirrors. Content pages have a Markdown version at index.md in the same folder; for example, a conflict page at /conflicts/ukraine/ has its text at /conflicts/ukraine/index.md.

Data files

  • /data/theatres.json — every theatre we track: id, slug, name, region, status, trend, intensity (0 to 1), reference point, bounding box, start date, parties and a one-line summary.
  • /data/control/<slug>.json — control areas, front lines and gray zones for the theatres with battlefield maps, as GeoJSON inside a JSON wrapper, with weekly snapshots and the Wikipedia module revisions they were derived from. Released under CC BY-SA 4.0. Rebuilt daily.

Live feeds

Live layers are published as static files on our data host, https://battlebytes-live.pages.dev:

  • /live/status.json — when each feed last updated, and event, aircraft, fire and alert counts for each theatre.
  • /live/events-24h.geojson — reported events from the last 24 hours, with type, time, confidence (1 to 3), theatre and the outlets that reported them.
  • /live/aircraft.geojson — military and government aircraft broadcasting publicly over ADS-B.
  • /live/fires.geojson — satellite-detected thermal anomalies inside our theatres.
  • /live/gdacs.geojson and /live/quakes.geojson — natural-disaster and earthquake alerts.
  • /live/news.json and /live/videos.json — the items behind the Live page.

These feeds are refreshed every few minutes and observe the delays in our Methodology: event pins appear no sooner than one hour after the event, and control changes no sooner than 24 hours after first report.

Rate expectations

  • Poll live feeds no more than once every five minutes; they do not change faster than that.
  • Fetch control files and theatres.json no more than once an hour; they change at most daily.
  • Use conditional requests (If-None-Match / If-Modified-Since) and cache what you fetch.
  • Send a descriptive User-Agent with a way to contact you.
  • Crawl HTML pages at a modest pace. If you only need the text, the Markdown mirrors are lighter.

Using what you take

  • Respect the licenses: our derived control layers are CC BY-SA 4.0, and third-party data in the feeds stays under its owners' licenses, listed on our Attributions page.
  • Keep claims as claims. If you summarize our pages, keep the attribution of contested statements to the party that made them, and keep the confidence level attached to any event.
  • Nothing here is suitable for operational, targeting or safety decisions, and that applies to automated systems as much as to people.

Questions or problems: [[email protected]](mailto:[email protected])

Endpoints

  • Theatres: https://battlebytes.net/data/theatres.json
  • Territorial control (CC BY-SA 4.0): https://battlebytes.net/data/control/<slug>.json
  • Live (refreshed every 5 minutes): https://battlebytes-live.pages.dev/live/status.json, /live/events-24h.geojson, /live/aircraft.geojson, /live/fires.geojson, /live/gdacs.geojson, /live/quakes.geojson, /live/news.json, /live/videos.json
  • Every content page has an index.md mirror beside it; see /llms.txt.