⚡
MagnusEdge

Dashboard

Live competitor insights across the Magnus and Quiky ecosystem.

Competitors tracked
—
Active targets
—
Open insights
—
Scans / 24h
—

Swarm pipeline

  1. 1. Scheduler wakes up stale targets (cadence-based).
  2. 2. For each target, create a scan row + dispatch to the swarm via POST /api/brain/tasks.
  3. 3. Worker agent fetches + normalizes + diffs vs. previous snapshot.
  4. 4. On meaningful diff, agent returns structured insight — kind, severity, title, summary, affected_products[].
  5. 5. Insight surfaces in the relevant Magnus/Quiky product dashboard via GET /api/insights?product=X.

Scheduler + worker agents land in the next MagnusEdge build session. Schema + API + swarm dispatch primitive are in place today.

Recent insights

No insights yet — first scan cycle happens once targets are seeded and the scheduler boots.

GET /api/insights → { insights: [] }

Targets

Seed the initial target list (Telegram, Stripe, Twitch, Auth0, etc.) via POST /api/admin/seed once auth is wired.

GET /api/targets → { targets: [] }