Access

One Synorb Key works for MCP and REST. Keep it in your agent's secure settings, never in a chat or a URL.

One active key at a time. Issuing a new key immediately revokes your current one.

Agents that connected through OAuth: what each can do, and what it has read.

Profile

Integrations

Synorb already works in all of these through MCP. Native, one-click access points are in progress.

Catalog

Pick a surface or search by name. Copy a question so your agent checks what a stream covers right now, or open it in Studio.

Digest Builder

Group streams into a Digest your agent queries as one source. Rules choose the streams; new Manifests join the Digest as they are routed.

Synorb Digests

Synorb Digests are sets of streams curated by Synorb. Add one to your organization and your agent reads it as a single source; the Enterprise plan includes them.

Added Digests

The Synorb Digests your organization has added. Remove one here; it stays listed under Synorb Digests.

Plan & usage

Your workspace owner manages billing and plan changes.

Firehose

Studio / Connect

Studio / Manifest Explorer

A Beacon is a saved Manifest query your agent can ping on demand or schedule from your own runtime. Use its beacon_id from cron, Airflow, Temporal, or another scheduler — Synorb does not host production cron. Beacons cover podcasts, corporate blogs, filings, official announcements, newsletters, research, and other source channels.

Help & Docs

The reference for connecting an agent, querying over MCP and REST, and managing your account.

Archive exports

An archive export is one file per public stream holding every Manifest published in the period you buy: the Signal and Brief for each, plus the Record where your plan includes Records. Exports sit outside your monthly Manifest usage allowance. Once payment clears you have 30 days to download; purchases are final. Pay by ACH or wire.

Identifier mappings

A sync pairs a Synorb tag, topic or stream with the identifier your own systems use. Stream Signals and Briefs fetched over REST then carry that identifier and your labels on each tag.

Loading...

You:   "Sync Tesla to CRM-TSLA-001 and label it buy-side"
Agent: → synorb-tags("Tesla", type="organization")
       → synorb-sync(object_id=1234, external_id="CRM-TSLA-001",
           external_name="Tesla Corp", labels="buy-side")
       → "Done. Tesla synced to CRM-TSLA-001 with label buy-side."

You:   "Show me what I have synced so far"
Agent: → synorb-syncs()
       → "You have 12 active syncs across 3 labels."

pip install synorb

from synorb import Synorb

client = Synorb(
    synorb_key="YOUR_SYNORB_KEY"
)

# Search by name and type
results = client.ontology.search("Tesla", tag_type="organization")

for tag in results:
    print(f"{tag.id}: {tag.name} ({tag.type})")
    print(f"  {tag.claim_count} claims, aliases: {tag.aliases}")

# Create a sync
client.ontology.sync(
    tag_id=1234,                       # Synorb tag ID
    external_id="CRM-TSLA-001",        # Your internal ID
    external_name="Tesla Corp",        # Display name (optional)
    labels=["watchlist", "buy-side"]   # Your labels (optional)
)

# List all syncs
for s in client.ontology.syncs():
    print(f"{s.tag_name} → {s.external_id} [{', '.join(s.labels)}]")

# Remove a sync
client.ontology.unsync(tag_id=1234)

# Create labels
client.ontology.create_label("buy-side", group="portfolio")
client.ontology.create_label("short", group="portfolio")
client.ontology.create_label("competitor", group="market")

# List all labels
for label in client.ontology.labels():
    print(f"{label.name} (group: {label.group})")

Loading the preview…