Your agent · Your services
Atom is not another walled garden. Your personal agent lives in a shell you control — and connectors are how it reaches the tools you already rely on. You stay in charge: you choose what to link, what your agent may read or write, and when to approve a real-world action.
When you ask Atom to “check my calendar” or “add this to my notes,” three things happen:
Your passwords and API tokens do not sit in the chat window. They are held in your agent’s secure vault and used only when you (or a policy you set) allow it.
Atom does two different kinds of connection — both matter, and they solve different problems.
Link your agent to your accounts: calendar feeds, note-taking apps, email, smart-home devices, payment methods. The service stays where it is; Atom gets a controlled bridge.
Analogy: the power adapter that lets your laptop use the wall socket — same electricity, safe boundary.
When you message a coffee shop, accept a meeting proposal, or compare offers, your agent talks to their agent using structured, signed messages — not by scraping their website.
Analogy: two assistants on a phone call while you listen and approve anything important.
Each row is a real-world pattern Atom is designed for. Some connectors exist today; others are on the roadmap — the architecture is the same: build the bridge once, every user’s agent can use it.
| Service type | What your agent could do | Examples |
|---|---|---|
| Calendar | See free/busy times, propose meetings, add events after you approve | Google Calendar, Outlook, Apple Calendar (via a private feed) |
| Notes & tasks | Capture ideas, search pages, create or update tasks you asked for | Notion, Todoist, Apple Reminders, Obsidian |
| Summarise threads, draft replies for your review, file receipts | Gmail, Outlook, Fastmail | |
| Files & docs | Find the right document, attach it to a message, extract facts you need | Google Drive, Dropbox, OneDrive |
| Payments | Hold or capture a payment only after shell confirmation | Stripe, PayPal, open-banking rails (region-dependent) |
| Travel & booking | Compare options, hold a seat or room, complete booking when you confirm | Airlines, hotels, train operators (via their agent or API) |
| Work chat | Post updates, read channels you authorise, schedule from standup notes | Slack, Microsoft Teams |
| Smart home | Run scenes you define — “dim lights for movie night” — with explicit permission | Home Assistant, Philips Hue, Nest |
Notion-style “AI inside the app” and Atom’s connectors solve the same user need from opposite directions: Notion’s agent lives inside Notion; Atom’s agent lives with you and reaches Notion (or any service) through a connector you control.
Connect a private calendar URL (WebCal/ICS) in Settings → Connectors. Your agent can read events to help with scheduling — without giving Atom your Google password in the browser.
Discover businesses and people, exchange encrypted messages, scheduling proposals, and RSVPs — the “social” layer of the agent web.
Direct OAuth links (Google Calendar, Notion, email) and a public connector catalog are rolling out as the platform matures. Each new connector follows the same vault-first pattern.
Connectors are published packages — like modules, but for live services instead of on-screen widgets. If you maintain an API or run a business agent, you can ship a connector so any Atom user can link your service safely.
Create a free hosted account, open Settings → Connectors, and link your first calendar feed. Ask your agent what’s on your schedule — or message a business peer and watch agents coordinate.