SAGARIS Documentation
Build on the SAGARIS revenue engine
Guides, concepts, and API reference for the Company Brain, agents, and every channel.
The Company Brain
The Company Brain is the shared memory that every SAGARIS agent reads from and writes to. One record of truth across calls, email, SMS, and pipeline, so context never lives in a single channel again.
Every agent inherits the caller's permissions. The Brain resolves access at query time, so agents only ever see what the user is cleared to see.
How context is written
Activity is captured automatically as it happens. When a call ends, a message sends, or a meeting is booked, the event is normalized and written to the account record with its source attached, no manual entry required.
curl https://api.sagaris.ai/v1/brain/context \ -H "Authorization: Bearer $SAGARIS_KEY" \ -d '{ "account_id": "acc_vertexa", "event": "call.ended" }'Reading the Brain
Agents query the Brain the same way the API does. Ask for an account and you get the resolved record: the latest touch on every channel, the open threads, and the signals that changed the deal, already scoped to the caller's permissions.
curl https://api.sagaris.ai/v1/brain/context/acc_vertexa \ -H "Authorization: Bearer $SAGARIS_KEY"Permissions
Access is part of the memory, not a filter applied afterward. Every read resolves against the caller's clearance at query time, so an agent acting for a rep sees exactly what that rep would see, no more and no less. There is no separate access list to keep in sync.
Related
Was this page helpful?
In this topic
Developers and integrations
- IntegrationsWhat SAGARIS connects to, and in which direction.
- The SAGARIS MCP serverYour CRM and Brain in your AI assistant, with scoped Social drafts and gated LinkedIn actions.
- IntroductionWorkspaces, autonomy levels and outbound holds.
- QuickstartFrom sign-in to your first play, as a checklist.
- API authenticationAPI keys, the twelve scopes, and what gets rejected.
- REST API referenceThe API operations, their scopes and the gates they pass.
- WebhooksThe webhook events, HMAC signing and dead letters.
- Rate limitsThe write and MCP request limits, per minute.
- SDKsNo official SDK, and how to generate one from the OpenAPI spec.
- HubSpot integrationHubSpot reads are live; write-back is a dry run.
- Salesforce integrationSalesforce reads are live; write-back is switched off in production.