Flume Health

Flume Health is a New York based healthcare data platform for the payer ecosystem. Its Relay product is an integration platform (iPaaS) that maps eligibility, claims, and other health plan data between source and destination Endpoints — SFTP, cloud storage, databases, Snowflake, and APIs — through a canonical Flume Data Model, with Connections, Shards, Transactions, and mapping jobs managed from the Flume Console. A newer Context layer adds a knowledge graph over a customer's data estate, natural-language query, and domain agents for actuarial, claims, coding, and compliance work, exposed to AI clients through an OAuth-protected Model Context Protocol endpoint. The public Flume Console API is a 153-operation Swagger 2.0 contract served from console.flumehealth.com, authenticated with OpenID Connect / OAuth 2.0 at auth.flumehealth.com. Flume sold its third-party administrator operations to Vitori Health in 2023 to focus on the software platform.

Flume Health publishes 1 API on the APIs.io network: Flume Console API. Tagged areas include healthcare, health-plans, payers, healthcare-data, and data-integration.

Flume Health’s developer surface includes documentation, API reference, support, authentication, and 26 more developer resources.

🌐 Visit website 📡 Source on GitHub
47.1/100 developing Agent 47/100 agent ready Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
2 APIs 2 MCP Servers
healthcarehealth-planspayershealthcare-datadata-integrationipaaseligibilityclaimsknowledge-graphmcpagent-nativeoauth2data-engineeringinteroperability

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 47.1/100 · developing
Contract Quality 9.7 / 21
Developer Ergonomics 9.2 / 17
Commercial Clarity 8.5 / 17
Operational Transparency 2.3 / 11
Governance 2.1 / 10
Discoverability 6.5 / 9
Regulatory Posture 8.8 / 15
Agent readiness — 47/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
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 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Health 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.
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/. This rating is computed from github.com/api-evangelist/flume-health: 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.

Flume Console API

The REST API for Relay by Flume Health. Manages Accounts, Account Contracts, Connections, Endpoints and their per-protocol secrets and tests (API, cloud storage, database, SFTP,...

Flume Context MCP Server

A remote Model Context Protocol endpoint served by the Flume Console at /api/v1/context/mcp. It is protected by OAuth 2.0 and advertises RFC 9728 protected-resource metadata, re...

MCP Servers 2

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

flume-health-mcp.yml

MCP SERVER

mcp

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Flume Health Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Flume Health Rate Limits

0 limits

RATE LIMITS

Security Posture 3

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

Flume Health Authentication

oauth2/openIdConnect · 3 schemes

SECURITY

Flume Health Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Flume Health Trust Center

SOC 2 Type II, HITRUST CSF, HIPAA

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Flume Health Scopes

14 scopes · implicit

14 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 Login
Login

Documentation 3

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference
 OpenAPI
OpenAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer
MCPServer
 WellKnown
WellKnown
 LLMsTxt
LLMsTxt
 AgentSkill
AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 ErrorCatalog
ErrorCatalog
 DataModel
DataModel
 Lifecycle
Lifecycle
 Conformance
Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 ToolCrosswalk
ToolCrosswalk
 Packages
Packages

Access & Security 5

Authentication, authorization, and security posture

TrustCenter
TrustCenter
 Authentication
Authentication
 OAuthScopes
OAuthScopes
 Compliance
Compliance
 DomainSecurity
DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support
Support
 StatusPage
StatusPage
 RateLimits
RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans

Company 1

The organization behind the API

Website
Website

Other 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: flume-health
name: Flume Health
description: Flume Health is a New York based healthcare data platform for the payer ecosystem. Its Relay product is an integration
  platform (iPaaS) that maps eligibility, claims, and other health plan data between source and destination Endpoints — SFTP,
  cloud storage, databases, Snowflake, and APIs — through a canonical Flume Data Model, with Connections, Shards, Transactions,
  and mapping jobs managed from the Flume Console. A newer Context layer adds a knowledge graph over a customer's data estate,
  natural-language query, and domain agents for actuarial, claims, coding, and compliance work, exposed to AI clients through
  an OAuth-protected Model Context Protocol endpoint. The public Flume Console API is a 153-operation Swagger 2.0 contract
  served from console.flumehealth.com, authenticated with OpenID Connect / OAuth 2.0 at auth.flumehealth.com. Flume sold its
  third-party administrator operations to Vitori Health in 2023 to focus on the software platform.
image: https://flumehealth.com/og-image.png
url: https://raw.githubusercontent.com/api-evangelist/flume-health/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.21'
created: '2026-08-16'
modified: '2026-08-16'
tags:
- healthcare
- health-plans
- payers
- healthcare-data
- data-integration
- ipaas
- eligibility
- claims
- knowledge-graph
- mcp
- agent-native
- oauth2
- data-engineering
- interoperability
apis:
- name: Flume Console API
  description: The REST API for Relay by Flume Health. Manages Accounts, Account Contracts, Connections, Endpoints and their
    per-protocol secrets and tests (API, cloud storage, database, SFTP, Snowflake, Flume Lakehouse), Endpoint Maps, Shards,
    Transactions, Source Files, Business Objects and Instances, Users, Flags, Worker Sizes, Reports, Telemetry, and v2 trade/automap
    jobs — plus the Context Discovery, Context Graph, and Context Knowledge surfaces. Swagger 2.0, 153 operations across 108
    paths, OAuth 2.0 / OIDC bearer auth, account scoping via the X-Flume-Account-ID header, and pageToken/pageSize cursor
    pagination.
  humanURL: https://console.flumehealth.com/api/docs
  baseURL: https://console.flumehealth.com/
  tags:
  - healthcare
  - health-plans
  - data-integration
  - ipaas
  - eligibility
  - claims
  - knowledge-graph
  - oauth2
  properties:
  - type: OpenAPI
    url: openapi/flume-health-console-api-openapi.yml
  - type: APIReference
    url: https://console.flumehealth.com/api/docs
  - type: Documentation
    url: https://docs.flumehealth.com/
  - type: Authentication
    url: authentication/flume-health-authentication.yml
  - type: OAuthScopes
    url: scopes/flume-health-scopes.yml
  - type: Conventions
    url: conventions/flume-health-conventions.yml
  - type: ErrorCatalog
    url: errors/flume-health-problem-types.yml
  - type: DataModel
    url: data-model/flume-health-data-model.yml
  - type: Overlay
    url: overlays/flume-health-console-api-overlay.yaml
  - type: RateLimits
    url: rate-limits/flume-health-rate-limits.yml
- name: Flume Context MCP Server
  description: A remote Model Context Protocol endpoint served by the Flume Console at /api/v1/context/mcp. It is protected
    by OAuth 2.0 and advertises RFC 9728 protected-resource metadata, returning a 401 with a WWW-Authenticate Bearer challenge
    and a resource_metadata pointer to unauthenticated callers, so the live tool list requires an authenticated introspection.
    Discovered by probe; Flume publishes no MCP documentation page.
  humanURL: https://www.flumehealth.com/developers
  baseURL: https://console.flumehealth.com/api/v1/context/mcp
  tags:
  - mcp
  - agent-native
  - knowledge-graph
  - healthcare
  properties:
  - type: MCPServer
    url: mcp/flume-health-mcp.yml
  - type: MCPServer
    url: https://console.flumehealth.com/api/v1/context/mcp
  - type: ToolCrosswalk
    url: mcp/flume-health-tool-crosswalk.yml
  - type: OAuthScopes
    url: scopes/flume-health-scopes.yml
  - type: Authentication
    url: authentication/flume-health-authentication.yml
common:
- type: TrustCenter
  url: security/flume-health-trust-center.yml
- type: Website
  url: https://www.flumehealth.com/
- type: DeveloperPortal
  url: https://www.flumehealth.com/developers
- type: Documentation
  url: https://docs.flumehealth.com/
- type: APIReference
  url: https://console.flumehealth.com/api/docs
- type: Support
  url: https://support.flumehealth.com/portal/en/home
- type: StatusPage
  url: https://status.flumehealth.com/
- type: Login
  url: https://console.flumehealth.com/
- type: TermsOfService
  url: https://www.flumehealth.com/terms
- type: PrivacyPolicy
  url: https://www.flumehealth.com/privacy
- type: GitHubOrganization
  url: https://github.com/flumehealth
- type: OpenAPI
  url: openapi/flume-health-console-api-openapi.yml
- type: MCPServer
  url: mcp/flume-health-mcp.yml
- type: ToolCrosswalk
  url: mcp/flume-health-tool-crosswalk.yml
- type: WellKnown
  url: well-known/flume-health-well-known.yml
- type: Authentication
  url: authentication/flume-health-authentication.yml
- type: OAuthScopes
  url: scopes/flume-health-scopes.yml
- type: Conventions
  url: conventions/flume-health-conventions.yml
- type: ErrorCatalog
  url: errors/flume-health-problem-types.yml
- type: DataModel
  url: data-model/flume-health-data-model.yml
- type: Lifecycle
  url: lifecycle/flume-health-lifecycle.yml
- type: Conformance
  url: conformance/flume-health-conformance.yml
- type: Compliance
  url: conformance/flume-health-conformance.yml
- type: DomainSecurity
  url: security/flume-health-domain-security.yml
- type: Overlay
  url: overlays/flume-health-console-api-overlay.yaml
- type: LLMsTxt
  url: llms/flume-health-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Packages
  url: packages/flume-health-packages.yml
- type: Plans
  url: plans/flume-health-plans-pricing.yml
- type: RateLimits
  url: rate-limits/flume-health-rate-limits.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-08-16'
  status: enriched
  artifacts_added: 27
  pass: local-v1