Live CoT stream — fused sensors + operator self-reports
Server-Sent Events from /api/tak/stream. Each event is a CoT XML document — the same payload a connected TAK Server would receive over its CoT port (8087/8089). Operator self-reports are highlighted.
Operator-as-sensor self-report
Push your position + a free-text observation into the bridge. Becomes a friendly-ground-unit CoT (a-f-G-U-C-I) on the next stream tick. With a configured TAK Server + admin key, the same CoT can be relayed straight into your TAK ecosystem.
TAK yellow pages — who's online
Shows operators who recently pushed a TAK self-report. Request-to-connect is a coordination handshake: it creates a pending request for TAK, voice, workspace, or field contact. It is not a chat service and does not bypass command net discipline.
Connection requests
Pending requests involving the operator ID above. Target operators can accept or decline from this console.
Bridged TAK Server
Connection info baked into Data Package preference profiles. The actual outbound relay is controlled by TAK_SERVER_URL + client cert env vars (server-side); update those via your deployment and they flow through here.
Live status
- loading
- …
What this bridge actually does
/Marti/api/cot POST relay for a real TAK Server · ATAK-ingestible .zip Data Package with a preference profile that pre-configures the EUD on first import.X-Admin-Key matching INTEL_ADMIN_SECRET. No FedRAMP / IL-5 / ATO claims. AI never authors ballistic numbers.