API

Versioned, machine-readable feeds for OneNetwork and a future Meta Sentinel. No private credentials in the browser.

/api/v1/health
/api/v1/sources
/api/v1/observations
/api/v1/intelligence-objects
/api/v1/intelligence-objects/:id
/api/v1/investigations
/api/v1/attention
/api/v1/events
/api/v1/relationships
/api/v1/brief
/api/v1/map-state
/api/v1/handoffs
/api/v1/handoffs/marine
POST /api/v1/ask
POST /api/v1/ingest (header x-ingest-token)
POST /api/v1/onenetwork/flush (header x-ingest-token)
POST /api/v1/onenetwork/publish (header x-ingest-token, disabled unless publication is enabled)

Filters: time, geography, source, confidence, sphere, variable, Intelligence Object type, relationship type, sentinel. Kernel publication is separate from ingest health. It stays off unless ONENETWORK_PUBLICATION_ENABLED is true. The Worker then calls the ONENETWORK service binding with the ONENETWORK_API_KEY secret. POST /api/v1/onenetwork/publish sends the current Haze Intelligence Object only. The legacy outbox and the empty ONENETWORK_API_URL path are not used for that delivery. Marine handoffs are not part of it. Ingest, flush, and publish require the Worker secret INGEST_TOKEN in the x-ingest-token header. That secret is not sent to the browser. The scheduled ingest does not use the header.