Maya Okonkwo
Partner, Ridgeline
Backed two of your portfolio founders. Warm via Tim H.
Mutuals: Tim H. +3
AgentIntros gives your agent standing access to your network. The moment it needs a warm path, it has one — it finds the route, drafts the ask with real context, and sends it to you to approve. Your network, on call. You, still in charge.
Live agent panel
Partner, Ridgeline
Backed two of your portfolio founders. Warm via Tim H.
Mutuals: Tim H. +3
Angel, ex-Stripe
Met at SaaStr '24; replied to your last email.
Mutuals: direct
Draft ready
Reviewing
Your network
Connect Gmail, Calendar, contacts, LinkedIn, and X. AgentIntros unifies them into a single relationship graph — enriched, scored, and ready the instant your agent asks. No exports, no re-syncing, no search box to open.
Gmail
Calendar
Contacts
X
Product primitives
Every intro is a durable object that moves through a lifecycle: request, match, approval, send, follow-up, outcome. Your agent can reason over each stage. You stay in control of the one that matters most — approval.
Your agent doesn't open an app or wait for a sync. The graph is there the moment it's needed, every session it runs.
Capture who an agent wants to reach, why it matters, and exactly what context is safe to share.
People, companies, communities, and past touchpoints, modeled as the routing context behind every warm path.
Review queues, approver notes, and explicit send-ready calls. Nothing leaves until a person signs off.
Acceptance, timing, nudges, and outcomes. Intros don't vanish after the first message.
Typed primitives for matches, approvals, events, and lifecycle status, designed to code against. Direction, not yet live.
Use cases
AgentIntros is for teams who need more than lead scoring. Agents surface the connections worth making — with the context to back them — without ever stepping over the people who actually hold the trust.
Integrate with your agent
Start with the CLI today. The SDK, MCP server, and typed events are where the surface is headed — so any agent you run can reach your network without glue code. Add the MCP server once, and your network becomes a standing tool in every session.
Only the intros CLI is live today. The MCP server, SDK, and typed events are future-facing product direction.
npm install -g intros
intros new "Investor Intro Agent" --role "Warm intro router"{
"mcpServers": {
"agentintros": {
"type": "url",
"url": "https://agentintros.ai/mcp"
}
}
}import { AgentIntros } from "@agentintros/sdk";
const client = new AgentIntros();
const request = await client.introRequests.create({
for: "Founder raising seed",
target: "fintech investors",
context: "traction, deck, warm path",
approval: "human_required",
});
await client.matches.list({ requestId: request.id, minTrustScore: 0.82 });Also works in
Claude · Claude Code · Cursor · ChatGPT · any MCP client
Workflow templates
Reads a founder update, finds the likely warm paths, drafts the context, and queues it for approver review.
Maps a partner ask to the right operator, company, or ecosystem node before proposing the intro.
Turns agent-suggested connections into clear approve, edit, defer, or decline decisions.
Keeps the loop alive with status checks, handoff reminders, and outcome capture.
Search tools wait for you to open them and type a query. AgentIntros gives your agent standing access, so it can find and propose intros while it works — and route every one to you for approval. The agent reaches in; you stay the gate.
No — it's the opposite. Agents handle the discovery and the drafting; people make the call. Trust never gets automated into spam.
Not yet. This site lays out the product direction. The docs, examples, and `intros` CLI are real and usable today; the hosted API is not.
The published `intros` package lets you create agent intro briefs locally right now. Everything else — SDKs, MCP tools, hosted approvals — builds outward from that entry point.