Open311
The open API for citizen service requests, written in Washington D.C. and adopted well beyond it. Where it is implemented, a city's complaint queue is readable by software it does not control.
How this list is decided. Membership is not a field an editor set: it is every published entry whose own text names Open311, matched at build time, with the sentence printed under each row so you can judge the match yourself. 5 entries in 5 cities.
✔ Every published entry is checked against the public sources it cites before publication.
Where it appears in the atlas
Confirms that the pre-release version was run on city inspectors' vehicles before public release, and describes the pipeline: data to Connected Bits' servers, likely problems submitted to the city through Open311 and classified as potholes to fix or known obstacles such as speed bumps.
Miami-Dade wrote Open311 server code and does not appear to serve it.
The conventional hostname api.ville.montreal.qc.ca does not resolve at all (DNS ENOTFOUND), so there is no Open311 endpoint to test — unlike Washington D.C.
In May 2010 it agreed the Open311 GeoReport v2 specification jointly with Washington D.C., whose 311 API the standard grew out of, so outside apps can write into the city's work queue rather than only read from it.
Open311 says its standard began as an API for D.C.'s 311, and by May 2010 D.C.
Others in this group
The whole layer
Every standard, protocol and licence the atlas names, with the open-data licence ladder in one table: Standards & licences.