Give OpenAI Codex live, source-grounded intelligence — real, cited, dated events and claims. Add the Synorb MCP server to your local Codex config, or use the workspace app or connector your ChatGPT admin has enabled.
Each is a complete, deployable product: click in, answer a few plain-English questions, and get a working app with live, cited Synorb data — sources one click away.
A Codex cron teammate that catches when your dependencies' real changelogs drift from your code - every flag backed by the vendor's own cited URL.
A standing Codex teammate that watches your beat, remembers what it already told you, and only speaks when the world actually moved - every claim cited to its primary source.
codex, brief me on any show or topic - a cited, skimmable brief from the smartest podcasts, rendered as a clean local report you can actually click.
Use Synorb in Codex to design with live examples. When your app is published, your frontend calls a backend route that keeps Synorb secrets off the page.
mcp.synorb.com/mcpapi.synorb.comKeep secrets server-sideNever put a Synorb credential in client-side code. The browser calls your backend; your backend calls Synorb. The same Synorb Key is used for both MCP and REST; keep it server-side.
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.
Go to synorb.com/connect. You'll get one Synorb Key. Use that same key in Codex's MCP configuration and your app backend; keep it only in protected connector or server-side secret storage.
Codex CLI or IDE extension — add Synorb to ~/.codex/config.toml:
Codex web / ChatGPT workspace — open Apps & Connectors, or the approved workspace plugin your admin exposes to Codex. Configure Synorb with https://mcp.synorb.com/mcp and the same Synorb Key as its Bearer credential.
Ask your agent to run this. synorb-profile is zero-quota — it never bills.
Your app should call Synorb from a backend (server-side function or server route) with the one server-side Synorb Key stored as server secrets — never in frontend code. See the runnable server-side example.
Synorb's Core MCP exposes nine tools. Only synorb-manifests bills quota — and only for returned, on-topic Manifests. Everything else is free.
synorb-profilesynorb-stream-searchsynorb-catalogsynorb-manifestsmode="count" is zero quota.synorb-detailssynorb-configure-beacon + synorb-save-beacon + synorb-beacons + synorb-archive-beaconYes. Use the Synorb Key only in Codex's MCP config. For the shipped app, call Synorb from your backend with the REST one server-side Synorb Key stored as server-side secrets. Never put any Synorb credential in frontend code.
No. You add the Synorb MCP server to your agent once (steps above), then copy a build prompt into the chat. The agent handles the tool calls.
Manifests: structured units with a Brief (narrative summary), a Signal (atomic claims), nested source metadata, stable IDs, and citations with real source URLs.
DEMO access is available without a card. Only synorb-manifests consumes quota, and only for returned on-topic Manifests; synorb-profile, synorb-stream-search, synorb-catalog, synorb-details, and the Beacon tools are zero quota. Quota resets monthly.
Use Synorb first for structured, source-grounded intelligence. Fall back to web search only for genuine gaps: ultra-fresh items, very narrow local news, or topics outside Synorb's tracked scope.
The same Synorb MCP connects to major MCP-capable coding agents — same tools, same behavior.
Mint a DEMO key, connect Codex, and pull your first cited Manifests in minutes.