The vet book answers machines the same way it answers people: the nearest practices to a zip with the phone numbers, which ones are open at 2 a.m., which ones come to the farm. Every phone and hours line was read off the practice's own website on the date each record carries. The pages stay free for people. Lookups by agents are metered after a free taste.

Plain JSON

curl "https://porchdogsupply.com/api/nearby?zip=38655&service=24-hour&radius_miles=120" \
  -H "Authorization: Bearer pdv_live_…"

GET /api/nearby?zip=&lat=&lng=&radius_miles=&service=&category=&q=&open_at=
GET /api/entries/{id}            the full record: phone, hours, services, verified_from, verified_on
GET /api/entries/{id}/open?datetime=   open · closed · unknown, in the practice's own time zone
GET /api/billing/me              your lookups this month (send the key)
GET /api/openapi.json            the OpenAPI 3.1 description

MCP

{
  "mcpServers": {
    "porch-dog-vets": {
      "url": "https://porchdogsupply.com/mcp",
      "headers": { "Authorization": "Bearer pdv_live_…" }
    }
  }
}

tools: find_nearby · get_entry · check_open     (a metered call without credit answers HTTP 402, JSON-RPC error -32002, with the terms in `data`)

Service tags

24-hour, emergency, large-animal, farm-call, poultry-and-goats, urgent-care. Results carry distance_miles, phone, hours (structured where the practice publishes a plain schedule), verified_from and verified_on. Claimed records, confirmed by the practice itself, rank first.

Terms: no listing is paid for; the data is the practice's own published information, re-published with the source and date. Confirm with the practice before you drive. Questions: the contact page.