ASK, IN CONTEXT
A question about the surface you are already on.
What Copilot answers, why it appears on some routes and not others, and what bringing your own model key means.
THE SHAPE
Copilot is contextual, not a destination
Copilot is asked from the route you are on, about what that route is showing. It has no page of its own because the context is the point: a question about a backtest result means something different from the same words typed into an empty box.
A route without a context contract has no Ask button. That is deliberate - a surface gets one on the day its contract exists, and never as a decoration before then.
YOUR KEY
Bring your own model
Copilot runs against a model endpoint you configure with your own key, using an OpenAI-compatible interface. Meridian does not resell inference, and what you spend is between you and your provider.
Because the inference is yours, Copilot is not metered in credits. It is available on Pro and above, and the endpoint is configured in Settings alongside the assistant connections.
- Your key stays server-sideIt is stored on the account and used from the gateway; the browser never holds it.
- Answers cite what they readCopilot answers from the evidence the route already carries, so a claim can be traced back to the surface that produced it.
QUESTIONS
Common questions
How is this different from an assistant connection?
Direction. Copilot is Meridian asking a model a question on your behalf, about the screen you are on. An assistant connection is a Claude client reaching into Meridian and calling its tools as you.
Can Copilot place a trade?
No. It reads and explains. Execution has a single path through Automations and a Portfolio boundary, and there is deliberately no second, quieter one.
Does it cost credits?
No. You are paying your own model provider directly, so there is nothing for Meridian to meter.