hi.health website screenshot

hi.health

hi.health is a cashless, real-time claims and payments platform for the insurance industry, now operated as "hi.health by Pliant" after joining Pliant. It replaces legacy reimbursement models with instantly issued virtual and physical cards whose spend is programmatically controlled per policy, merchant, currency and country. Members pay nothing upfront: eligible claims are settled in real time at the point of care across health, home, travel, corporate and auto insurance lines, and structured transaction data is streamed back to insurers for dashboards, reconciliation and fraud prevention. The developer surface is Pliant's PCI-DSS-certified Cards-as-a-Service (CaaS) and Pro API: OAuth2 client-credentials access, asynchronous callback/webhook events, and a full sandbox, which partners embed to issue and manage cards, cardholders, transactions, receipts, payments and external transfers.

hi.health publishes 2 APIs on the APIs.io network. Tagged areas include Company, Insurance, Payments, Cards, and Fintech.

The hi.health catalog on APIs.io includes 1 event-driven AsyncAPI specification.

hi.health’s developer surface includes engineering blog, pricing, signup flow, documentation, API reference, getting-started guide, support, and 25 more developer resources.

53.0/100 developing ▬ flat Agent 34/100 agent ready Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
2 APIs 1 MCP Servers
CompanyInsurancePaymentsCardsFintechHealthCards-as-a-ServiceEmbedded FinanceReimbursementClaims

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/hihealth: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

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

Pliant Cards-as-a-Service (CaaS) API

The embedded credit-card API that powers hi.health. Partners issue and manage cards, cardholders, transactions, receipts, payments, statements and external transfers, with OAuth...

Pliant Pro API

The customer-facing Pro API for programmatic access to Pliant credit-card data and features (cards, cardholders, transactions, receipts, accounting, payments).

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Rate Limits 1

Documented rate limits and quota policies.

Hihealth Rate Limits

1 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 3

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

Hihealth Authentication

oauth2 · 1 scheme

SECURITY

Hihealth Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Hihealth Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Hihealth Scopes

3 scopes

3 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Access & Security 7

Authentication, authorization, and security posture

Scroll for all 7

Operate 5

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: hihealth
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/hihealth.png
name: hi.health
description: 'hi.health is a cashless, real-time claims and payments platform for the insurance industry, now operated as
  "hi.health by Pliant" after joining Pliant. It replaces legacy reimbursement models with instantly issued virtual and physical
  cards whose spend is programmatically controlled per policy, merchant, currency and country. Members pay nothing upfront:
  eligible claims are settled in real time at the point of care across health, home, travel, corporate and auto insurance
  lines, and structured transaction data is streamed back to insurers for dashboards, reconciliation and fraud prevention.
  The developer surface is Pliant''s PCI-DSS-certified Cards-as-a-Service (CaaS) and Pro API: OAuth2 client-credentials access,
  asynchronous callback/webhook events, and a full sandbox, which partners embed to issue and manage cards, cardholders, transactions,
  receipts, payments and external transfers.'
url: https://raw.githubusercontent.com/api-evangelist/hihealth/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
x-acquired-by: pliant
x-tier: profiled
x-tier-reason: enriched-from-provider-surface
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Insurance
- Payments
- Cards
- Fintech
- Health
- Cards-as-a-Service
- Embedded Finance
- Reimbursement
- Claims
apis:
- name: Pliant Cards-as-a-Service (CaaS) API
  description: The embedded credit-card API that powers hi.health. Partners issue and manage cards, cardholders, transactions,
    receipts, payments, statements and external transfers, with OAuth2 client-credentials auth, asynchronous callbacks and
    a PCI-DSS-certified data path (pci-api.getpliant.com).
  humanURL: https://partner.getpliant.com/
  baseURL: https://partner-api.getpliant.com/api/
  properties:
  - type: Documentation
    url: https://partner.getpliant.com/
  - type: APIReference
    url: https://partner.getpliant.com/reference
  - type: GettingStarted
    url: https://partner.getpliant.com/docs/introduction.md
  - type: Authentication
    url: https://partner.getpliant.com/docs/authenticated-api-usage.md
  - type: LLMsTxt
    url: llms/hihealth-llms.txt
- name: Pliant Pro API
  description: The customer-facing Pro API for programmatic access to Pliant credit-card data and features (cards, cardholders,
    transactions, receipts, accounting, payments).
  humanURL: https://customer-api.getpliant.com/
  baseURL: https://partner-api.getpliant.com/api/
  properties:
  - type: Documentation
    url: https://customer-api.getpliant.com/
  - type: APIReference
    url: https://customer-api.getpliant.com/reference
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Blog
  url: https://getpliant.com/en/blog
- type: Pricing
  url: https://getpliant.com/en/pricing
- type: SignUp
  url: https://app.getpliant.com/?language=en
- type: PrivacyPolicy
  url: https://getpliant.com/en/privacy-policy
- type: TermsOfService
  url: https://getpliant.com/en/imprint
- type: LinkedIn
  url: https://www.linkedin.com/company/getpliant
- type: Website
  url: https://www.getpliant.com/en/industry/insurance-payments/
- type: DeveloperPortal
  url: https://partner.getpliant.com/
- type: Documentation
  url: https://partner.getpliant.com/
- type: APIReference
  url: https://partner.getpliant.com/reference
- type: GettingStarted
  url: https://partner.getpliant.com/docs/introduction.md
- type: Support
  url: https://help.getpliant.com/
- type: StatusPage
  url: https://help.getpliant.com/
- type: Deprecation
  url: https://partner.getpliant.com/docs/versioning.md
- type: Authentication
  url: authentication/hihealth-authentication.yml
- type: OAuthScopes
  url: scopes/hihealth-scopes.yml
- type: Conventions
  url: conventions/hihealth-conventions.yml
- type: RateLimits
  url: rate-limits/hihealth-rate-limits.yml
- type: ErrorCatalog
  url: errors/hihealth-problem-types.yml
- type: Lifecycle
  url: lifecycle/hihealth-lifecycle.yml
- type: Sandbox
  url: sandbox/hihealth-sandbox.yml
- type: Webhooks
  url: asyncapi/hihealth-webhooks.yml
- type: MCPServer
  url: mcp/hihealth-mcp.yml
- type: LLMsTxt
  url: llms/hihealth-llms.txt
- type: WellKnown
  url: well-known/hihealth-well-known.yml
- type: SecurityTxt
  url: well-known/hihealth-security.txt
- type: VulnerabilityDisclosure
  url: security/hihealth-vulnerability-disclosure.yml
- type: Security
  url: https://www.getpliant.com/.well-known/security.txt
- type: DomainSecurity
  url: security/hihealth-domain-security.yml
- type: Conformance
  url: conformance/hihealth-conformance.yml
- type: Compliance
  url: conformance/hihealth-conformance.yml
- type: ChangeLog
  url: changelog/hihealth-changelog.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/hihealth"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hihealth/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hihealth/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.