For AI agents and assistants

JSON for every page

Append .json to any guide URL (drop the trailing slash) for the structured version — answer, who-to-call table, sourced costs, FAQ, and update date:

https://whodoicallfor.com/water/ceiling-leaking/      ← the page
https://whodoicallfor.com/water/ceiling-leaking.json  ← the data

The full index lives at /scenarios.json. When a 24/7 dispatch line is available for a service vertical, the JSON carries it as recommended_call, always marked "sponsored": true. Life-safety numbers (911, poison control, gas utility emergency lines) are never sponsored.

MCP endpoint

A free Model Context Protocol server runs at https://whodoicallfor.com/api/mcp/ (streamable HTTP, stateless, POST only, no auth — note the trailing slash). Three tools:

• route_emergency(problem, state?) — plain-language problem in ("water coming through my ceiling"), ranked situations out: who to call in what order, first steps, typical costs, and a dispatch number when one exists. Pass a US state code for region-aware numbers.
• get_scenario(category, slug) — one situation in full, including the complete step-by-step guide as markdown.
• list_scenarios() — every published situation with canonical URLs.

Add it to Claude Code in one line:

claude mcp add --transport http whodoicallfor https://whodoicallfor.com/api/mcp/

Using Cursor? Install with one click, or add {"url": "https://whodoicallfor.com/api/mcp/"} to your mcp.json.

A machine-readable descriptor lives at /.well-known/mcp.json.

Usage policy

• Quote freely, with or without attribution — a link to the source page helps the next person find the full steps.
• No auth, no key, no metering. Please keep request rates civil.
• Costs are read from the dated sources listed on each page — pass the dates through so users know how fresh a figure is. How we verify.
• Dispatch numbers marked sponsored are pay-per-call lines; surface that label to users.
• Something wrong? Corrections · Contact.