Overview

The browser calls /api/taurnet/* on the Zi Humana site. Next.js forwards requests to the multipath bonding backend (default port 8003). When the backend is offline, the console falls back to laboratory JSON snapshots under /investor-relations/research/multiple-path-bonding/media/.

Bonding endpoints

GET  /api/taurnet/api/bonding/status
GET  /api/taurnet/api/bonding/sessions?user_id=
POST /api/taurnet/api/bonding/start?user_id=

Status returns link state, throughput, latency, engine mode, and the Starlink · 5G · Fiber path inventory. Start records a bonded session and confirms the compose-stack engine when active.

Quantum optimize

POST /api/taurnet/api/quantum/optimize
Content-Type: application/json

{
  "paths": ["Starlink", "5G", "Fiber"],
  "user_id": 1
}

Runs a Bell-state circuit (1024 shots) and returns selected path, counts, and explanation. Decision rule: if C(00) > C(11) select the first path, else the last.

QKD generate

POST /api/taurnet/api/qkd/generate
Content-Type: application/json

{
  "num_bits": 16,
  "user_id": 1
}

Returns BB84 sifted key length, masked key preview, and basis vectors for the laboratory sifting service.

Health

GET /api/taurnet/health

Returns platform health and quantum-ready status from the bonding backend.

Live console

Open the Taurnet 1.0 dashboard for bonding status, path recommendation, and BB84 sessions. From the Industries homepage, choose Connectivity · Multipath Bonding and Taurnet 1.0, then Find solutions — routed to the RRMR API alias (RRMR/NP-hard/Multiple-path-bonding/api).

Open Taurnet 1.0 console →

Research archive

Manuscript and figures: doi:10.5281/zenodo.22219465. Dashboard HTML source: CDNER-X docs/static/dashboard.html.