Connectors

Connectors plug your world into your agent. Each one sharpens what your agent can see and, behind your approval, what it can do. You reach them from the lightning bolt in the agent chip, or the Connectors tab on the dashboard.

The surface has three tabs:

• Connected shows only what is actually connected: your accounts (with the addresses your agent reads and what each address grants), plus any API keys you have added. The counter at the top mirrors this list exactly.
• Gallery is where you browse everything you can connect, grouped by service area. Mail and calendar, messaging, knowledge, and the money-and-ops services sit side by side. One search box covers all of it, and a search with no match becomes a request to your agent so we know what to build next.
• Custom connects any service with an API key, even one we have never heard of.

Mail, calendar, and messaging

Google and Microsoft accounts connect with a normal sign-in. Your agent can then read your inbox and calendar to prepare briefs and answers; anything it sends waits for your approval first. You can connect more than one account, and each account chip shows which services (mail, calendar, drive) that address grants.

WhatsApp connects as a linked device, the same way WhatsApp Web does. More channels are labeled in the Gallery as they come.

The Gallery: one key, real work

The money-and-ops services (Mercury, Cloudflare, AWS, Azure, Google Cloud, Hetzner, X, Mailjet) follow one pattern:

1. Open the service card in the Gallery. It shows what your agent can do with the account and a few example asks.
2. Follow the numbered steps on the card to create an API key in that service's own dashboard. The card tells you exactly where the key lives.
3. Paste the key into the card and connect.

The key goes straight into a credential vault, pinned to that service's own API host. It never lands in our database, and your agent can only reach the one host the key was pinned to. Reads happen on their own; anything the agent wants to change upstream comes to you as an approval card first.

Connecting is live for all of these today; per-service agent skills are still rolling out, so the depth of what your agent can do with each one grows over time.

Custom connectors

Any service with an HTTPS API can connect from the Custom tab:

1. Give it a short name (lowercase letters, numbers, dashes).
2. Paste the API host, like https://api.example.com. Host only, no path.
3. Paste the key and connect.

The same rules apply: the key lives in the vault, pinned to the one host you named, and writes wait for your approval. Once connected, it shows under Connected with the rest.

What your agent can and cannot do with a key

• Your agent can read from a connected service on its own, to ground briefs and answers.
• Anything that changes the outside world (a payment, a DNS record, a post, a campaign send) is proposed first and waits on your approval card.
• A key is scoped to the host it was pinned to. Your agent cannot point a credential at a different service.

Not yet

• Telegram, Signal, Slack, Notion, iMessage. Listed in the Gallery as coming; connecting them does not work yet.
• Stripe. On the roadmap; there is no connect flow today.
• Per-service skill depth varies. A freshly connected service may start with reads and simple proposals while its skills roll out.