// API
Bring your own systems in.
Most teams never need this page. It's for the case where you run something custom and want ORiON to read it alongside everything else.
Custom systems connect through the Model Context Protocol — the open standard for giving an agent structured access to a tool. If you need programmatic access beyond what MCP provides, talk to us about it: the right approach depends on what you're building, and we'd rather scope it with you directly.
The Model Context Protocol route
MCP is an open standard for exposing a system's capabilities to an agent in a structured way. Rather than us building a bespoke integration for every tool that exists, your system describes what it can do, and ORiON's agents work with that description directly.
The practical implication for you: anything with a usable API can be brought in without waiting on our roadmap, and once it's connected it behaves like any other source — it appears in the Context Graph, agents can read it, and writes go through the same approval gate.
Your system needs a reachable API
Authenticated HTTP is the practical requirement. If the only access route is a UI or a nightly file drop, this doesn't apply.
Someone technical does the initial setup
A one-time task, typically an afternoon. After that the connection is managed alongside every other one and needs no ongoing engineering attention.
Scope the access deliberately
Grant the narrowest access that answers your questions. Unlike an OAuth connection inheriting a person's permissions, here you're choosing the boundary yourself.
It behaves like every other source
Same traceability, same approval gate on writes, same treatment in answers. No second-class integration path.
// CUSTOM SYSTEM