Partner Integration

ISS LLC (DBA SecureAssure) · SDVOSB pending · partners@secureassure.app

NATO eval-ready STANAG-aligned (intent) CoT / Link 16 / VMF / GeoJSON Versioned schema

Live status

probing /api/live-feed/tracks …

probing /api/partners/schema …

probing /api/live-feed/stream …

Three-tier integration path

Tier 1 — Pull (works today, zero code our side)

Your client polls a stable JSON endpoint on adaptive cadence (typically 1–5s with jitter; honor X-Atlas-Poll-* headers). Use /api/partners/snapshot/v2 for one-call immersive payloads, or protocol-specific formats below.

GET /api/partners/snapshot/v2
GET /api/live-feed/tracks?limit=500
GET /api/live-feed/tracks?format=cot
GET /api/live-feed/tracks?format=link16
GET /api/live-feed/tracks?format=vmf
GET /api/live-feed/tracks?format=geojson

Tier 2 — Push (SSE, live now)

Server-Sent Events stream. Same envelope as Tier 1, pushed every ~2s + 30s heartbeats. Standard EventSource.

GET /api/live-feed/stream
event: snapshot
data: {"tracks":[…], "count":11, …}

Tier 3 — Bidirectional

Your HUD sends cueing events, gets back DECIDE-layer recommendations.

POST /api/integration/cot/ingest    # inbound from your sensors
GET  /api/atlas/threat-assessment   # ATLAS DECIDE layer

Standards alignment

Standard	Status	Endpoint	Notes
STANAG 5516 (Link 16 / TADIL-J)	Outbound	`/api/live-feed/tracks?format=link16`	Message conversion. Not a certified Link 16 terminal.
MIL-STD-6017 / VMF K05.1	Outbound	`/api/live-feed/tracks?format=vmf`	Self-assessed alignment.
Cursor on Target (CoT 2.0) — TAK/ATAK	Bidirectional	`?format=cot` · `/api/integration/cot/ingest`	TAK ecosystem compatible.
GeoJSON (RFC 7946)	Outbound	`?format=geojson`	Standard GIS consumer.
NATO JC3IEDM (data model)	Alignment intent	—	Envelope field naming mirrors JC3IEDM categories where possible. Not a certified JC3IEDM implementation.

Endpoints

Method	Path	Purpose
loading from /api/partners/manifest …

Canonical envelope

Track envelope (v1): /api/partners/schema. Immersive snapshot (v2): schema and payload. Example below is v1 track schema.

loading …

Sample consumer — browser / WebXR

Drop into any browser or WebXR context. Unity (C#) consumers should poll Tier 1 with adaptive jitter (not every render frame) or use an SSE plugin for near-live push.

loading /api/partners/sample-client.js …

IP terms

Partner renders. Your scene / HUD / XR app is your IP.
ATLAS owns. Data schema, decision logic, audit trail, source feeds.
No source merge. No shared repos. You consume the versioned schema + endpoints; ATLAS evolves independently.
Contract basis. Per-partner CRADA or SOW. Standard terms: ISS LLC retains all backend IP.

Reach back

partners@secureassure.app Manifest JSON Schema JSON Snapshot v2 Live picture (/cop)

SHIELD/ATLAS · ISS LLC (DBA SecureAssure) · Dr. Terry Flood, CWO 131A Ret. · Veteran-Owned · SDVOSB pending · This page documents UNCLASSIFIED feeds. CUI / SECRET surfaces require a separate agreement.