Read It Before You Trust It.

The public REST definition, language clients and integration tools are open for inspection. Nobody has to take our word for how Care, Consent and Claims work.

Explore GitHub Read the docs

Install a Heyrafiki SDK

Choose your language and copy the install command.

JavaScript

$npm install @heyrafiki/rafiki-js@0.1.0-beta.1

Python

$python -m pip install --pre heyrafiki==0.1.0b2

Go

$go get github.com/heyrafiki/rafiki-go@v0.1.0-beta.2

.NET

$dotnet add package heyrafiki --version 0.1.0-beta.3

Rust
```
$cargo add heyrafiki@0.1.0-beta.2
```

The API definition everything else is built on.

Public Session, Claim and remittance operations move through the same versioned definitions. Proving Ground turns consequential guarantees into tests others can run.

OpenAPI definition

Practitioners, Sessions, eligibility, Cover, authorisations, Claims and remittances, in one versioned API definition.

heyrafiki/contract04

Developer docs

Every guide, reference and Webhook, from one public source.

heyrafiki/docs04

JavaScript SDK

Typed server-side access for JavaScript and TypeScript services.

heyrafiki/rafiki-js04

Proving Ground

Executable conformance evidence and failure boundaries for the public API definition.

heyrafiki/proving-ground03

Language clients

In the language your Team already writes.

The same API definition has a native client for each stack.

Python

Sync and async, for Python services.

heyrafiki/rafiki-py04

Go

For institutional integrations at scale.

heyrafiki/rafiki-go04

.NET

Typed access for C# and .NET services.

heyrafiki/rafiki-net04

Rust

Async, for systems that cannot drop a Claim.

heyrafiki/rafiki-rs04

Model Context Protocol

Governed agent access.

An agent reaches the Platform through the same authorization boundary a person does: named scopes, an explicit grant, and audit evidence for every call. Request access to evaluate what is available.

Read the MCP guide Request access

Inspect the public interfaces and evidence.

Defensive thresholds, fraud rules and production data remain private because exposing them would weaken the safeguards they enforce.

What you can inspect and extend

The REST API definition and the public Developer Docs
SDKs, the Heyrafiki CLI and cross-language conformance tests
Proving Ground tests for Consent authority, evidence timing and financial identities

What stays private

Safety and triage thresholds
Anti-fraud and abuse controls
Practitioner verification checks and their evidence
Production data and payer-bound rules

Read the boundary

Contribute

Infrastructure should outlast the company that started it.

Infrastructure a whole Sector depends on should not belong to one Company alone.

Contributing guide Why open source