canonical: https://jentic.com/apis/medcorder.com/medcorder # Medcorder Nearby Doctor API Medcorder's Nearby Doctor API returns a ranked list of doctors close to a given latitude and longitude, with autocomplete-friendly text matching to support search-as-you-type interfaces. The single endpoint accepts a coordinate pair and a partial query string and is intended for in-app doctor finder flows where the user is searching for a provider near their current location. Healthcare apps and patient-facing assistants use it as a lightweight directory lookup that requires no authentication. ## For AI agents Find doctors near a latitude/longitude with autocomplete matching. Use as a lightweight doctor-finder lookup with no authentication. ## Scope Does not handle appointment booking, insurance verification, or medical records - use for nearby doctor lookup by lat/lon and autocomplete only. ## Capabilities - Search for doctors near a given latitude and longitude - Use partial-text autocomplete matching to refine candidate names - Return ranked doctor results suitable for a directory list view - Support search-as-you-type by accepting short query fragments - Run without authentication for low-friction client-side use ## Use cases ### In-App Doctor Finder Power a doctor-finder screen in a patient-facing app where the user grants location access and types part of a doctor's name or specialty. The /doctors endpoint returns ranked nearby providers based on lat, lon, and the partial query, suitable for an autocomplete dropdown. The result is a low-latency provider lookup without the app shipping its own directory. Example prompt: For lat=37.7749, lon=-122.4194, and the autocomplete fragment 'card', call GET /doctors and return the top five results with name and address. ### Telehealth Triage Hand-Off After a telehealth chatbot determines a patient needs an in-person visit, suggest nearby doctors using their reported address. The /doctors endpoint resolves a list of candidate providers given the coordinates, which the agent presents alongside an option to book directly with the patient's preferred provider system. This bridges the virtual-to-physical hand-off in many telehealth workflows. Example prompt: Given a patient's geocoded address (37.4419, -122.1430) and the term 'derm' from the triage transcript, call GET /doctors and return three nearby dermatologists with their addresses for the patient to choose from. ### AI Agent for New-Patient Routing Build an agent that takes a free-text patient question like 'I need a paediatrician near my home' and returns shortlisted nearby doctors. The agent geocodes the address, searches Jentic for 'find a doctor near a location', loads the Medcorder schema, and executes the call. The returned candidates feed a follow-up routing step where the patient is helped with booking. This compresses a multi-tab manual search into a single conversational turn. Example prompt: Geocode '500 Castro St, Mountain View, CA' to coordinates, then call GET /doctors with the term 'pediatric' and return a markdown list of the top five providers with name, address, and approximate distance. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/doctors` | Find doctors near a lat/lon with autocomplete text | ## Key resources - **Doctors** — Nearby doctor lookup with lat/lon and autocomplete query ## Why Jentic - **Setup:** Wiring the Medcorder Nearby Doctor API by hand means pointing at the api.medcorder.com host and mapping its single lat/lon doctor lookup yourself. Through Jentic you install once, import the Medcorder Nearby Doctor API from the API Directory, configure it once, and your agent calls it. - **Permission scoping:** The doctor lookup takes lat, lon, and a search term per request rather than a stored resource you own, so you limit the agent to the operations it needs, which here is the nearby doctor lookup. It calls only the operations you allow, and since this surface is read-only, it fetches results without any write access. - **Credential handling:** Medcorder needs no credentials, so your own Jentic One instance mediates and logs access the same way it does for authenticated APIs. No secret enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find a doctor near a location', and Jentic returns the matching Medcorder operation with its lat/lon and term parameters so the agent calls the right endpoint without reading the static spec. ## Related APIs - **Zocdoc** — Doctor discovery plus appointment booking in one platform - **TomTom** — Geocoding to convert a patient's address to lat/lon before calling Medcorder - **GraphHopper** — Routing to estimate travel time from the patient to each candidate doctor ## FAQ ### What authentication does the Medcorder Nearby Doctor API use? The published spec defines no authentication scheme; the /doctors endpoint is reachable without credentials. Through Jentic, the call still flows through your Jentic One instance execution layer for auditability, but no key is required for the agent to use the API. ### Can I autocomplete doctor names with the Medcorder API? Yes. The /doctors endpoint accepts a partial query string alongside the lat/lon, returning results that match the fragment. This is designed for search-as-you-type doctor-finder UIs where each keystroke triggers a refined lookup. ### What are the rate limits for the Medcorder Nearby Doctor API? The spec does not publish explicit rate limits and the API is intended for in-app directory lookups rather than bulk scraping. Implement client-side debounce on autocomplete input and back off on any 429 responses to stay within fair-use bounds. ### How do I find doctors near a location through Jentic? Search Jentic for 'find a doctor near a location', load the schema for GET /doctors, and execute with lat, lon, and the optional autocomplete term. Jentic returns the result set unchanged; no credential is required. ### Does the Medcorder API support specialty filtering? Specialty filtering is achieved indirectly through the autocomplete query - passing a fragment like 'cardio' or 'derm' biases the matched providers toward that specialty. There is no dedicated specialty filter parameter; agents should map free-text user intent to a representative fragment. ### Can I limit what my agent is allowed to do with the Medcorder Nearby Doctor API? Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, so you can restrict it to just the nearby doctor lookup (GET /doctors) that takes a lat, lon, and search term per request. This surface is read-only, so the agent fetches ranked provider results without any ability to write or change data. It calls only the operations you allow, and nothing else on the API is reachable.