Durham Agenda Center API
Read-only live access to Durham, NC Agenda Center records. The source publishes a structured RSS feed containing the latest agenda updates; the API preserves that scope and exposes source-derived agenda and packet links. The feed does not publish a separate body field or pagination cursor, so body is conservatively inferred from each RSS title and next_cursor is null at the source boundary.
Endpoint health
Loading verification…
Connect your agent
Connect through MCP so your agent can find this API, read its docs, and call its endpoints.
Add the server from your terminal.
claude mcp add --transport http agent-data https://agent-data.motie.dev/mcpIn Claude Code, run /mcp, select agent-data, then Authenticate. Sign in to your agent-data account in the browser.
Then ask your agent to use the Durham Agenda Center API for your task.
Call it over HTTP
Get an API keySign up free, generate an API key, and set it as AGENT_DATA_API_KEY in your environment. Your first 100 calls each month are free.
curl --request GET --get 'https://3kpkg0jfvk.execute-api.us-east-2.amazonaws.com/prod/b9838fca-2414-4339-81b5-123cc27b03d8/meetings' \
--header "Authorization: Bearer $AGENT_DATA_API_KEY"Endpoints
Inputs and response fields for every endpoint in this API.
GETMeetings/meetings
Fetches the live Durham Agenda Center RSS feed. body is a case-insensitive substring filter over the feed title-derived body; from and to are inclusive ISO dates. The source feed currently publishes a bounded latest-update list and no continuation token, so next_cursor is null and cursor is accepted only as a numeric compatibility input.
Input
bodyOptionalQuery · string | nullCase-insensitive body substring.
Example: City Council
fromOptionalQuery · string | nullInclusive start date, YYYY-MM-DD.
Example: 2026-09-01
toOptionalQuery · string | nullInclusive end date, YYYY-MM-DD.
Example: 2026-10-31
cursorOptionalQuery · string | nullNumeric compatibility cursor; the source feed has no continuation page.
Response
itemsobject[]items[].body?string | nullitems[].titlestringitems[].agenda_url?string | nullitems[].meeting_idstringitems[].packet_url?string | nullitems[].source_urlstringitems[].status_raw?string | nullitems[].minutes_url?string | nullitems[].observed_atstringitems[].meeting_date?string | nullitems[].source_as_of?string | nullnext_cursor?string | nullobserved_atstringsource_as_of?string | nullFields marked ? are optional.
For the next page, pass next_cursor from the response as cursor. Leave it empty on the first call.
GETMeetings by meeting id/meetings/{meeting_id}
Resolves a meeting identifier from the live Durham agenda RSS feed.
Input
meeting_idRequiredPath · stringNumeric identifier from a Durham RSS item link.
Example: 3585
Response
body?string | nulltitlestringagenda_url?string | nullmeeting_idstringpacket_url?string | nullsource_urlstringstatus_raw?string | nullminutes_url?string | nullobserved_atstringmeeting_date?string | nullsource_as_of?string | nullFields marked ? are optional.
GETMeetings by meeting id documents/meetings/{meeting_id}/documents
Resolves the live meeting from RSS and returns the Durham agenda and packet URLs using the source URL convention observed on Agenda Center records. Durham RSS does not expose document inventory as structured fields. It emits a minutes link only when the RSS description explicitly says minutes were added or updated.
Input
meeting_idRequiredPath · stringNumeric identifier from a Durham RSS item link.
Example: 3585
Response
itemsobject[]items[].urlstringitems[].meeting_idstringitems[].source_urlstringitems[].observed_atstringitems[].source_as_of?string | nullitems[].document_typestringmeeting_idstringobserved_atstringsource_as_of?string | nullFields marked ? are optional.
Don’t see the endpoint you need?
Ask agent-data to add an endpoint or return more fields. Extensions are free and keep existing endpoints working.
An account is required to submit an extension. Prepare your request, then sign in to build.