Skip to content
Enterprise

Ground truth, structured.

Satellites see heat. Sensors see position. Neither sees a queue at a fuel station, a substation still burning at hour thirty, or a port that quietly reopened. Witness delivers what only a person standing there can record, in a schema you can query.

What you get
01

Events endpoint

Geotagged, timestamped, categorized events as JSON. Filter by bounding box, category, time window, and confidence.

02

Confidence, exposed

Every event carries a confidence score and the evidence behind it, so you set your own threshold rather than inheriting ours.

03

Provenance

Every reporter-originated event carries a capture record you can defend downstream.

04

Managed access

Scoped keys, quotas, and full request logging.

Example response shape: single event
GET /eventsapplication/json
{
  "id": "evt_7f3a92c1",
  "occurred_at": "2026-07-19T04:17:32Z",
  "location": {
    "region": "approximate",
    "country": "approximate",
    "coordinates": null
  },
  "category": "infrastructure",
  "confidence": 0.82,
  "provenance": {
    "captured_at": "2026-07-19T04:16:58Z",
    "signals": ["device", "time", "location"],
    "capture_record": "attached"
  },
  "source": "reporter"
}
Why it is different
Machines cannot scrape what only a person standing there can record.

Aggregated feeds rent their data layer from platforms they do not control, which is why they cannot tell you where a file came from or vouch for what it shows. Witness owns the point of capture. Provenance is the product, not a feature on top of it.

What we will not sell
01

Identities. Buyers receive events. This is enforced in the schema, not only in the contract.

02

Real-time monitoring to law enforcement without a warrant and public transparency.

03

Data as a settlement or resolution source for prediction markets.

Access

Access is granted per organization. Tell us the regions and categories you care about and we will scope it with you.