Medcorder Nearby Doctor API

```json
{
  "service_type": "platform",
  "base_url": "https://medcorder.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [
    {
      "name": "Nearby Doctor Lookup",
      "method": "unknown",
      "path": "unknown",
      "description": "Returns doctors near a client given a lat/lon and autocomplete text.",
      "parameters": [
        {
          "name": "lat",
          "type": "number",
          "required": true,
          "description": "Latitude of the client"
        },
        {
          "name": "lon",
          "type": "number",
          "required": true,
          "description": "Longitude of the client"
        },
        {
          "name": "query",
          "type": "string",
          "required": false,
          "description": "Autocomplete text (e.g., doctor name or specialty)"
        }
      ]
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Geolocation-based doctor search",
    "Autocomplete search for doctors",
    "Proximity search using latitude/longitude"
  ],
  "raw_analysis": "Medcorder appears to be a healthcare/medical platform focused on connecting patients or clients with healthcare providers. The 'Nearby Doctor API' is described as returning doctors near a given location (lat/lon) with optional autocomplete text, suggesting a geo-search and autocomplete capability for finding medical professionals.\n\nHowever, the information provided is extremely limited. There is no publicly documented REST API endpoint, no visible authentication scheme, no SDK, no rate limit documentation, and no clear pricing model on the main site (medcorder.com). The platform may be defunct, private, or the API may only be available to partners or via a mobile app backend.\n\nMaturity assessment: Cannot be confirmed. The single-line description suggests at least one internal endpoint exists, but without a public developer portal, docs, or OpenAPI spec, it is not usable by third parties as-is. Integration options are unknown.\n\nRecommendation: Treat as a platform with a potentially internal/private API. Further investigation would require contacting Medcorder directly or reverse-engineering the mobile app. Not recommended for direct integration without official developer access."
}
```

2/3 tests passed

```json
{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 6.0,
    "response_parseability": 5.0,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 5.0,
    "latency": 10.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "note": "No public pricing information detected"
  },
  "issues": [
    "No llms.txt — agents lack a machine-readable capability/endpoint manifest",
    "No public pricing page detectable, blocking cost-benefit recommendations",
    "Core value prop is ambiguous: homepage titles it 'medical appointment recording/transcription', but capability data describes 'geolocation doctor search' — conflicting identity",
    "No documented public API despite having structured capabilities (geolocation, autocomplete), making programmatic use unclear",
    "Auth flow not described anywhere in fetched signals"
  ],
  "recommendations": [
    "Publish an llms.txt with API endpoints, auth method, and capability manifest",
    "Clarify the platform's primary purpose — recording/transcription vs. doctor discovery — in a single consistent tagline",
    "Expose a public API or integration docs to unlock response_parseability scoring",
    "Add a public pricing page (even 'free tier' clarity) to enable cost comparisons",
    "Document rate limits and auth options (e.g., NotLogin/magic link) to raise first_try_success"
  ]
}
```