Public surface / Payer Provider Directory APIs
AvMed Provider Directory API
This endpoint could not be reached from any vantage on this run, so nothing about what it publishes was observed.
Observed surface
- Base URL
https://avmp.interop.avmed.com/avmp/api/plannet- Category
- Payer Provider Directory APIs
- Availability
- answered 0 of 1 checks so far; availability is reported once 14 observations exist
- Vantage agreement
- not reached from any of the 3 vantages tried, all on one network (github-actions), so this run cannot separate an endpoint that is down from one that does not answer this network: HTTP 404
Interpretation
A grade describes two public discovery documents at one point in time. It does not inspect patient data, authenticated behavior, or clinical quality.
Read the scoring method →Findings
Observed since 2026-08-20; no changes to declared capability recorded.
Registry provenance
How this entry was verified
Listed on the organization's own publication of this base URL, not on a retrieved conformance document: base URL printed under the literal heading 'Base URL' in AvMed's own Provider Directory API Documentation PDF (2026), linked from avmed.org/en/for-developers. AvMed prints two addresses for this surface and neither answers; this entry names the one its API documentation of record declares as the base URL (recorded 2026-08-19). Published at https://www.avmed.org/en/for-developers. On the verification date this probe observed: HTTP 404 ({"statusCode": 404, "message": "Resource not found"}) to an unauthenticated GET of /metadata. The other address AvMed publishes for this surface - a myfhir.avmed.org/provider/metadata link titled 'Capability Statement and Meta Data' on the for-developers page - fails TLS verification because the served certificate is AvMed's own (CN=myfhir.avmed.org, O=Avmed) and expired 2026-05-15, an endpoint-side fact rather than a vantage-side one; with verification disabled the same URL serves a 1,666-byte HTML maintenance page, not a CapabilityStatement. Both addresses are in the candidate log. The surface the rule requires to be reachable without authentication is published twice and reachable at neither address. No later re-check is recorded, so the date above is the last time anyone checked this entry against the live endpoint.
Share this endpoint's status
Link the badge back to this evidence page so readers can inspect the current findings.
<a href="https://fhir.chelseakr.com/endpoint/avmed-provider-directory/">
<img src="https://fhir.chelseakr.com/badge/avmed-provider-directory.svg"
alt="FHIR Scorecard: not observed on the latest run"></a>This is an observational snapshot of a public, unauthenticated surface. It is not an audit, a ranking of care quality, or a statement about anyone's regulatory compliance. See how we grade.