Optics · Observe · Free

See where supported agent traffic goes.

Optics records connection and process metadata from wrapped agent paths. Install without an account.

Install OpticsGitHub

Three outcomes

  • Identify destinations used by wrapped agents.
  • Attribute activity to a process and trace.
  • Export metadata from infrastructure you control.

How it works

Sight Loop is the daily workflow. Wrap the agent process, watch outbound connections, and inspect the run locally. vantio doctor checks the install. vantio coverage --local names attached, idle, outside, and degraded paths. vantio leave stops the wrap. Metadata can be exported from the machine you control. A read-only Optics MCP is available. Full steps live in Docs.

  1. 01

    Install the CLI

    npm i -g @vantio/cli

  2. 02

    Wrap a Node agent

    vantio run --summary node agent.js

  3. 03

    Inspect the run

    vantio prove --list
vantio prove

Python support requires vantio-agent-sdk. Follow the current Python SDK example and verify that a supported outbound event appears before relying on the coverage state.

pip install vantio-agent-sdk
vantio run python agent.py

Data and privacy

Optics records the fields below. Prompts and completions are not retained.

Recorded

  • Destination
  • Provider
  • Process and runtime
  • Timing
  • Request and response size
  • Trace identifier
  • Decision metadata when used with Gate

Not recorded

  • Prompts
  • Completions
  • Request or response bodies
  • Authorization headers
  • Query strings

Coverage and limitations

Optics sees traffic that enters the wrap. It does not block, and it is not an organization-wide agent scanner. Browser paths stay outside this wrap. Inventory questions it cannot answer yet stay named: which agents are running, which are protected, which sit outside the wrap, and who owns each deployment.

Model APIs on the wrap

OpenAI, including regional endpoints, Anthropic, Google Gemini, Google Vertex AI, Amazon Bedrock, Azure OpenAI, Azure AI, Cohere, Mistral, Groq, Together AI, Perplexity, xAI, DeepSeek, Fireworks, OpenRouter, Cerebras, Voyage AI, SambaNova, DeepInfra, Hugging Face Inference, Replicate, Ollama, NVIDIA NIM (hosted).

Agent runtimes

Node fetch, undici.fetch, undici.request, undici.stream, Node http/https, Node http2, Node net/tls, Node WebSocket, Node-spawned curl/wget, Python urllib (vantio run / shield()), Python http.client (vantio run / shield()), Python requests (vantio run / shield()), Python httpx (vantio run / shield()), Python aiohttp (vantio run / shield()), Python urllib3 (vantio run / shield()), Python sockets (vantio run / shield()), Python-spawned curl/wget (vantio run / shield()).

Compatibility matrix

Questions that add detail

Where does Optics run?
Inside the agent process you wrap, on macOS, Linux, or Windows with WSL. Telemetry stays on that machine.

Next: Gate

When those records need to become rules, Gate applies policy on the same wrap.

Explore Gate