Introduction
What Median is, how the pieces fit, and where to start.
Median is an AI support agent for your product, with an inbox for whatever it cannot finish.
How it works
| Step | What happens | Read more |
|---|---|---|
| Customers write in | From the support widget, the support modal, the contact form or the feedback panel on your site. Also by email, in your Discord server, or through your own UI on the API. | Components |
| The agent answers | It searches your knowledge, calls the tools you define, and replies in the thread. | Knowledge, Custom tools |
| Your team takes over | A thread the agent cannot finish moves to Needs a person in the inbox. High risk tool calls wait there for a teammate’s approval. | Inbox |
| Signal collects the rest | Bugs and suggestions from conversations and the feedback panel land in Signal. Send them on to Linear or GitHub. | Signal |
Set up
| Path | What you do | Start here |
|---|---|---|
| Dashboard | Create a key, mount the widget, and write the agent’s first document in the browser. | Quickstart |
| CLI | Run median login once. Every later step is a command, so a coding agent can run it. |
CLI |
For AI coding agents
| Resource | Where |
|---|---|
| Markdown copy of any page | Add .md to the page URL, as in https://docs.median.sh/installation.md. The home page is /index.md. |
| Page index | https://docs.median.sh/llms.txt lists every page with its description. |
| Whole site in one file | https://docs.median.sh/llms-full.txt |
| Your workspace | The MCP server lets an agent read and work your inbox, knowledge and settings. |
Next steps
Quickstart
From a new account to an answered test message.
Install the widget
Every stack, environment variables, identity and CSP.
Custom tools
Let the agent look things up and act in your product.
Inbox
Pick up the threads the agent hands over.
Knowledge
The documents the agent answers from.
API
Keys, authentication and the REST API.