Public surface / Payer Provider Directory APIs
Health Care Service Corporation 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://api.hcsc.net- Category
- Payer Provider Directory APIs
- Availability
- answered 0 of the last 46 daily checks (0%)
- Last answered
- not in the recorded window
- Vantage agreement
- answered HTTP 500 from 3 of 3 vantages but returned no usable document: the endpoint is running and refusing this request, which is not the same as being unreachable: HTTP 500
What each vantage saw
| Vantage | Result | What it saw | Condition |
|---|---|---|---|
github-actions/macos-latest | not reached | HTTP 500 | HTTP 500, server_error |
github-actions/ubuntu-latest | not reached | HTTP 500 | HTTP 500, server_error |
github-actions/windows-latest | not reached | HTTP 500 | HTTP 500, server_error |
Vantages on one network are one network’s view sampled several times. A rule applied to that network’s address space reaches every one of them at once and reads exactly like agreement.
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 →This endpoint's full report: what was observed, what was not, and what would change it →
What its CapabilityStatement declares, resource by resource →
Findings
- No answer: /metadata answered HTTP 500 from 3 of 3 vantages but returned no usable document: the endpoint is running and refusing this request, which is not the same as being unreachable: HTTP 500 (observed 2026-10-03)R1Spec ↗
- No answer: latency not measured: no vantage was answered (observed 2026-10-03)R2Spec ↗
Observed since 2026-08-19; no changes to declared capability recorded.
Declared app-to-server access
What the endpoint's own documents declare about app-to-server access, observed on this run. Nothing here was requested or exercised, and none of it is graded. An absent field is reported as absent, not as a refusal: a document that does not mention a field has not said anything about it.
| Question | Answer | What the document says | Where it is declared |
|---|---|---|---|
| Declares private_key_jwt client authentication at the token endpoint | not retrieved on this run | no vantage retrieved .well-known/smart-configuration | SMART discovery: token_endpoint_auth_methods_supported |
| Declares the client_credentials grant, which SMART Backend Services uses | not retrieved on this run | no vantage retrieved .well-known/smart-configuration | SMART discovery: grant_types_supported |
| Declares the client-confidential-asymmetric capability | not retrieved on this run | no vantage retrieved .well-known/smart-configuration | SMART discovery: capabilities |
| Declares system-level scopes | not retrieved on this run | no vantage retrieved .well-known/smart-configuration | SMART discovery: scopes_supported |
| Declares an export operation | not retrieved on this run | no vantage retrieved the CapabilityStatement | CapabilityStatement: rest.operation and rest.resource.operation |
| Instantiates the Bulk Data Access implementation guide | not retrieved on this run | no vantage retrieved the CapabilityStatement | CapabilityStatement: instantiates |
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 verbatim on Health Care Service Corporation's own interoperability site, on the Provider Directory API page, as 'API endpoint base url: https://api.hcsc.net', with the instruction to substitute it for {environmentBaseUrl} in the paths the downloadable API spec gives. The page covers the Blue Cross and Blue Shield plans HCSC operates in Illinois, Montana, New Mexico, Oklahoma and Texas, so the entry is named for the corporation rather than for the Texas brand: one address serves five state plans and nothing in it distinguishes them. Blue Cross and Blue Shield of Texas's own domain publishes no interoperability or developer page at all; its 583-URL sitemap contains none (recorded 2026-08-19). Published at https://interoperability.hcsc.com/s/provider-directory-api. On the verification date this probe observed: HTTP 500 to a GET of /metadata. TLS is clean from this vantage with and without certificate verification, so the host is live and the server is erroring at the conformance path FHIR R4 requires every server to publish. The page prints this string as a base URL to substitute into spec paths rather than as a FHIR base, which is recorded here rather than repaired: no other address for this surface is printed, and constructing one would be a guess. 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/hcsc-provider-directory/">
<img src="https://fhir.chelseakr.com/badge/hcsc-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.
Every observation on record for this endpoint, with the dates it answered and the dates it did not.