Single-endpoint report

Centene Provider Directory API (Ambetter): 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

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.

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.