Vitality

Vitality is a United Kingdom health and life insurer, operating as VitalityHealth and VitalityLife under the Vitality umbrella brand and owned by the South African financial services group Discovery Limited. Formed from the 2004 PruHealth joint venture with Prudential and the 2010 acquisition of Standard Life Healthcare, and rebranded to Vitality in 2014, it is the UK's third-largest private medical insurer behind Bupa and AXA, with roughly 1.9 million members and a shared-value model that prices private medical insurance, life cover and protection against member health and activity engagement. Its lines of business are private medical insurance, life insurance and protection, and workplace/employee benefits distributed through intermediaries, employee benefit consultants and bank partnerships rather than direct developer channels. Vitality's API posture is partner-gated and undocumented in public: it has modernised onto a WSO2 API Manager platform to decouple core policy and member services from front-end applications and to shorten partner onboarding, and it runs a publicly resolvable production API gateway at apis.vitality.co.uk, but it publishes no self-serve developer portal, no API reference, no OpenAPI or Swagger definitions and no public quote, bind, issue or FNOL endpoints. Credentials are issued through commercial partner onboarding and the gateway's OAuth2 client-credentials token endpoint rejects anonymous callers. There is no public ACORD, AL3 or NGDS reference for the UK entity, which is consistent with a life-and-health carrier in a market where ACORD adoption is concentrated in the London subscription market rather than in retail health and protection.

Vitality is listed with 1 API on the APIs.io network. Tagged areas include Insurance, United Kingdom, Health Insurance, Life Insurance, and Employee Benefits.

Vitality’s developer surface includes support, authentication, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

20.4/100 emerging ▬ flat Agent 16/100 agent aware saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPartner gated

1 API

Insurance United Kingdom Health Insurance Life Insurance Employee Benefits Carrier Policy Administration Underwriting

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 20.4/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.8 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 5.5 / 15

Agent readiness — 16/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/vitality-uk/"><img src="https://apis.io/badge/vitality-uk/card.svg" alt="Vitality on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 16.7 — up to +16.7 composite points
Access Clarity scores 21.1 — up to +15.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/vitality-uk/apis.yml: open an issue on github.com/api-evangelist/vitality-uk to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Dynamic Client Registration

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Vitality Partner API Gateway

Vitality's production API gateway, running WSO2 API Manager at apis.vitality.co.uk (origin wso2-prd-apigw.tvc.vitality.co.uk:8243 behind an AWS load balancer in eu-west-1). The ...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Vitality Uk Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

Vitality Uk Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Vitality Uk Scopes

5 scopes · authorizationCode/clientCredentials

5 scopes

SCOPES

Resources

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Conventions

Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Contact

Contact

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

OpenIDConnect

OpenIDConnect

Source (apis.yml)

aid: vitality-uk
url: https://raw.githubusercontent.com/api-evangelist/vitality-uk/refs/heads/main/apis.yml
name: Vitality
kind: company
description: 'Vitality is a United Kingdom health and life insurer, operating as VitalityHealth and VitalityLife under the
  Vitality umbrella brand and owned by the South African financial services group Discovery Limited. Formed from the 2004
  PruHealth joint venture with Prudential and the 2010 acquisition of Standard Life Healthcare, and rebranded to Vitality
  in 2014, it is the UK''s third-largest private medical insurer behind Bupa and AXA, with roughly 1.9 million members and
  a shared-value model that prices private medical insurance, life cover and protection against member health and activity
  engagement. Its lines of business are private medical insurance, life insurance and protection, and workplace/employee benefits
  distributed through intermediaries, employee benefit consultants and bank partnerships rather than direct developer channels.
  Vitality''s API posture is partner-gated and undocumented in public: it has modernised onto a WSO2 API Manager platform
  to decouple core policy and member services from front-end applications and to shorten partner onboarding, and it runs a
  publicly resolvable production API gateway at apis.vitality.co.uk, but it publishes no self-serve developer portal, no API
  reference, no OpenAPI or Swagger definitions and no public quote, bind, issue or FNOL endpoints. Credentials are issued
  through commercial partner onboarding and the gateway''s OAuth2 client-credentials token endpoint rejects anonymous callers.
  There is no public ACORD, AL3 or NGDS reference for the UK entity, which is consistent with a life-and-health carrier in
  a market where ACORD adoption is concentrated in the London subscription market rather than in retail health and protection.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  gated: partner
  gated_source:
  - tag:Partner Gated
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Insurance
- United Kingdom
- Health Insurance
- Life Insurance
- Employee Benefits
- Carrier
- Policy Administration
- Underwriting
created: '2026-07-25'
modified: '2026-07-25'
specificationVersion: '0.23'
apis:
- name: Vitality Partner API Gateway
  description: 'Vitality''s production API gateway, running WSO2 API Manager at apis.vitality.co.uk (origin wso2-prd-apigw.tvc.vitality.co.uk:8243
    behind an AWS load balancer in eu-west-1). The gateway is publicly resolvable and returns HTTP 200, and its OAuth2/OpenID
    Connect identity layer is fully published anonymously — discovery document, JWKS, authorization, token, userinfo, introspection,
    revocation, device-authorization and logout endpoints are all live. The business APIs behind it are not: no API catalogue,
    no reference documentation and no machine-readable contract are exposed, every WSO2 developer-portal route returns the
    404 fault document, and the token endpoint rejects anonymous callers with invalid_client. Credentials are issued through
    commercial partner onboarding rather than a signup form. This entry records a real, verified, undocumented API surface
    — it is not a claim that Vitality operates a public API programme.'
  humanURL: https://apis.vitality.co.uk/
  baseURL: https://apis.vitality.co.uk
  tags:
  - Insurance
  - Health Insurance
  - OAuth
  - OpenID Connect
  - Authentication
  tags_raw:
  - Insurance
  - Health Insurance
  - Partner Gated
  - OAuth2
  - OpenID Connect
  - Authentication
  properties:
  - type: Authentication
    url: authentication/vitality-uk-authentication.yml
  - type: OAuthScopes
    url: scopes/vitality-uk-scopes.yml
  - type: OpenIDConnect
    url: well-known/vitality-uk-openid-configuration.json
  - type: WellKnown
    url: well-known/vitality-uk-well-known.yml
common:
- type: DomainSecurity
  url: security/vitality-uk-domain-security.yml
- type: Website
  url: https://www.vitality.co.uk/
- type: GitHubOrganization
  url: https://github.com/VitalityUK
- type: Contact
  url: https://www.vitality.co.uk/contact/
- type: Support
  url: https://www.vitality.co.uk/support/
- type: PrivacyPolicy
  url: https://www.vitality.co.uk/privacy/
- type: TermsOfService
  url: https://www.vitality.co.uk/legal/
- type: Authentication
  url: authentication/vitality-uk-authentication.yml
- type: OAuthScopes
  url: scopes/vitality-uk-scopes.yml
- type: OpenIDConnect
  url: well-known/vitality-uk-openid-configuration.json
- type: WellKnown
  url: well-known/vitality-uk-well-known.yml
- type: Conformance
  url: conformance/vitality-uk-conformance.yml
- type: ErrorCatalog
  url: errors/vitality-uk-problem-types.yml
- type: Conventions
  url: conventions/vitality-uk-conventions.yml
- type: Lifecycle
  url: lifecycle/vitality-uk-lifecycle.yml
- type: LLMsTxt
  url: llms/vitality-uk-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-tags-removed:
- Partner Gated

Vitality API — frequently asked questions

Does Vitality have an API?

Yes. APIs.io lists 1 API from Vitality, including Vitality Partner API Gateway.

How do I authenticate with the Vitality API?

Vitality documents its authentication (oauth2/openIdConnect · 2 schemes). The details are profiled on APIs.io as Vitality Uk Authentication.

Is the Vitality API ready for AI agents?

Vitality has a Kin Score of 20.4 out of 100 (emerging) and an Agent Readiness score of 15.8 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/vitality-uk"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/vitality-uk/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/vitality-uk/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.