One API across your GTM stack
Connect your CRM, inbox, calendar and call recorder once. Read every customer through one endpoint.
Works for every customer, in every tool
Five records in five tools. OpenNous resolves them to one person, even if they changed their email, were never added to your CRM, or the call was recorded somewhere else.
Doesn’t need a clean CRM to work
Duplicates, missing owners and stale rows are fine. No schema to design and no cleanup first.
Save months of data engineering
Connectors, identity resolution, extraction and freshness are already built, and already maintained.
Get a whole account with a single call
1 $ curl https://api.opennous.cloud \ 2 /v2/accounts/acme.com \ 3 -H "Authorization: Bearer $KEY"
- Works with a domain, an email, a LinkedIn URL or an ID.
- An ambiguous match returns the candidates, never a guess.
- People, deals, ICP score and activity in one response.
Replied to email · 24 Sep“Thursday works. Can you bring pricing for 40 seats?”Every fact with its source, date and confidence
1 "facts": [{ 2 "category": "Budget", 3 "content": "Budget approved for Q4.", 4 "quote": "We have the budget signed off.", 5 "speaker": "Sarah Chen", 6 "source": "fireflies", 7 "date": "2026-09-24" 8 }]
- The quote and the speaker behind every fact.
- A confidence score and freshness on every claim.
- Facts that go out of date are marked stale.
Discovery call · 24 SepTom 14:02
Security review is the last step on our side.
Sarah 14:03
We have the budget signed off for Q4.
Budget approved for Q4, owned by the CRO.
Context shaped for your agent
1 $ curl -X POST https://api.opennous.cloud \ 2 /v2/context -d '{ 3 "focus": "sarah@acme.com", 4 "intent": "meeting_prep" }'
- Five intents, from account review to meeting prep.
- Ranked and cut to your token budget.
- The same context in Claude over MCP.
- Sarah Chen (VP Sales) signs. Budget is approved for Q4.
- Tom Becker wants the security review done first.
- Open ask: pricing for 40 seats.
Account events, pushed over webhooks
1 { 2 "type": "deal.stage_changed", 3 "account": { "domain": "acme.com" }, 4 "stage": "proposal", 5 "changed_at": "2026-10-01T14:02:00Z" 6 }
- Deal, reply, meeting and ICP tier events.
- Every payload signed with HMAC-SHA256.
- A test event and a delivery log for every endpoint.
Frequently asked questions
What is a unified accounts API?
An API that returns one resolved record per customer, built from every tool your team uses. Each fact in the record carries the source it came from, its date and a confidence score.
What can I build with the Unified Accounts API?
Anything that needs to know a customer: sales agents, meeting prep, follow-up drafting, CRM updates, account scoring, customer success alerts and internal copilots.
Which tools does it connect to?
HubSpot, Salesforce and Attio for your CRM. Gmail, Outlook and Google Calendar. Granola, Fireflies and Fathom for calls. Slack, and PostHog for product usage.
Why use a unified accounts API rather than build your own?
Building it means syncing a dozen tools, resolving the same person across all of them, extracting facts from calls and emails and keeping those facts current. That is months of work, and it never ends. The API gives you the finished record.
How do I get an account?
Call GET /v2/accounts with a domain, an email, a LinkedIn URL or an ID. If the identifier matches more than one account, you get the candidates back instead of a guess.
How does it know two records are the same customer?
It matches emails, domains, LinkedIn profiles and CRM IDs first, then names only when another detail confirms them. When the evidence isn’t strong enough, the match is flagged for a person to confirm.
How current is the data?
Records update as new calls, emails and CRM changes arrive. Paid plans also import the last three months of history on day one.
How do I get notified when an account changes?
Subscribe to webhooks. Events cover deals, replies, meetings and ICP tier changes, and every payload is signed.
Can AI agents use the same accounts?
Yes. Claude, Claude Code and Slack read the same records over the OpenNous MCP server, and your own agents use the API, with the same permissions as your team.
How is customer data kept private?
Raw emails, calls and messages are visible only to the person they belong to. The API returns the business facts extracted from them, such as the decision maker or the agreed next step, with their source and date.
Can I self-host it?
Yes. OpenNous is open source. You can run it on your own infrastructure and take your data with you.
How do I try the Unified Accounts API?
Sign up for free and create an API key in Settings, or talk to us and we’ll set it up on your own accounts.
