Public surface / Payer Provider Directory APIs
Centene Provider Directory API (Ambetter)
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://iopc-pd.api.centene.com/iopc/pd/fhir/providerdirectory- Category
- Payer Provider Directory APIs
- Availability
- answered 3 of the last 30 daily checks (10%)
- Last answered
- 2026-09-20
- Vantage agreement
- answered HTTP 403 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 403
What each vantage saw
| Vantage | Result | What it saw | Condition |
|---|---|---|---|
github-actions/macos-latest | not reached | HTTP 403 | HTTP 403, forbidden |
github-actions/ubuntu-latest | not reached | HTTP 403 | HTTP 403, forbidden |
github-actions/windows-latest | not reached | HTTP 403 | HTTP 403, forbidden |
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 403 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 403 (observed 2026-10-03)R1Spec ↗
- No answer: latency not measured: no vantage was answered (observed 2026-10-03)R2Spec ↗
Observed since 2026-09-04; 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
base URL printed under the heading 'URL' in the 'Getting Started' document for the API 'FHIR - Provider Directory' on Centene's Partner Portal, whose catalog is served unauthenticated; Ambetter from Buckeye Health Plan's own Ohio page links that portal as 'our Partner Portal' and names that exact catalog entry. Attribution runs from the issuer outward: Centene's own documents name neither 'Ambetter' nor 'Buckeye', and the catalog entry is marked visibility Public, authentication None. Supersedes the retired production.api.centene.com addresses in data/rejected.json. A live CapabilityStatement was retrieved unauthenticated from a residential vantage on the curation date, and the publishing network does not get one: all three GitHub-hosted probing vantages received HTTP 403 on 2026-09-04 while this machine received a document the same hour. Both facts are recorded because neither is the whole picture. The endpoint pages grade what the publishing run observed, so this endpoint reads as not observed there while this record says a document was retrieved; the difference is the vantage, not the endpoint (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.
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/ambetter-centene-provider-directory/">
<img src="https://fhir.chelseakr.com/badge/ambetter-centene-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.