A public-records MCP server and API for AI agents
SOS.city gives agents the official public record of every city with citations built in: 10 MCP tools, a REST API with an OpenAPI spec, a free allowance with no key, and pay-per-call in USDC through x402.
What it is
Every answer carries the publisher, the original URL, the licence and whether SOS.city opened and checked it.
No key needed for the free allowance. A key adds your plan; x402 needs no account at all.
Buildings, places and events. No person search, and no screening use.
Discovery
| MCP server (Streamable HTTP) | https://api.sos.city/mcp |
| MCP server card | https://api.sos.city/.well-known/mcp/server-card.json |
| OpenAPI 3.1 | https://api.sos.city/v1/openapi.json |
| Store catalogue | https://api.sos.city/v1/store |
| llms.txt | https://sos.city/llms.txt |
| Content map (Markdown) | https://sos.city/sitemap.md |
| Official MCP Registry | io.github.Proof-Layer/sos-city |
How it works
| Tool | What it does |
|---|---|
| search_library | Search the public record by question or keywords, scoped to a place (includes everything covering it) and a shelf. |
| get_source | Full details of one source: publisher, original link, API endpoint, licence, check status. |
| list_places | The atlas: world, countries, states, counties and cities, with their ids. |
| list_departments | The 15 shelves and what each covers. |
| list_gaps | Records people need that no one publishes yet. Check before saying a record doesn't exist. |
| search_records | The records themselves: building permits, code cases, inspections, certificates of occupancy, new businesses, grants, weather alerts, earthquakes, wildfires and power shutoffs, by place, ZIP, address or date. |
| request_record | Ask SOS.city to find a record that isn't in the library. |
| get_store | Prices and what's free; how to pay with credits, x402 or Stripe. |
| buy | Starts a checkout for credits or a city pack and returns the link for the person who pays. |
| get_city_pack | Every source for one place plus a year of reusable records, paid from credits. |
curl -s https://api.sos.city/mcp -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'GET https://api.sos.city/v1/records?kind=permit&place=us-ca-los-angeles&full_history=1
← 402 PAYMENT-REQUIRED: {x402Version: 2, accepts: [{scheme: "exact", network: "eip155:8453", asset: USDC, ...}]}
GET (same URL) PAYMENT-SIGNATURE: <signed payment>
← 200 PAYMENT-RESPONSE: <settlement>Rules for agents
- Cite. Show the publisher and the original link with every result. The original wins if it differs.
- Check the gap board first. Before telling a user a record doesn't exist, call
list_gaps; then offerrequest_record. - Ask before spending. Paid calls are priced in
get_store;buyreturns a link for the person who pays. - Never screen or profile people. SOS.city is not a consumer reporting agency. Not an emergency service: call 911.
What to do next
Questions people ask
How does an agent find SOS.city?
From the MCP server card at api.sos.city/.well-known/mcp/server-card.json, the OpenAPI spec at api.sos.city/v1/openapi.json, sos.city/llms.txt, or the official MCP Registry entry io.github.Proof-Layer/sos-city (which GitHub's MCP registry and other directories read).
Does it need a key?
No for the free allowance. A key adds your plan's limits and lets the agent spend credits. x402 needs no key at all.
What should an agent show its user?
The publisher and the link to the original for every result. If the original differs, the original wins.
What must an agent never do with it?
Locate, profile or screen a person, or use it for tenant, employment, credit or insurance decisions. And it's not an emergency service: in an emergency, call 911.