Lynx
Lynx (Lynx FinHealth) is a healthcare fintech platform that provides embedded banking, payments, benefits, and e-commerce infrastructure for health plans, providers, and digital health companies. Its API-first and white-label platform powers consumer-directed health accounts (HSA/FSA), ICHRA administration, directed and filtered spend accounts, instant physical and virtual card issuance with merchant and SKU-level controls, supplemental benefits, pharmacy access, rewards and incentive programs, and a qualified medical expense (QME) e-commerce marketplace with end-to-end fulfillment. Lynx is SOC 2 and HITRUST certified and exposes a developer hub, dated changelog, hosted sandbox, and Atlassian status page. Surfaced as a portfolio company of Obvious Ventures and enriched from the public Lynx surface (the full API reference, authentication model, and test data are gated behind developer login).
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Lynx the way a machine reads it — 86 machine-readable artifacts across 18 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 — Lynx scores 51.7/100 (developing), with a separate agent-readiness read of 36/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Lynx's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lynx/"
title="Lynx on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lynx.svg"
alt="Lynx Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/lynx/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lynx/"
title="Lynx on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lynx/card.svg"
alt="Lynx Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Lynx
Each block below is one kind of artifact we hold for Lynx. 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 21
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.
Lynx API
Lynx FinHealth API for embedded health accounts, enrollment, contributions, payments and distributions, transactions, and card issuance/management. Reference is gated behind dev...
Lynx Investments API
The Investments API from Lynx — 20 operation(s) for investments.
Lynx Tags API
The Tags API from Lynx — 2 operation(s) for tags.
Lynx Accounts API
The Accounts API from Lynx — 9 operation(s) for accounts.
Lynx Cards API
The Cards API from Lynx — 14 operation(s) for cards.
Lynx Claims API
The Claims API from Lynx — 3 operation(s) for claims.
Lynx Client Org Application Token Controller API
The client-org-application-token-controller API from Lynx — 1 operation(s) for client-org-application-token-controller.
Lynx Clients API
The Clients API from Lynx — 5 operation(s) for clients.
Lynx Commerce API
The Commerce API from Lynx — 23 operation(s) for commerce.
Lynx Copay API
The Copay API from Lynx — 2 operation(s) for copay.
Lynx Enrollments API
The Enrollments API from Lynx — 3 operation(s) for enrollments.
Lynx Expense API
The Expense API from Lynx — 1 operation(s) for expense.
Lynx Externalaccounts API
The Externalaccounts API from Lynx — 6 operation(s) for externalaccounts.
Lynx Externalnotifications API
The Externalnotifications API from Lynx — 7 operation(s) for externalnotifications.
Lynx Member Expense Controller API
The member-expense-controller API from Lynx — 4 operation(s) for member-expense-controller.
Lynx Members API
The Members API from Lynx — 8 operation(s) for members.
Lynx Payments API
The Payments API from Lynx — 11 operation(s) for payments.
Lynx Relatedpersons API
The Relatedpersons API from Lynx — 7 operation(s) for relatedpersons.
Lynx Substantiation API
The Substantiation API from Lynx — 5 operation(s) for substantiation.
Lynx Transactions API
The Transactions API from Lynx — 13 operation(s) for transactions.
Lynx Uploads API
The Uploads API from Lynx — 2 operation(s) for uploads.
Scroll within the panel for all 21 ·
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.
Lynx Context
JSON-LDSpectral 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.
Lynx API Rules
SPECTRALJSON Schema 60
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.
AdHocNotificationRequest
JSON SCHEMABaseMemberResponse
JSON SCHEMACalculateSalesTaxResponse
JSON SCHEMACardStatusChangeRequest
JSON SCHEMAClientOrgApplicationTokenRequestDoc
JSON SCHEMAClientOrgApplicationTokenResponse
JSON SCHEMAClientOrgExclusionListRequest
JSON SCHEMAClientOrgNotificationConfigurationData
JSON SCHEMAClientOrgNotificationConfigurationResponse
JSON SCHEMAClientOrgRequest
JSON SCHEMAClientOrgSubscribedEventsRequest
JSON SCHEMAClientOrgSubstantiationModelDto
JSON SCHEMAClientOrgSubstantiationModelRequest
JSON SCHEMACommerceCatalogFacetsResponse
JSON SCHEMACommerceCommodityListDocModelResponse
JSON SCHEMACopayCreateResponse
JSON SCHEMACopayGroupGetDetail
JSON SCHEMADocClientOrgCopayGroupCreateRequest
JSON SCHEMADocClientOrgCopayGroupEditRequest
JSON SCHEMADocCopayGroupGetRequest
JSON SCHEMADocCreateClientOrgExternalBankAccountRequest
JSON SCHEMADocLinkAccountRequest
JSON SCHEMADocMemberBankAccountRequest
JSON SCHEMADocMemberBankAccountRequestVerified
JSON SCHEMADocPostDependentCardRequest
JSON SCHEMADocUpdateBankAccountRequest
JSON SCHEMAGetAccountPerformanceResponse
JSON SCHEMAGetAccountPositionsResponse
JSON SCHEMAGetClaimDetailResponse
JSON SCHEMAGetClaimsResponse
JSON SCHEMAGetClientOrgBankAccountBalanceResponse
JSON SCHEMAGetClientOrgExclusionList
JSON SCHEMAGetCommodityDetailDocModelResponse
JSON SCHEMAGetMemberAccountBalanceResponse
JSON SCHEMAGetMemberAccountTransferResponse
JSON SCHEMAGetMemberCardsResponse
JSON SCHEMAGetMemberEnrollmentsByClientResponse
JSON SCHEMAGetMemberExternalAccountsResponse
JSON SCHEMAMemberAccountStatusRequest
JSON SCHEMAMemberCardRequest
JSON SCHEMAMemberRequest
JSON SCHEMAMemberViewCommerceClassificationDto
JSON SCHEMAPatchClientOrgSubstantiationModelResponse
JSON SCHEMAPatchMemberAccountRequestDoc
JSON SCHEMAPatchMemberEnrollmentRequestDoc
JSON SCHEMAPatchMemberEnrollmentResponseDoc
JSON SCHEMAPatchMemberNotificationStatusRequest
JSON SCHEMAPersistClaimsResponse
JSON SCHEMAPostEcommerceRefundRequest
JSON SCHEMAPostMemberAccountTransferRequest
JSON SCHEMAPostMemberClaimRequest
JSON SCHEMAPostMemberEcommerceOrderRequestDoc
JSON SCHEMAPostReplaceEcommerceOrderRequest
JSON SCHEMAPutCommerceSalesTaxRequest
JSON SCHEMAPutMemberClaimRequest
JSON SCHEMAReissueCardRequestDoc
JSON SCHEMAReplaceCardRequestDoc
JSON SCHEMAValidateCouponRequest
JSON SCHEMAScroll within the panel for all 60 ·
Security 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.
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.
Resources
Every other property we hold for Lynx — 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 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lynx · machine-readable index on apis.io
This is an independent, third-party profile of Lynx, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.