Sana Benefits
Sana Benefits is an Austin, Texas health benefits company founded in 2017 that sells level-funded and self-funded small-group health plans to small and midsize employers in the United States, bundling medical, dental and vision coverage with Sana Care, its in-house virtual-first primary care and care navigation service. Sana distributes almost entirely through licensed benefits brokers, underwrites and administers the plan itself with stop-loss insurance included, and prices provider claims off a reference-based percentage of the Medicare fee schedule. State landing pages confirm sales in Texas, Arizona, Illinois, Indiana, Kentucky, Ohio, Oklahoma, Virginia, Wisconsin and Alabama. Its API posture is closed: as of July 2026 Sana publishes no public developer portal, no API reference, no OpenAPI or Postman artifacts, no GraphQL surface and no webhook or event catalog. The developer.*, developers.*, docs.* and api.* subdomains do not resolve, and every /developers, /api, /developer, /partners and /integrations path on sanabenefits.com returns 404. The only machine surface is secure.sanabenefits.com, a login-walled JSON application serving the member, employer and broker dashboards; its /openapi.json and /swagger.json paths answer 401 login_required, confirming an internal-only API. No ACORD, AL3, IVANS, NGDS or X12 834 reference appears anywhere in public marketing or FAQ content. Quoting is a human broker workflow — "rates in 48 hours" from a web form — not an API. This is a partner-gated, broker-mediated benefits carrier with zero public self-serve API surface, which is the typical posture for the US benefits-admin tier in a market with no open-insurance mandate.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Sana Benefits the way a machine reads it — 1 machine-readable artifact, 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 — Sana Benefits scores 21.8/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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 Sana Benefits
Each block below is one kind of artifact we hold for Sana Benefits. 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.
Security Posture 1
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 Sana Benefits — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 9
The organization behind the API
Scroll within the panel for all 9 ·
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sana-benefits · machine-readable index on apis.io