Skip to main content
ego sits between your data and the agents that want to read it. You grant access one scope at a time instead of handing over a token that sees everything. Every grant is revocable, and every read goes through a single place you control, so access stays something you can audit and take back.
The ego API is in preview. The endpoints in these docs describe the shape we’re building toward; they aren’t live yet. The connections feature in the app works today.

​
Why it exists

Connecting an agent to your data usually means minting a token that reads everything, then hoping the agent behaves. That token outlives the task, nobody can see what it touched, and every agent reinvents how it reaches your files, mail, and databases. ego replaces that with one controlled interface:
  • Grant an agent the narrow slice it needs, not the whole account.
  • Take any grant back from one place, the moment you stop needing it.
  • Route every read through ego, where it’s logged, so you can see what an agent touched after the fact.
  • Reach files, mail, and databases through one interface, wired up once.

​
Start here

Quickstart

Make your first request against the ego API.

Grant scoped access

Connect a source and hand an agent one scope.

API reference

Base URL, authentication, and every endpoint.

ego on GitHub

Read the source and follow along.