Single-endpoint report

AvMed Provider Directory API: endpoint report

Everything this project observed about this one endpoint, everything it did not observe, and what would change the result. Free to read, link, print and hand on; there is nothing here behind a sign-in and nothing to buy.

Built to print. Use your browser’s print or “Save as PDF” to keep a dated copy; the page carries its own address and observation date.

What was observed, and what was not

This report covers 4 checks. 0 ran. 2 were asked from every reporting vantage and answered by none. 2 were never asked, because nothing was retrieved for them to read. The three are different facts and none of them is a zero: a check that did not run publishes no number, no mark against this endpoint, and nothing below to act on.

What would change this

Nothing is listed here, because no check in this report ran. This project observed nothing about this endpoint on this run, and an absence is not a finding to act on.

If this does not match what you see

This run was not answered from any of 3 vantages on 1 network. A rule applied to one network's address space -- a bot filter, a geo rule, a rate limit -- reaches every vantage on that network at once, and nothing here can tell that apart from an endpoint being down. If this endpoint answers from your own network, that difference is the finding, and this project would rather publish it than keep this page as it stands.

Correct or dispute this record. There is no sign-in, no fee, and nothing to buy: this report is free to read, link, print and hand on, and this project collects nothing about the people who read it.

Where this came from

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.

The same run, as data: this endpoint's JSON, what its CapabilityStatement declares, resource by resource, and every observation on record for it, with the dates it answered and the dates it did not.