Single-endpoint report

Blue KC 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 9 checks. 9 ran. 0 were asked from every reporting vantage and answered by none. 0 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

Ordered by the points each would recover. Every item below comes from a check that actually ran on this run; nothing derived from a check that did not run appears here. The three dimensions are weighted, so recovering points does not guarantee a different letter — how we grade gives the weights.

1. Reduce the time /metadata takes to answer. The band is measured on the median across the vantages that answered, and it is deliberately coarse so that a network-path difference cannot move a grade.

   Worth up to 20 of the 100 points in Reachability.

   This run observed: /metadata responded in 3041 ms (median across 3 reachable vantages on one network)

   R2: what this check isSpec ↗

2. Declare what is running, in software.name and software.version. Both are needed; one without the other does not pass.

   Worth up to 20 of the 100 points in Capability transparency.

   This run observed: software name/version missing

   T2: what this check isSpec ↗

If this does not match what you see

Every number here describes two public documents at one moment, read from the vantages listed above. If it does not match what you serve, the difference is worth knowing.

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

base URL printed as finished, non-sandbox request URLs across three worked-example pages on Blue KC's own developer portal, and as the Swagger link href on its Provider Directory page. Vendor is Sapphire Digital, named and linked by Blue KC, which prints the finished URLs rather than a template. The portal states the directory 'does not require a user authentication to use'. Live CapabilityStatement retrieved Grade instability recorded on the curation date: repeat probes returned different interop-readiness scores while reachability held, which means this host served different profile declarations on different requests. That is the alternation this project already names, and no single probe's letter is the whole picture. (recorded 2026-09-04). 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.