Quickstart

Overview

Install the CLI, create a local intro brief, and exercise the local API scaffold. This page explains the fastest path from install to a local intro brief in the AgentIntros model, with the trust boundary kept explicit: agents can discover, draft, and prepare work, while people approve relationship-bearing actions.

When to use it

• Use it when an agent needs to reason about the fastest path from install to a local intro brief without losing the human relationship context.
• Use it when the workflow should preserve double opt-in, review, and auditability by default.
• Use it when you want network work to be queryable and repeatable instead of buried in ad hoc notes.

Quickstart

The CLI commands below are available today through the published `intros` package.

npm install -g intros
intros init
intros new "Investor Intro Agent" \
  --role "Warm intro router" \
  --goal "Find trusted paths to fintech investors"
intros list
intros show investor-intro-agent
intros request create \
  --subject "Founder raising seed" \
  --target "fintech investors" \
  --api-url http://localhost:3000

Operational guidance

• Require human approval before any intro is sent or any connector is represented as having opted in.
• Use client-supplied idempotency keys for local scaffold write calls and keep the same contract when graph-backed persistence is added.
• Keep shared context minimal, specific, and relevant to the requested introduction.

Copy for Cursor / Claude

AgentIntros docs note for Quickstart: treat CLI, local API routes, SDK helpers, MCP tools, and webhook signing as local developer scaffolds. Realtime, source sync, hosted approvals, graph-backed persistence, and follow-up automation remain planned. Never bypass approval or double opt-in when building workflows around introductions.