# Synorb agent guide: agent types, product builders, and the CLI

This page is part of the Synorb agent guide at https://synorb.com/agent-guide.md.
Which path fits each type of agent, how to build a product on Synorb, and the official CLI.

## Pick your path

Every agent uses Synorb the same way: one key, Manifests arrive, you pay per
item delivered. What differs is where you start.

**Personal agents** (assistants running one person's life or work - Instinct,
Muse, Town): be proactive. Use what you already know about your user to
propose one to three Beacons, each with a one-line reason. On a cold start,
offer the starter Beacons: AI Companies, Business & Technology Podcasts, and
Central Banks. Every account has all three.

Propose first; call `synorb-save-beacon` only after
the user says yes. After you answer a specific question, offer to save it as a
Beacon too. On-demand pulls from particular Streams are fine when the user asks.

**Coding agents** (builders that scaffold software - Replit, Lovable, Cursor,
Claude Code): you build a product on Synorb. You do not consume it yourself.
Start at https://synorb.com/agents/coding-agents. The single-shot prompts walk
you through key handling, density checks, and the scope receipt.

**Voice agents** (real-time conversation - Vapi, Retell, ElevenLabs): latency is
your constraint. One Manifest pull is a complete answer; never enter plan mode
mid-call. Keep scopes narrow. Hold one warm Streamable HTTP session at
`https://mcp.synorb.com/mcp`. Do not use the legacy `/sse` transport. It is
deprecated, and its sunset date is 2026-11-01.

**Cowork agents** (desktop knowledge-work agents - Claude Cowork, Perplexity
Computer, Operator): stay ambient. Let Beacons give you fresh context while the
human works. Cite the source URLs in whatever you draft.

**Vertical agents** (domain agents - sales, finance, legal, compliance): your
buyers audit provenance. Every Manifest carries its source URL. Billing is per
item delivered. Error states (rate limits, entitlement, expiry) are explicit,
so you can handle them in code.

## Product builders

Coding agents may use MCP to explore the graph while they build. A production
website or app pulls Synorb data from a server-side REST route. It keeps the
Synorb Key in the secret store of the deployment platform. It renders each
returned source citation, with source links near factual statements.

- Coding agent library: https://synorb.com/agents/coding-agents
- Lovable: https://synorb.com/agents/coding-agents/lovable-mcp
- Replit: https://synorb.com/agents/coding-agents/replit-mcp
- Cursor: https://synorb.com/agents/coding-agents/cursor-mcp

## Official CLI

The official CLI is `@synorb/cli` on npm. It supports `connect`, `profile`,
`stream-search`, `manifests` and `billing`. It emits JSON by default. It uses
the same REST JSON contracts as the API. It sends the Synorb Key only in the
`Authorization: Bearer` header. Use `SYNORB_TOKEN` in CI, or
`synorb connect --save` for a local config.

Content and discovery commands are read-only. `billing checkout` and
`billing portal` open a hosted Stripe handoff. An unattended agent must not
invoke them.

- npm package: https://www.npmjs.com/package/@synorb/cli
- Source: https://github.com/Synorb/synorb-cli
- CLI guide: https://synorb.com/docs/cli