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.