See a city's streets change, block by block.

teleon.dev/docs/municipal reads open city data: 311 service requests, code violations and GTFS-RT transit feeds. Records keep the request type, a block-level place and the dates, with their source, license and read time.

v42.0teleon.dev/docs/municipalCivic data feedhttpsjson

Read the docs Copy the agent prompt

311 requests by districtone city, one week

D1D2D3D4D5D6

Potholes

Streetlights

Water leaks

Illegal dumping

Graffiti

Noise

fewermore

Darker cells hold more requests. Water leaks cluster in district 4, so a keyed watch on that district picks up each new one.

What it does

311 requests

Potholes, outages and water leaks arrive with their type, block and the dates opened and closed.

Code violations

Building and housing cases record the parcel, the code section cited and each status change.

Transit in real time

GTFS-RT trip updates, vehicle positions and alerts show where service runs late or reroutes.

The contract

Every record carries its source, license and read time, and agents follow a city by cursor or with a keyed watch on a district or route.

StoreS181

Versionv42.0

Sources311 requests, code violations, GTFS-RT

Each recordSource, license, read time

Identifiers

311 service_request_id
GTFS-RT trip_id

Execution contracts

Request and responseCopy

GET https://api.teleon.dev/v1/municipal/changes?since=cur_0c41&type=water_leak

# Response
{
  "cursor": "cur_0c58",
  "records": [
    {
      "id": "muni_311_88412",
      "kind": "311_request",
      "type": "water_leak",
      "place": "400 block Avenue, district 4",
      "opened": "2026-10-24T14:10:00Z",
      "status": "open",
      "source": "Meridian City open data portal",
      "license": "CC BY 4.0",
      "read_at": "2026-10-25T21:30:02Z"
    }
  ]
}

Endpoints

Method	Path	Access	What it does
`GET`	`/v1/municipal/records`	RING-3	List records by city, request type and district
`GET`	`/v1/municipal/records/{id}`	RING-3	Read one record with its source, license and read time
`GET`	`/v1/municipal/changes?since={cursor}`	RING-3	Read every change since a cursor, in order
`POST`	`/v1/municipal/watches`	RING-2	Watch a district, a route or a request type with a key

Listed paths appear in the service’s published files today. This surface comes from the Teleon Omnibus Codex v1.0 to v50.0, Oct 25, 2026. In the one-host plan every path here is served under api.teleon.dev/v1/municipal.

How it connects

Reads from

Foragerteleon.dev/docs/forager Permits and deedsteleon.dev/docs/permits

Feeds into

Catalyst fusionteleon.dev/docs/catalysts Searchteleon.dev/docs/search

Queuesaq526-aq600

StoresS181 Municipal 311, Code Violations and Transit

For agents

Give your agent the read-only guide first. It reports back before any write.

Agent prompt

Read https://teleon.dev/docs/municipal.md and summarize this week's 311 water-leak requests for one city by district. Read only.

Copy

llms.txt Agent card

Words on this page

Full glossary

311 request: A non-emergency service request to a city, such as a pothole, logged with its type, place and dates.
GTFS-RT: GTFS Realtime: the standard feed format for transit trip updates, vehicle positions and service alerts.
Cursor: A position in a feed's change log. Reading since a cursor returns everything newer, in order.
Keyed watch: A standing request made with an API key that names what to follow and delivers each matching change.