How BeInvolved works
City agendas live on dozens of different platforms. A custom Apify Actor reads them all into one schema, Claude explains each item in plain English and scores it against what you care about, and every action (calendar, public comment, alerts) is built on top of that one stream.
1Actor collects
Legistar Web API + Berkeley eAgenda, normalized into one schema
2Dataset stores
Every item lands in an Apify dataset with its staff report link
3Claude explains
Relevance to your interests, plus a one-sentence plain-English summary
4You act
Calendar, Claude-drafted public comments, weekly alerts via Apify Schedules
Under the hood
Government agendas are scattered across platforms that were never built to be read together. BeInvolved turns them into one stream that agents can call, built entirely on Apify.
Custom Actor
beinvolved, Python + httpx + BeautifulSoup, published with input and dataset schemas
Standby mode
Always-on HTTP API and its own MCP server at /mcp, no cold start
Datasets
One normalized row per agenda item, with a table view for the Console
Key-value store
OUTPUT record with a Markdown digest agents can read directly
Pay per event
agenda-item-scanned and relevant-item-found, so agents can pay per call
Tasks + Schedules
One click turns a scan into a weekly watch
Actor-to-Actor
Digests go out through apify/send-mail
Apify MCP server
Claude calls the Actor and apify/web-fetch through mcp.apify.com
Use it from your own agent
BeInvolved is an MCP tool. Add either endpoint to Claude, Cursor or any MCP client.
Apify MCP server
BeInvolved's own MCP (Standby)