Skip to main content

Labyrinth Scout

Labyrinth Scout is the optional control plane for production AI agents. It integrates with Carina, Aiva, and other stacks, but it is operated as its own product with its own console, docs, and pricing.

What Scout adds​

  • Prompt injection detection - Three layers: regex, tool-output patterns, LLM judge
  • Kill switch - Suspend an instance instantly; Carina listens on Redis labyrinth:control
  • Real-time dashboard - Events, anomalies, tool heatmap, instance heartbeats
  • Honeypots - Decoy API keys and file paths; access triggers breach events
  • Anomaly detection - Z-score baselines on session metrics (threshold 3.0)
  • Tool policy - Blocklist, rate limits, confirmation rules
  • Egress filter - HTTPS domain allowlist and response DLP

Get Scout access​

  • Hosted Scout details live on labyrinthscout.com#pricing
  • Self-hosted Scout setup lives in the Scout docs
  • Legacy Carina-hosted deployments may still use a pairing handoff while that flow remains in service.

Optional legacy pairing from Carina​

  1. Obtain LABYRINTH_URL and LABYRINTH_API_KEY from Scout provisioning or your self-hosted Scout .env.

  2. Add to Carina .env or run carina setup and paste when prompted:

    LABYRINTH_ENABLED=true
    LABYRINTH_URL=<your Scout console URL>
    LABYRINTH_API_KEY=<your Scout API key>
    LABYRINTH_INSTANCE_ID=carina-prod
    LABYRINTH_INSTANCE_NAME=Carina Production

  3. Restart Carina. Logs should show Scout heartbeat and kill-switch subscription.

Carina automatically:

  • Sends heartbeat every 60 seconds to POST /api/heartbeat
  • Reports tool calls and security events to POST /api/events
  • Flushes session metrics for anomaly detection
  • Subscribes to Redis for suspend/resume messages

Legacy hosted pairing​

If you use the legacy hosted Carina workspace, Scout can pair to that deployment:

  • /security - pairing key, instances, recent events
  • /dashboard - tenant-scoped live security dashboard
  • Cloud chat is monitored automatically (hosted:{userId} instance)
  • The same scout_live_* key can pair any supported deployment to the same Scout account

This pairing path is a deployment integration, not a product boundary. Scout remains product-separate.

Public trust metrics​

Anyone can poll read-only posture at labyrinthscout.com/trust without a Scout login. Tenant operators use their provisioned console for live events, kill switch, and quarantine.

Full documentation​

Agent integrators and operators should read:

labyrinthscout.com/docs

Topics include dashboard panels, HTTP API, SDKs (@verlox/labyrinth-scout, labyrinth-scout on PyPI), Docker deployment, ERC-8004/8126 on Base, and OpenAI-compatible proxy mode for third-party agents.