Build the FinHealth Record™ into your product

For enterprise product and engineering teams embedding the FinHealth Workflow™ — Diagnosis, Prescription, Delivery, Outcome, Proof — into an existing experience.

What you build with

One connected record. Multiple developer surfaces. Use whichever fits your stack.

REST API

The core surface. Read and write FinHealth Record™ data on a per-person basis — diagnoses, prescriptions, delivery events, outcomes — all anchored to the FinHealth Score® as the diagnostic instrument.

CLI

Operate against the API from a terminal. Useful for ops scripts, batch backfills, scheduled jobs, and internal tooling.

MCP server

Connect Claude (or any MCP-compatible AI agent) directly to your FinHealth Record™ data. Query, analyze, and generate prescriptions in natural language — without writing glue code.

OpenAPI spec

Auto-generated client libraries in any language. Auto-documented integration. The API contract you can pin against.

Webhooks

Subscribe to FHR events — new diagnosis, prescription written, delivery confirmed, outcome recorded — and react in your own systems.

What this enables

• Embed the FinHealth Workflow™ into your existing product without rebuilding the methodology. The FinHealth Score® is the proven diagnostic instrument used by major financial institutions.
• Read and write the FinHealth Record™ on a per-person basis. Track every individual's diagnosis, prescription, delivery, and outcome over time as one connected longitudinal record.
• Run AI agents over your population's data to generate personalized prescriptions, check outcome trajectories, and produce proof-of-impact reports for regulators and boards.
• Plug into the broader financial health ecosystem — your record speaks the same data standard as everyone else's, by design.

Talk to us about embedding →