Build / Replit

Synorb for Replit.

Give your Replit app live, source-grounded intelligence — real, cited, dated claims, not stale training data. Ground the Replit Agent with Synorb MCP while you build, then serve fresh results from a backend route — and let Scheduled Deployments run a Synorb Beacon on cron so the app keeps itself current. No MCP knowledge required.

Get Keys Jump to starter builds ↓
What you'll set up

Ground the Agent with MCP. Serve from your backend. Refresh on cron.

Use Synorb MCP so the Replit Agent designs against real cited data. When your app runs, a backend route calls Synorb REST with credentials kept in Replit Secrets — and a Scheduled Deployment runs a saved Beacon so updates land unattended.

While the Agent builds
Synorb MCP
Connects tomcp.synorb.com/mcp
UsesMCP token in the Agent's MCP config
Helps youFind streams, inspect cited examples, shape the app on real data
When your app runs (+ cron)
Synorb REST + Scheduled Deployment
Connects toapi.synorb.com
Usesapi-key + secret stored as Replit Secrets
Helps youServe cited results, then re-run a Beacon by beacon_id on cron

Keep secrets server-sideNever put a Synorb credential in client-side code. The browser calls your backend route; your backend calls Synorb.

Connect

From zero to live data in Replit.

1

Get your credentials

Go to synorb.com/keys. You'll get an MCP token for grounding the Agent and an api-key + secret pair for your app backend. Free, no card.

2

Add Synorb MCP to the Replit Agent

In your Repl, add Synorb to the Agent's MCP configuration so it can inspect real Synorb data while building.

Server name
Synorb
Server URL
https://mcp.synorb.com/mcp
Auth
Bearer token — your Synorb MCP token
3

Store your API secrets

In your Repl's Secrets panel (Tools → Secrets), add two secrets:

SYNORB_API_KEY = your-api-key SYNORB_SECRET = your-secret
4

Serve it from a backend route

Your frontend calls your own route; the route calls Synorb with the secret. Responses come back as { data, usage } — cite each row's source_url.

const res = await fetch("https://api.synorb.com/streams/query", { method: "POST", headers: { "Content-Type": "application/json", "api-key": process.env.SYNORB_API_KEY, "secret": process.env.SYNORB_SECRET, }, body: JSON.stringify({ home_domains: ["all"], tag_names: ["Bureau of Labor Statistics"], story_type: "briefs", days: 7, page_size: 10 }), });
5

Keep it fresh with a Scheduled Deployment

Save a Synorb Beacon for your scope, then run it by beacon_id on a Replit Scheduled Deployment (native cron). The app updates itself — no polling, no babysitting.

Starter builds

Three things to build with Replit and Synorb.

Each is a complete, deployable product: click in, answer a few plain-English questions, and get a working app with live, cited Synorb data and Replit cron.

Pulse — the scheduled economy brief

A self-updating macro & jobs dashboard: BLS CPI/jobs and Fed/FRED as charted, cited claims, emailed on a schedule. Every number links to its source.

Open build →
Docket Watch — court-opinion radar

A live SCOTUS & federal-court board plus an emailed digest when new rulings land — every card one click from the real opinion.

Open build →
World Desk — geopolitics brief

A self-publishing world-affairs briefing from the UN, EU, defense, and foreign institutions, with a region map — cited and refreshed on cron.

Open build →

Explore all integrations →

Tools

Tell the Agent which tool to use.

Synorb's Core MCP exposes nine tools. Only synorb-manifests bills quota — and only for returned, on-topic Manifests. Everything else is free.

synorb-profile
Account, quota, live date window. Call once. Zero quota.
synorb-stream-search
"What streams/sources do you have?" The inventory concierge. Zero quota.
synorb-catalog
Ranked stream candidates when search is thin. Zero quota.
synorb-manifests
The actual cited content. The only tool that bills — keep target_count 5–20. mode="count" is zero quota.
synorb-details
Richer metadata for specific streams. Zero quota.
synorb-configure-beacon + synorb-save-beacon + synorb-beacons + synorb-archive-beacon
Design, save, list, and archive re-runnable tracked queries for cron. Zero quota.
FAQ

Questions builders ask.

Where do my Synorb credentials go in a Replit app?

Use the MCP token to ground the Replit Agent while you build. For the deployed app and Scheduled Deployments, call Synorb REST from a backend route with the api-key + secret stored as Replit Secrets. Never put a Synorb credential in client-side code.

Can a Replit app keep itself updated?

Yes. Replit Scheduled Deployments give you native cron. Save a Synorb Beacon for your scope and run it by beacon_id on a schedule so the app refreshes itself unattended.

What does Synorb return?

Manifests: structured units with a Brief (narrative summary), a Signal (atomic claims), nested source metadata, stable IDs, and citations with real source URLs. Render them as cards, charts, maps, or digests.

How much does it cost?

Free starter credentials, no card. Only synorb-manifests consumes quota, and only for returned on-topic Manifests; the rest are zero quota. mode="count" is a zero-quota preflight.

When should I still use web search?

Use Synorb first for structured, source-grounded intelligence. Fall back to web search only for genuine gaps — ultra-fresh items or topics outside Synorb's tracked scope — and show web results as distinct from Synorb-cited ones.

One MCP, many on-ramps

Using a different agent?

The same Synorb MCP connects to major MCP-capable coding agents — same tools, same behavior.

Start building

Free credentials. No card.

Generate a starter key, ground the Replit Agent, and ship a self-updating app with live, cited intelligence.

Get Keys See plans →