# Blue Cross Canada

> Blue Cross Canada (bluecross.ca) is the national consumer brand of the Canadian Association of Blue Cross Plans, a federation of independent, largely not-for-profit regional Blue Cross plans covering roughly eight million Canadians a year for supplementary health and dental, group and employee benefits, retiree plans, travel medical, and term life and critical illness. It has NO public API: no developer portal, no API reference, no OpenAPI/Swagger/AsyncAPI/GraphQL, no SDKs, no webhooks, and no Postman collection. Every integration path is an authenticated member, plan-sponsor, broker, or health-provider login.

Generated by API Evangelist from apis.yml and the artifacts in this repository. The provider publishes no llms.txt of its own — /llms.txt returns 404 on bluecross.ca and on every member-plan host probed.

## What an agent can and cannot do here

- There is no programmatic way to quote, bind, issue, submit a claim (FNOL), or check eligibility with Blue Cross Canada. Those flows exist only as HTML web forms behind member and provider logins.
- The association underwrites nothing; each regional plan operates its own systems, and none of them publishes a developer surface either.
- Electronic claims do move over real rails — Claimstream (Alberta, Pacific and Medavie Blue Cross), Medavie ePay, and third-party networks such as TELUS eClaims — but none publishes a public specification or developer documentation.
- The only anonymous machine-readable documents in the federation are Pacific Blue Cross's OIDC/OAuth discovery documents, which authenticate website members against an Umbraco CMS. They are not an insurance API.

## Company

- [Website](https://www.bluecross.ca/): National brand and regional routing site.
- [About](https://www.bluecross.ca/about/): "An association of independent Blue Cross Plans", operating in Canada since 1938.
- [Contact](https://www.bluecross.ca/contact/): Regional office directory — the support channel.
- [News](https://www.bluecross.ca/news/): Association news; RSS at https://www.bluecross.ca/feed/.
- [Members](https://www.bluecross.ca/memberweb/): "Make a Claim" entry point that routes to per-plan authenticated portals.
- [Terms of Use and Privacy](https://www.bluecross.ca/terms-of-use-privacy/)
- [Accessibility](https://www.bluecross.ca/accessibility/)
- [Careers](https://www.bluecross.ca/careers/)

## Member plans

- Alberta Blue Cross — https://ab.bluecross.ca/
- Pacific Blue Cross — https://pac.bluecross.ca/
- Manitoba Blue Cross — https://www.mb.bluecross.ca/
- Saskatchewan Blue Cross — https://www.sk.bluecross.ca/
- Ontario and Quebec Blue Cross (Canassurance) — https://on.bluecross.ca/
- Medavie Blue Cross — https://www.medaviebc.ca/

## APIs

None. apis.yml lists zero APIs, deliberately. The default WordPress route at https://www.bluecross.ca/wp-json/ answers 200 but is an artifact of the publishing platform, not an insurance API, and the Umbraco Content Delivery API on pac.bluecross.ca returns 401 to every anonymous request.

## Artifacts in this repository

- [Review](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/review.yml): Full probe log and verdict.
- [Well-known index](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/well-known/canadian-blue-cross-well-known.yml): /.well-known/ status across seven hosts.
- [OIDC discovery (Pacific Blue Cross)](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/well-known/canadian-blue-cross-pac-openid-configuration.json)
- [OAuth authorization-server metadata (Pacific Blue Cross)](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/well-known/canadian-blue-cross-pac-oauth-authorization-server.json)
- [JWKS (Pacific Blue Cross)](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/well-known/canadian-blue-cross-pac-jwks.json)
- [Authentication profile](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/authentication/canadian-blue-cross-authentication.yml)
- [OAuth scopes](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/scopes/canadian-blue-cross-scopes.yml)
- [Problem types](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/errors/canadian-blue-cross-problem-types.yml)
- [Conformance](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/conformance/canadian-blue-cross-conformance.yml)
- [Conventions](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/conventions/canadian-blue-cross-conventions.yml)
- [Domain security](https://raw.githubusercontent.com/api-evangelist/canadian-blue-cross/refs/heads/main/security/canadian-blue-cross-domain-security.yml)

## Market context

Canada has no open-insurance mandate. OSFI supervises federally regulated insurers prudentially, the provinces (FSRA in Ontario, AMF in Quebec) regulate market conduct, and Consumer-Driven Banking — Canada's open-banking framework — explicitly excludes insurance. Unlike the US Blues, which were pushed into FHIR Patient Access APIs by CMS-9115-F, no Canadian rule asks this federation to publish anything. A zero-API posture here is compliant behaviour, not a lag.