0:50
Statehouse Signal
A 50-state policy signal room with issue filters, review state, official-source links, and scheduled delivery.
Built for: Government relations, public affairs, advocacy, policy research, and newsroom teams
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.
Replit build library
What can you build with Replit and Synorb?
Choose a real product, watch the short build video, and copy the complete one-shot prompt. Replit builds the product layer; Synorb supplies the current, structured, source-grounded content.
0:50
0:50
Exact-Source Policy Wire
A source-locked legal monitor with deduplication, review state, a delivery ledger, and Slack or email alerts.
Built for: Legal research, policy, court-reporting, and law-firm knowledge teams
0:57
Pulse
A live economic dashboard and scheduled morning brief with official charts, cited takeaways, and email.
Built for: Economists, finance leaders, investors, policy teams, and executive communications
0:57
Docket Watch
A cited federal-court opinion radar with filters, charts, review states, and a scheduled digest.
Built for: Litigators, legal researchers, court reporters, policy teams, and law-firm knowledge groups
0:57
World Desk
A map-forward geopolitical briefing with institution charts, regional sections, an archive, and scheduled publishing.
Built for: Geopolitical-risk, public-policy, defense, global-affairs, and executive-briefing teams
0:57
Podcast Wire
A searchable podcast intelligence app with Briefs, Signals, entity filters, real episode links, and a digest.
Built for: Research, communications, media, brand, investment, and podcast-intelligence teams
0:57
Content Feed
A hosted content product with rich Briefs and Signals, bookmarks, pagination, deployment, and scheduled refresh.
Built for: Product teams, community builders, SaaS founders, research teams, and niche publishers
No builds match those filters. Try a broader search or clear one filter.
One prompt. A few product choices. A working product powered by fresh Synorb streams.
Open the one-shot promptFor Replit builders
See what Replit builders can make with Synorb.
Browse real Replit products, one-shot prompts, videos, and a practical path from build-time discovery to secure runtime delivery.
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 to
mcp.synorb.com/mcpUsesSynorb Key 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 to
api.synorb.comUsesSynorb Key stored as Replit Secrets
Helps youServe cited results, then re-run a Beacon by
beacon_id on cronKeep 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.
Account ladder: DEMO — 1,000 Manifests, expires 24 hours after mint → Starter — free forever, 1,000 Manifests/month, after binding an email → Paid — $10/month, 10,000 Manifests/month.
Parse only credentials.synorb_key from the Connect response and read the top-level expires_at; surface that expiry to the user. Bind the email with POST https://api.synorb.com/api/connect/bind-email using Authorization: Bearer <synorb_key>. The same key keeps working. If DEMO expires, show Synorb key expired — bind an email or mint a new demo key and document the recovery path in the generated README and environment template.
1
Get your credentials
Go to synorb.com/connect. You'll get one Synorb Key for both the Agent and your app backend. Store the same value only in Replit Secrets. 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
- Authorization: Bearer your Synorb Key
3
Store your Synorb Key
In your Repl's Secrets panel (Tools → Secrets), add one secret:
SYNORB_KEY = your-synorb-key
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",
"Authorization": "Bearer " + process.env.SYNORB_KEY,
},
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.
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 Synorb Key to ground the Replit Agent while you build. For the deployed app and Scheduled Deployments, call Synorb REST from a backend route with the Synorb Key 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?
DEMO access is available without a 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.
Mint a DEMO key, ground the Replit Agent, and ship a self-updating app with live, cited intelligence.