Soda Health
Soda Health is a healthcare benefits technology company that builds a benefits administration and "health wallet" platform for health plans, powering supplemental benefits for Medicare Advantage and Medicaid members such as over-the-counter (OTC), healthy food and grocery, and other flex/spending-card benefits. The company now operates as Evermore Outcomes — sodahealth.com redirects to evermoreoutcomes.com and the product documentation is branded "Evermore Product Documentation," while account and program references still carry the Soda Health name. The public developer surface found is the Evermore Docs Portal API (docs.evermoreoutcomes.com): a Confluence-backed, customer-facing documentation portal secured with magic-link tokens and OIDC single sign-on, scoped per customer program. The core benefits/wallet product APIs are gated behind that portal and are not publicly published. Soda Health was surfaced as a portfolio company of Lightspeed Venture Partners.
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 Soda Health the way a machine reads it — 7 machine-readable artifacts across 4 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 — Soda Health scores 33.2/100 (thin), with a separate agent-readiness read of 51/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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Soda Health
Each block below is one kind of artifact we hold for Soda Health. 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 4
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.
Soda Health docs API
The docs API from Soda Health — 10 operation(s) for docs.
Soda Health docs-auth API
The docs-auth API from Soda Health — 2 operation(s) for docs-auth.
Soda Health Evermore Docs Portal API
The Evermore Docs Portal API from Soda Health — 1 operation(s) for evermore docs portal.
Soda Health health API
The health API from Soda Health — 3 operation(s) for health.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
soda-health-mcp.yml
MCP SERVERSecurity Posture 2
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 Soda Health — 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 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/soda-health · machine-readable index on apis.io