Every morning, a one-page briefing of exactly which bills moved in the states you care about — every line clicks through to the official legislature page. A set-and-forth morning briefing that tells you, with a clickable link to the official bill page for every single item, exactly which bills moved yesterday in the states you follow — built once, refreshing itself every day.
A saved Claude Routine (scheduled cloud agent, cron, runs unattended on Anthropic infrastructure with the Synorb MCP connected per-task) that wakes daily, executes a saved Synorb Beacon over the user's chosen states, and produces a one-page cited briefing Artifact: a 50-state SVG choropliths map shaded by activity, a per-state column of bills that changed (introduced / passed chamber / referred to committee / enacted) with sponsor, vote tally, and committee, and a 7-day momentum sparkline — every bill row linking through to its real legislature.gov source_url. Delivered as the Routine's run output (and optionally re-opened as a live Artifact).
This is THE Routines narrative Anthropic is actively promoting (daily unattended briefing, connectors-per-task, runs while you sleep) pointed at a domain where Claude's #1 liability — hallucinated/mis-attributed citations — is fatal: a lobbyist who cites a wrong bill number loses the client. Synorb makes every claim auditable to the official statehouse URL with never_invent_urls enforced. The civic inventory is far richer than anyone expects (40+ live state legislatures; Michigan alone produced 296 bill manifests in 14 days, each with sponsor, 34-0 vote tallies, committee referrals, MCL section amendments). No existing Claude page is a scheduled multi-state cited Routine with a choropleth — the closest are one-shot statehouse-briefing workflows; this is the named upgrade: automated, multi-state, mapped, and provenance-first.
No setup to learn. Claude asks a handful of normal-person questions — each with a smart default, so “you pick” always works — then builds it with live Synorb data flowing in.
Smart default: The 10 highest-activity states plus anything the user later names — picked automatically from live volume so the first briefing is full, not empty.
Smart default: Everything that moved yesterday, with the user's spotlight subjects pinned to the top if they name any.
Smart default: Newsroom — a clean editorial one-pager with the map up top, dated and bylined like a real morning brief.
Smart default: 7:00 a.m. in your local time, delivered as the Routine's run output you can read in Claude (and re-open as the live map Artifact).
Editorial morning-brief aesthetic: serif headline, dateline, the choropleth map as the hero, then tidy per-state bill columns with sponsor + vote chips. Reads like a credible daily wire.
Dense, official-feeling monospace/utilitarian layout — status badges (INTRODUCED / PASSED / ENACTED), committee codes, and bill numbers front-and-center. Built for a staffer who scans fast.
Whitespace-forward, one accent color, map plus a single ranked list of what changed. For someone who wants signal and a source link, nothing else.
RUNTIME MCP, scheduled. The user connects the Synorb MCP to Claude once (Add connector -> https://mcp.synorb.com/mcp, paste the MCP token from Synorb Connect at connect time — requested in plain English only at that moment, never written into any file or client code). During the build the agent calls synorb-stream-search to resolve the chosen states to stream_ids, pulls a few real bills with synorb-manifests (compact=true, target_count 5-10) to shape the UI against true fields, then creates a saved Beacon (synorb-configure-beacon -> synorb-save-beacon) scoped to those states. It then registers a Claude Routine on the user's chosen cron; each firing runs the Beacon by beacon_id with a 1-day window through the connected MCP, gets live cited bill manifests, and renders the briefing Artifact. Data is live through the MCP session every morning; the credential lives only in the Claude connector vault.
Credential safetySynorb credentials stay server-side or local — never in client/frontend code. You only enter them when the agent asks, with credentials from synorb.com/connect.
Provenance is the spine: every bill row is a citation chip showing the source_channel_display (e.g. 'Michigan Legislature RSS — Bills Update') and a 'View bill ->' link to the exact source_url Synorb returned (e.g. legislature.mi.gov/Bills/Bill?ObjectName=2026-SB-0937). Hovering a claim ('passed 34-0', 'referred to Judiciary') highlights which citation backs it. A 'Sources' footer lists every official URL used that day. URLs are rendered ONLY from citations[]; the Routine never fabricates a legislature link, and on a thin day it states plainly that no bills moved rather than inventing one.
Yes. The build prompt connects Synorb at build time to learn the real data shape, then wires live Synorb data into the running product. A set-and-forth morning briefing that tells you, with a clickable link to the official bill page for every single item, exactly which bills moved yesterday in the states you follow — built once, refreshing itself every day.
Only where they are safe. RUNTIME MCP, scheduled. The user connects the Synorb MCP to Claude once (Add connector -> https://mcp.synorb.com/mcp, paste the MCP token from Synorb Connect at connect time — requested in plain English only at that moment, never written into any file or client code). During the build the agent calls synorb-stream-search to resolve the chosen states to stream_ids, pulls a few real bills with synorb-manifests (compact=true, target_count 5-10) to shape the UI against true fields, then creates a saved Beacon (synorb-configure-beacon -> synorb-save-beacon) scoped to those states. It then registers a Claude Routine on the user's chosen cron; each firing runs the Beacon by beacon_id with a 1-day window through the connected MCP, gets live cited bill manifests, and renders the briefing Artifact. Data is live through the MCP session every morning; the credential lives only in the Claude connector vault.
Provenance is the spine: every bill row is a citation chip showing the source_channel_display (e.g. 'Michigan Legislature RSS — Bills Update') and a 'View bill ->' link to the exact source_url Synorb returned (e.g. legislature.mi.gov/Bills/Bill?ObjectName=2026-SB-0937). Hovering a claim ('passed 34-0', 'referred to Judiciary') highlights which citation backs it. A 'Sources' footer lists every official URL used that day. URLs are rendered ONLY from citations[]; the Routine never fabricates a legislature link, and on a thin day it states plainly that no bills moved rather than inventing one.
A real app. Synorb is the cited data core; it also composes the platform's own tools: Claude Routines / Managed Agents (cron scheduling, runs unattended on Anthropic cloud, Synorb connector configured per-task), Artifacts: interactive React + inline SVG choropleth US map (no external map lib needed) shaded by per-state bill activity, plus per-state sparklines for 7-day momentum, Native web search — GAP ONLY, e.g. to add a one-line plain-English explainer of an obscure statute a bill amends; web-sourced lines are rendered in a visually distinct 'context (web)' style and never replace a Synorb-cited bill row, docx/xlsx skill (optional) to export the day's moved-bills table as a shareable spreadsheet or memo.
A few plain-English questions, each with a smart default so you can just say 'you pick': Which states do you want to follow? (name a few, a region, or say 'all the active ones'); Any particular subjects to spotlight — like housing, healthcare, elections, taxes — or just everything that moves?; What look do you want — Newsroom, Government Wire, or Minimal?; What time each morning should it run, and how should it reach you?.
The same Synorb MCP connects to every major coding agent. Pick yours.
Generate credentials, connect Claude, and ship something with live, cited intelligence.