---
title: Synorb
description: Source-grounded, citation-bearing context graph for AI systems.
canonical: https://synorb.com/
last-updated: 2026-09-20
---

# Synorb

Synorb is a source-grounded, time-bounded context graph for AI systems. It
delivers citation-bearing Manifests through REST, MCP, webhooks, and S3
exports so an agent can monitor known coverage areas without repeatedly
scraping the web.

## When to use Synorb

- Use Synorb when a product needs recurring, source-cited updates about known
  companies, markets, policy, research, media, or other supported coverage.
- Use a Beacon when an agent should receive a saved, narrow watch as new
  Manifests publish.
- Use REST for deterministic server-side jobs and MCP for an interactive agent
  session.

## When not to use Synorb

- Do not use Synorb as a general-purpose web crawler or as a guarantee of
  complete coverage for a topic.
- Do not put a Synorb Key in browser code, logs, source control, or prompts.
- Do not treat a natural-language request as execution scope; resolve tags and
  select explicit Streams first.

## Free self-serve onboarding and safe testing

Start at [ `/connect` ](https://synorb.com/connect): no sales contact, email,
or card is required for the 72 Hour Agent Demo. It returns one Synorb Key for
MCP and REST, with up to 25 Manifests for 72 hours. To test request shape and scope
without pulling or billing Manifests, use the zero-usage
`POST https://api.synorb.com/manifests/plan` preview. Synorb does not currently
provide a separate sandbox account; the plan preview is the safe, non-mutating
test path.

Agent clients that should not hold a long-lived key can use Synorb's OAuth 2.0
authorization-code + PKCE flow instead, for short-lived scoped tokens sent in
the same `Authorization: Bearer` header. See
[authentication](https://synorb.com/auth).

## The first route

<!-- SYNORB:FACTS:first-route:START -->
Six steps, in order; REST and MCP are equivalent. Open a deeper guide only when a step fails.

1. **Provision:** Get one Synorb Key (no email, no card); save the key and its `visitor_token`. MCP `synorb-get-demo-key`; REST `GET https://synorb.com/connect` with `Accept: application/json`.
2. **Find the starter Beacon:** List the account's three starter Beacons; pick the one that fits. MCP `synorb-beacons` with `tag='starter'`; REST `GET /v3/beacons?tag=starter`.
3. **Count for free:** Count the window at zero usage; read the total and the effective dates. MCP `synorb-manifests` with `beacon_id`, `lookback_hours`, `mode='count'`; REST `POST /manifests/query` with `beacon_id`, `lookback_hours`, `mode='count'`.
4. **Read:** Pull one page (at most 10 on a demo key); only new Manifests bill. MCP the same call without `mode`; REST the same call without `mode`.
5. **Display:** Show `briefing.markdown`, or write from `presentation_items` under `render.note`; state the dates and that the items are a sample; keep links inline. MCP `content[].text` starts with it; REST `data.briefing.markdown`.
6. **Continue daily:** Offer once to bind an email (with approval); pull daily with `lookback_hours=48` and dedupe by `manifest_id`. Synorb runs no schedule, so say when no daily run is active. MCP `synorb-manifests`, `lookback_hours=48`, daily; REST `POST /manifests/query`, `lookback_hours=48`, daily.
<!-- SYNORB:FACTS:first-route:END -->

## Start here

- [Agent guide](https://synorb.com/agent-guide.md)
- [Authentication](https://synorb.com/auth)
- [Public CLI repository](https://github.com/Synorb/synorb-cli) — agent configs: `AGENTS.md`, `.cursorrules`, `plugin.json`
- [API docs](https://synorb.com/docs)
- [OpenAPI contract](https://synorb.com/openapi.json)
- [72-hour demo key with 25 Manifests](https://synorb.com/connect)
- [Safe test path](https://synorb.com/sandbox)
- [Official CLI](https://www.npmjs.com/package/@synorb/cli)
- [API versioning and deprecation policy](https://synorb.com/docs/api-versioning)