Documentation Index
Fetch the complete documentation index at: https://docs.mirage.strukto.ai/llms.txt
Use this file to discover all available pages before exploring further.
One View Across Systems
Mirage gives agents one way to see external systems. Instead of exposing every backend through its own API shape, Mirage represents services, data, and infrastructure through a unified filesystem interface. The agent gets one environment to browse, inspect, and reason about, with no mental-model switch per resource. This is the eyes for AI agents: how they perceive what exists, where it lives, and how to reach it.Why Representation Matters
Large language models work best when the environment is legible. Mirage makes systems legible by representing them through:- mounted paths
- directory structure
- stable, file-shaped resources
- familiar discovery commands such as
ls,find,grep, andcat
A Unified Interface
Mirage doesn’t ask the agent to remember one shape for GitHub, another for S3, another for Slack, and another for local disk. It maps all of them into the same visible environment. Discovery becomes consistent, provenance becomes traceable, and cross-system reasoning gets dramatically simpler. For an agent,/github/repo/README.md and /s3/reports/q1.csv are different resources, but they live behind the same interface, and the same cat, grep, or ls works on both.
Why This Fits Agents
Agents need more than raw access. They need an environment they can inspect and navigate reliably. A unified view gives them:- one way to discover what is available
- stable paths they can revisit and cite
- clearer provenance for outputs
- less prompt overhead spent translating between resource-specific APIs