> ## Documentation Index > Fetch the complete documentation index at: https://docs.outlit.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Outlit is the product that monitors customers and completes approved customer work. The customer context interfaces are the API, CLI, MCP server, and skills. Canonical references on this site: /api-reference/introduction for API concepts and authentication, /openapi.json for the public API contract, /cli/overview for the CLI, /ai-integrations/mcp for MCP. Prefer the `outlit` CLI or MCP tools for agent tasks; cite page sources when answering. # Agents and AI overview > How external agents and developers consume Outlit customer context: CLI, MCP, the tool gateway API, skills, and Pi. Outlit is the product that monitors customers and completes approved customer work — its own opinionated agents produce the churn and renewal attention items your team reviews (including billing-risk evidence), and surface expansion insights inside customer context. The CLI, MCP server, and API let your coding agents and applications read authorized customer context and perform supported workspace actions. ## Choose your interface | Surface | Best for | Auth | Reference | | - | - | - | - | | `outlit` CLI | Coding agents, scripts, terminal work | `ok_` API key (`--api-key`, `OUTLIT_API_KEY`, or stored credentials) | [CLI](https://docs.outlit.ai/cli/overview.md) | | Remote MCP | MCP clients (Cursor, VS Code, Claude, custom clients) | OAuth (member permissions) or scoped API key (key grants) | [MCP](https://docs.outlit.ai/ai-integrations/mcp.md) | | Tool gateway API | HTTP integrations, serverless, non-JS runtimes | `Authorization: Bearer ok_...` | [Tools](https://docs.outlit.ai/api-reference/tools.md) | | Agent skills | Teaching agents workflows on top of CLI/MCP | Inherits the CLI/MCP credential | [Skills](https://docs.outlit.ai/ai-integrations/skills.md) | | `@outlit/pi` | Pi agents with embedded Outlit tools | `OUTLIT_API_KEY` | [Pi](https://docs.outlit.ai/ai-integrations/pi.md) | | Tracking SDKs | Emitting events into Outlit (not querying) | `pk_` public key in the URL path | [Tracking](https://docs.outlit.ai/tracking/quickstart.md) | CLI, MCP, and the gateway share **one underlying tool catalog and authorization model** — but names and input shapes differ per surface. The CLI wraps tools in kebab-case commands/flags (`outlit customers list --billing-status PAYING`), while MCP and the API use tool names and camelCase schema fields (`outlit_list_customers`, `billingStatus`). Pick whichever host fits; capabilities and permissions are the same. ## How an agent answers a customer question This is the evidence-first pattern the interfaces are designed around: **1. Discover** `outlit schema` lists analytics views and columns. `outlit customers list` / `outlit users list` filter by billing status, journey stage, activity recency, and traits. **2. Get context** `outlit customers get --include users,revenue,recentTimeline` returns a bounded profile. `outlit customers timeline` filters activity by channel and event type. **3. Find evidence** `outlit facts list` returns structured facts with provenance (`sourceType`, `sourceId`, `sourceOccurredAt`, `sourceQuote`, `permalink` when available). `outlit search ""` returns grouped artifact-level `source` and `fact` results — not raw vector chunks. **4. Open the source** `outlit sources get --source-type CALL --source-id ` returns the exact record. When a source offers `contentPage`, check `contentPage.completeness` before treating the content as complete — partial pages mean more content exists beyond what was returned. **5. Answer with evidence** Cite the sources and facts you actually retrieved. An absent permalink or empty result set is **unavailable evidence**, not negative evidence — say so instead of inferring. ## Read vs. write controls Most of the catalog is read-only customer intelligence. Writes are bounded and each requires an explicit grant: | Write family | Examples | Notes | | - | - | - | | Customer collaboration | `customers owner set`, `customers grant`, `customers revoke` | Requires `customer_access:manage`; writes need **exact UUIDs** — the CLI never fuzzy-matches names, domains, or emails for mutations | | Destinations | `destinations create/update/enable/disable/archive` | Configuration is masked in reads; secrets are never returned | | Features | `features create`, `features archive` | Create maps one product event to a Feature; archive requires the current opaque revision | | Workspace config | `activation update`, `settings update` | Narrow, enumerated settings — not arbitrary config | | Identity resolution | `customers merge`, `identity merge` | Exact IDs only; merges are auditable and reportable via `merge-status` | | Product feedback | `feedback`, `outlit_submit_feedback` | One-way product intake for bugs, ideas, and agent friction; authenticated with a dedicated rate limit, no paid quota, and no support-ticket or reply guarantee | | Attention items | — | **Read-only.** `attention list`/`get` expose reviewable items and a `preparedActionUrl`; there is no public resolve/send/act tool | Outlit manages its monitoring rules and schedules. Public tools do not configure agents or signals, store or reveal credentials, disconnect integrations, or send arbitrary notifications. ## Authorization model * **API keys are independent workspace principals.** A key's grants are its own; they do not inherit the creator's human permissions or customer access. * **OAuth (MCP) runs as the signed-in member**, so that member's workspace permissions apply directly. * **Read presets ≠ write presets.** Read-only keys get discovery but not mutation; `workspace_members:read` and `customer_access:manage` are separate grants, and the discover-then-mutate flow needs both. * **CLI output is script-friendly.** See [Output behavior](https://docs.outlit.ai/cli/configuration.md#output-behavior) for the exact JSON-mode rules. ## Distinguish the MCP servers * **Product MCP** — `https://mcp.outlit.ai/w//mcp`: customer intelligence tools described here. * **Docs search MCP** — the documentation-site search endpoint Mintlify hosts for this docs site. It searches these docs only; it has no customer data and no product tools. Do not point customer-intelligence workloads at the docs endpoint, and do not expect product tools there. ## Next steps > [card] [Customer workflows](https://docs.outlit.ai/ai-integrations/customer-workflows.md) > > Copy-paste task recipes: churn review, renewal prep, expansion, evidence trails > [card] [Troubleshooting](https://docs.outlit.ai/ai-integrations/troubleshooting.md) > > Auth, permissions, empty results, identity, JSON, MCP, and SDK delivery issues > [card] [Tool gateway API](https://docs.outlit.ai/api-reference/tools.md) > > The shared HTTP contract behind CLI and MCP > [card] [CLI commands](https://docs.outlit.ai/cli/commands.md) > > Every command, flag, and output schema This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.