API & MCP
The relationship and context graph, as an API and MCP server.
Read and write your tenant’s people, companies, deals, notes, tasks, activity, and relationship intelligence. REST or MCP, your team or your agents, one API key.
100 intros surfaced a day
100K contacts, one watchlist
<1 hr to connect
recommended-paths
$ GET /v1/companies/{uuid}/recommended-paths
{
"results": [{
"name": "Sarah Chen",
"relationship_quality": 3,
"path": ["Sarah Chen", "David Park", "Acme Capital"]
}],
"top_external_contacts": [ ... ]
}
THE API
One key. Everything your team knows about a relationship.
Eight resources cover everything your company knows: people, companies, deals, notes, tasks, activity, meetings, and your team. One API key, scoped to what each user can already see, whether a person or an agent is asking.
PERSON
Everyone your team emails and meets. Look up by email, LinkedIn, or domain; create without duplicates.
GET POST PUT /v1/persons
COMPANY
Organizations, resolved by domain or LinkedIn, with the right people attached.
GET POST PUT /v1/companies
OPPORTUNITY
Your live pipeline, with your own types, stages, custom fields, and sub-deals.
GET POST PUT /v1/opportunities
NOTE
Meeting notes and transcripts. Write follow-ups back; search them semantically.
GET POST PUT DEL /v1/notes
TASK
Create and assign action items with due dates and reminders, straight from an agent.
GET POST PUT DEL /v1/tasks
ACTIVITY
The full email and meeting history behind every relationship, down to the message thread.
GET …/activities · …/activity-stats
MEETING
What’s on the calendar and who was in the room. Filter by person, company, or date.
GET /v1/meetings
USER
Your team’s directory, plus /me, so an agent can resolve “I” before it asks anything else.
GET /v1/users · /v1/me
Every list paginates and filters. Batches take up to 100 records per call and are safe to re-run; matching and idempotency keys prevent duplicates. Errors are typed JSON, and every schema lives in the OpenAPI document. Read-first by design: writes are scoped, and people, companies, and deals can never be deleted through the API.
THE INTELLIGENCE
Four answers your CRM was never going to have.
A CRM only knows what someone typed in, and most email and meetings never get typed in. Rings reads the calendar and inbox directly, so these four answers come straight from the source.
PATHPOWER®
One number for how well your firm knows anyone, with a plain-language strength band. Score a whole watchlist in one call.
GET …/pathpower · /v1/pathpower/scores
PATHS
The warmest way in — ranked contacts and the people in between, so an intro lands where a cold email can’t.
GET …/recommended-paths
AI SUMMARY
A structured briefing on any person or company, ready when you ask. No prompt to engineer.
GET …/ai-summary
HISTORY
Every email sent and meeting held, captured at the time — the record is what happened, not what got typed in.
GET …/activities · …/activity-stats
Day to day you live in four ideas: who you know, how strongly, who can introduce you, and what’s happened. All four are one tool call away, for your team and your agents.
ARCHITECTURE
Sources in. API and MCP out. Data stays where it lives.
Rings ingests via scoped OAuth, unifies into a tenant-isolated graph, and serves over REST and MCP. It doesn’t replace your CRM — it completes it.
60+
operations, read + write
1
API key, every consumer
0
writes back to your sources
SOURCES
Your data
Email + calendar
Microsoft 365 · Google Workspace — every thread and meeting
CRM records
Salesforce · Dynamics — accounts, contacts, deals
Each user’s own export — profiles, titles, moves
OAuth 2.0 · read-only · scoped
THE PLATFORM
Rings Platform
Tenant-isolated relationship graph
Resolve
One identity per person and company, across every source
Score · PathPower®
Relationship strength, per person and company — or a whole watchlist in one call
Paths
Ranked warm intros — and the people in between
Summarize
AI briefs on any person or company, ready when you ask
Search
Semantic + keyword search across notes and transcripts
Analyze
Activity analytics — every email and meeting, as it happened
Enrich
200M+ external datapoints layered onto the graph
CONSUMERS
Served over REST and MCP
Person
Company
Opportunity
Note
Task
Activity
Meeting
User
REST API
APPS + PIPELINES
Read and write the full graph, one record or a hundred at a time. Every response is scoped to the user behind the request.
Salesforce / Dynamics embeds
PathPower® + warm paths, rendered on the CRM record
Internal web + mobile apps
The graph behind your own product screens
Snowflake / Databricks pull
Nightly extracts into the warehouse BI already reads
Compliance + BI dashboards
Read-only reporting, straight off the graph
MCP server
AGENTS
The same graph, tool-shaped and ready for whatever agent your firm runs.
Claude / ChatGPT Enterprise
The graph inside the assistants your firm already runs
Your firm-built copilot
The same tools, called from agents you own
Tools generated from the API
recommended-paths, pathpower, ai-summary — and everything else in the API
Per-user answers
Every tool can answer as the person asking, not just the firm
AUTH
single API key
user-scoped requests
OAuth 2.0 — MCP acts as the signed-in user
Every consumer reads the same graph
Same rules for people and agents, over REST and MCP.
EVERY CALL
Authenticated to one tenant
Every key maps to exactly one tenant, enforced server-side
OPTIONAL
Act as a user
Scope any request to a single user and every answer narrows to their view
ON READS
Bounded reads
Nothing beyond what the acting user can already see
ON WRITES
Bounded writes
A write can’t exceed the acting user — even when an agent writes
USE CASES
What relationship-driven companies actually run on it.
Nine workflows from deployments and active builds at relationship-driven companies, from banks and funds to wealth and advisory teams. Three are live today, and each cites the tools an agent can call.
LIVE
Weekly signals → warm-path scan
Funding and job-change signals, paired with ranked internal paths across offices. Around 100 precise intros surfaced a day.
TOOLS
lookup · recommended-paths
LIVE
Team prospect watchlist
A shared 100K-contact watchlist with PathPower® on every row. Producers work the top of the list each morning.
TOOLS
pathpower · lookup
LIVE
CRM account-page embed
PathPower and warm paths rendered inside Salesforce and Dynamics records. Zero context switching for the team.
TOOLS
pathpower · recommended-paths
MCP
AI assistants that know the firm
Your firm’s own copilot answers “who on the team knows the CFO at this target?” on day one, over MCP.
TOOLS
recommended-paths · pathpower
CONTINUITY
Producer departure response
The moment a producer gives notice, surface the second-strongest internal connection to every client they touch — before the client calls.
TOOLS
recommended-paths · activities
COVERAGE
Coverage gap analysis
Against any target universe, surface every account where the firm has gone silent, ranked by who holds the warmest path to re-engage.
TOOLS
activities · recommended-paths
SOURCING
Two hops from any target
A new opportunity lands: who is one or two hops from this founder, CFO, or board member? Paths ranked, not guessed.
TOOLS
lookup · recommended-paths
EVENTS
Conference + event prep
Attendee list in, warm-path map out. Batch-resolved without duplicates, with a meeting-request sheet ranked by path strength.
TOOLS
lookup · persons · recommended-paths
AGENTS
Meeting prep → follow-through
An assistant preps each meeting from the graph, then captures commitments as tasks and notes, tied to the right people and deals automatically.
TOOLS
meetings · ai-summary · tasks · notes
Nine more workflows live in the technical addendum, from advisor succession and LP fundraising intelligence to mandate staffing, referral attribution, and agentic pipeline hygiene. Ask for it.
INTEGRATIONS
Wired into the stack you already run.
Read and write, permission-scoped. Creates, updates, and scoped deletes, each bounded by what the acting user can already do in Rings.
User-scoped requests. Ask as any user: “who do I know,” not just the firm.
Connect in minutes. Point any MCP-compatible agent at the server with an OAuth 2.0 sign-in; there’s no custom retrieval layer to build.
AGENT TOOLS — GENERATED FROM THE API
recommended-paths
Ranked warm paths to any target
pathpower
Strength scores for one target or a hundred
ai-summary
Structured briefs on any person or company
search-notes
Semantic search over notes + transcripts
activities
Email + meeting history
notes · tasks
Write follow-ups and action items back
opportunities
Update pipeline fields
…the full API
Every tool maps 1:1 to an operation
SECURITY & GOVERNANCE
Controls grounded in the production API spec.
None of this is aspirational; it’s how the API behaves, documented in the reference.
Permission-scoped and tenant-scoped, by default.
Auth
API-key auth, per-user scoping
Every request authenticates with a single API key
Tenant keys can act as a specific user, scoping any request to that person
User-scoped keys stay permanently bound to a single person
MCP uses OAuth 2.0, so AI tools act as the signed-in user, inside their permissions
Source systems connect via scoped, read-only OAuth 2.0
Isolation
Tenant-level data partitioning
Each key is scoped to exactly one tenant, enforced server-side
User and relationship lists return only your tenant’s data
Per-user email access control, with grants and explicit permission enforced at the endpoint
Encrypted in transit (TLS 1.2/1.3) and at rest
Writes
A write can’t exceed the user
Every create, update, and delete, whether from a human or an agent, is bounded by the acting user’s permissions
Deletes are scoped to notes, tasks, and associations; people, companies, and deals can never be destroyed through the API
No write path escalates beyond the key’s own grants
Source ingestion stays read-only, with nothing written back to email or CRM
SOC 2 Type II
EU–U.S. Data Privacy Framework
Encrypted in transit + at rest
Full OpenAPI spec
Security questions? Our team works directly with your InfoSec and procurement teams. SOC 2 audit available on request.
Point your agents at the graph.
One key gets you every person, company, deal, and warm path your company knows. REST for the software you build; MCP for the agents you run.