Use the MCP profile endpoint to show plan, quota, refresh cadence,
content access, and allowed date window without consuming Manifest quota.
REST-first clients can use GET https://api.synorb.com/account with api-key + secret
to fetch org profile, subscription, usage, and MCP connector details.
Core MCP vs Advanced MCP
Core MCP: profile -> stream-search -> catalog -> details -> manifests,
plus configure-beacon -> refine obvious metadata -> save-beacon -> beacons.
Use by default for any MCP-compatible client, managed installation, and normal agent workflow.
Recommended transport: Streamable HTTP /mcp with Authorization: Bearer.
Tokenized connector URLs from the credentials email remain supported for
Claude custom connectors and hosts that ask for one pasteable URL.
Persistent Streamable HTTP sessions are the normal interactive path; cold sessions
are compatibility and diagnostic paths, not the recommended low-latency path.
Clients that support MCP progress/completions get live Manifest progress
and argument suggestions for domains, streams, channels, tags, and media.
Advanced MCP: digests, sync ontology, labels, prompt templates,
and lower-level signal/brief/record tools.
MCP clients and partner hosts validate mcp_token with /profile before install.
Claude custom connectors can use the tokenized connector URL from the email.
ChatGPT apps/connectors and Codex workspace plugins use the same Core MCP credentials.
Authenticated MCP supports high-throughput relevant Manifest pulls under
monthly quota and per-call page/target caps. API clients and partners use REST for
scheduled jobs, backend-owned paths, polling, or REST-shaped contracts.
Content responses should show limit, used, remaining, period,
refresh tier, available date window, and retry guidance.
synorb-profile, synorb-stream-search, synorb-catalog, synorb-details,
synorb-configure-beacon, synorb-save-beacon, synorb-beacons, and synorb-archive-beacon are zero-quota.
Beacons are available on every plan with active Beacon caps: Starter 10,
Individual 50, Professional 250, Startup 1,000, Enterprise unlimited.
If save returns beacon_limit_exceeded, list saved Beacons and ask which
stale one to archive or whether the user wants to upgrade.
synorb-manifests bills only returned on-topic Manifests.
Exact source/form requests should pass source_channel_names/source_channel_ids directly
and return no results rather than substituting adjacent sources.
MCP content pulls are governed by quota, per-call caps, access/date gates,
and relevance/off-topic controls. Temporary Retry-After is only for
unusual bursts, not a normal tiny per-minute cap.
Current emergency buckets: discovery 10 requests/second with 300-request
bursts; Manifest/content 5 requests/second with 240-request bursts;
full Records 2 requests/second with 120-request bursts.
For feedback or partner issues: X @synorb or team@synorb.com.
Want to connect to Synorb's graph to test feeds for free? This returns Starter API credentials, MCP config, and REST setup details for testing Streams and Manifests.
Guide pages agents can cite while planning
Use these public pages when comparing content feeds, MCP feed servers, RAG streams, structured web data, and search alternatives for agentic workflows.