Your users’ conversations. One permissioned stream.
Attrove syncs and normalizes each user’s email, chat, calendar, meetings, and partner-supplied context. Your product gets scoped records, cited retrieval, and durable watched state behind one data model.
The hard part starts after the connector works.
Production communication needs durable sync, user isolation, clean threads, entity resolution, citations, and state that survives the next request.
Attrove handles user-scoped OAuth, durable sync, normalized threads, entity resolution, source citations, and watched state.
User-approved inputs become one normalized stream.
Email, chat, calendar, meetings, and signed push context flow through Attrove to sync and normalize records, resolve threads and entities, retrieve with citations, and watch durable state.
Your product reaches the same data model through the SDK, REST API, MCP server, or signed webhooks.
One stream. Use the surface that fits.
SDK, REST, MCP, and webhooks share the same user scope, source records, citations, Goals, and Commitments.
- TypeScript SDK: typed helpers for query, search, Goals, and Commitments.
- REST API: direct control from any server, runtime, or language.
- MCP server: the same user-scoped records and primitives as agent tools.
- Signed webhooks: source and watched-state changes without polling.
Durable state for the work between messages.
Use a Commitment when one expected signal should arrive. Use a Goal when an outcome needs evidence-based evaluation over time.
- Commitment: a promise, delegation, handoff, or wait with one expected signal and one time horizon. It is watching, at risk, or resolved.
- Goal: a named outcome over scoped communication, with system-computed health, cited snapshots, and a human-controlled lifecycle.
User-approved sources. Source-tied evidence.
Use read-scoped OAuth for live connectors. Add signed push context when OAuth is not the path. Microsoft Teams is currently in pilot.
- Gmail: threads and replies.
- Outlook: threads and shared inboxes.
- Slack: channels and DMs.
- Google Calendar: events and holds.
- Google Meet: transcripts and recaps.
- Microsoft Teams: chats and meetings in pilot.
- Push context: CRM, tickets, and internal events over signed REST.
The trust boundary stays visible.
- Per-user scope: records, queries, and watched state stay scoped to the connected user.
- Read-only by default: live connectors use read-scoped OAuth and never require mailbox passwords.
- Source-tied evidence: every answer can point back to the source record.
- Revocation: users can revoke access from Attrove or their identity provider.
SOC 2 Type I.
Connect one source. Ship the first useful signal.
The live product is available now. If you want help choosing the smallest production path, talk directly with Tim.