Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Cigna website screenshot

Cigna

Cigna Healthcare is a leading global health services company offering medical, dental, behavioral, and pharmacy plans for individuals, families, and employers. The Cigna Developer Portal exposes CMS-mandated FHIR APIs for Patient Access, Provider Directory, Drug Formulary, and Provider Access, along with member and provider service APIs that enable third-party applications, electronic health record systems, and partners to access member health data with consent and look up Cigna network providers and formulary information.

agent ready

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Cigna the way a machine reads it — 32 machine-readable artifacts across 15 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Cigna scores 62.0/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 62.0/100 · strong
Contract Quality 12.4 / 25
Developer Ergonomics 7.0 / 20
Commercial Clarity 13.7 / 20
Operational Transparency 3.4 / 13
Governance 8.8 / 12
Discoverability 10.0 / 10
Regulatory · Health 15.0 / 15
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Cigna

Each block below is one kind of artifact we hold for Cigna. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 15

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

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

Cigna Bulk Data API

The Bulk Data API from Cigna — 1 operation(s) for bulk data.

Cigna Condition API

The Condition API from Cigna — 1 operation(s) for condition.

Cigna Coverage API

The Coverage API from Cigna — 1 operation(s) for coverage.

Cigna Encounter API

The Encounter API from Cigna — 1 operation(s) for encounter.

Cigna ExplanationOfBenefit API

The ExplanationOfBenefit API from Cigna — 1 operation(s) for explanationofbenefit.

Cigna HealthcareService API

The HealthcareService API from Cigna — 1 operation(s) for healthcareservice.

Cigna InsurancePlan API

The InsurancePlan API from Cigna — 2 operation(s) for insuranceplan.

Cigna Location API

The Location API from Cigna — 1 operation(s) for location.

Cigna MedicationKnowledge API

The MedicationKnowledge API from Cigna — 1 operation(s) for medicationknowledge.

Cigna MedicationRequest API

The MedicationRequest API from Cigna — 1 operation(s) for medicationrequest.

Cigna Observation API

The Observation API from Cigna — 1 operation(s) for observation.

Cigna Organization API

The Organization API from Cigna — 1 operation(s) for organization.

Cigna Patient API

The Patient API from Cigna — 4 operation(s) for patient.

Cigna Practitioner API

The Practitioner API from Cigna — 2 operation(s) for practitioner.

Cigna PractitionerRole API

The PractitionerRole API from Cigna — 1 operation(s) for practitionerrole.

Scroll within the panel for all 15 ·

Open Collections 4

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

GraphQL 1

Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.

GraphQL schemas published by this provider.

Cigna GraphQL Schema

This document describes a conceptual GraphQL schema for Cigna Healthcare, one of the largest global health services companies. Cigna's Developer Portal exposes CMS-mandated FHIR...

GRAPHQL

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Cigna Plans Pricing

3 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Cigna Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.

Cost, billing, and metering signals for API financial operations.

Cigna Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Cigna Context

0 classes · 8 properties

JSON-LD

Spectral Rules 1

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

Cigna API Rules

5 rules · 3 warnings

SPECTRAL

JSON Schema 1

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

CignaPatient

10 properties

JSON SCHEMA

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Cigna Authentication

oauth2 · 2 schemes

SECURITY

Cigna Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Cigna Vulnerability Disclosure

disclosure policy published

SECURITY

Cigna Trust Center

SOC 2, HIPAA

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Cigna Scopes

6 scopes · authorizationCode/clientCredentials

6 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Cigna Agentic Access

22 operations

22 operations · 0 acting

AGENTIC

Resources

Every other property we hold for Cigna — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/cigna · machine-readable index on apis.io