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 documentation, API reference, getting-started guide, support, authentication, sandbox, changelog, and 19 more developer resources.

43.9/100 thin ▬ flat Agent 48/100 agent ready Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
2 APIs 1 MCP Servers
CompanyInsurancePaymentsCardsFintechHealthCards-as-a-ServiceEmbedded FinanceReimbursementClaims

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 43.9/100 · thin
Contract Quality 5.7 / 25
Developer Ergonomics 13.0 / 20
Commercial Clarity 1.6 / 20
Operational Transparency 7.5 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. 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. Want it done for you? Prioritized profiling — $2,500 →

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.

hihealth-mcp.yml

MCP SERVER

Rate Limits 1

Documented rate limits and quota policies.

Hihealth Rate Limits

0 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 3

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

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: hihealth
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.20'
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: 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