Optum
Optum, part of UnitedHealth Group, is a health services and technology company that operates one of the largest medical and pharmacy networks in the United States. Its developer platform (developer.optum.com) exposes RESTful, JSON- and X12 EDI-based healthcare APIs for eligibility verification, professional and institutional claims validation and submission, claim status, ERA/remittance reports, prior authorization, attachments, payer directory, dental pre-care and claims, pharmacy solutions, and FHIR-based Data Access and Interoperability (Patient Access) endpoints. APIs are secured with OAuth2 client-credentials bearer tokens over TLS 1.2+, with free sandbox access, interactive "Try It" documentation, and downloadable OpenAPI specifications.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Optum the way a machine reads it — 6 machine-readable artifacts across 3 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 — Optum scores 35.2/100 (thin), with a separate agent-readiness read of 16/100 (agent aware). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Optum
Each block below is one kind of artifact we hold for Optum. 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 3
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.
Optum Medical Network Eligibility and Claims API
RESTful, JSON and X12 EDI (270/271, 837, 276/277, 835) healthcare transaction APIs for real-time patient eligibility and coverage verification, professional and institutional cl...
Optum Data Access and Interoperability (FHIR) API
FHIR R4-based Patient Access and interoperability APIs (Endpoint, Procedure, DocumentReference, ObservationVitalSigns, Immunization, and related resources) supporting CMS intero...
Optum Real for Dental API
Real-time dental data exchange APIs for pre-care estimates, eligibility, claims submission and inquiry, attachments with image intelligence, and ERA, with GraphQL options for se...
Security Posture 3
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.
Resources
Every other property we hold for Optum — 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 4
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 3
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/optum · machine-readable index on apis.io