Developers
Build on the MedXT Platform
Layer 10 of our stack exists for you: SDKs, APIs, and sandbox environments. API-first, standards-native (FHIR, HL7, SMART on FHIR, DICOM), with post-quantum security handled for you.
Layer 10 of our stack exists for you: SDKs, APIs, and sandbox environments. API-first, standards-native (FHIR, HL7, SMART on FHIR, DICOM), with post-quantum security handled for you.
Client libraries for JavaScript/TypeScript, Python, Java, and Go. Sign records, anchor CIDs, verify audit chains, and manage decentralized identities with a few lines of code.
OpenAPI-documented endpoints for records, claims, identity, and audit. Native FHIR R4 resources, so your existing healthcare integrations map directly.
A full test network with synthetic patients, test identities, and a faucet of sample transactions. Break things safely before production.
Representative preview of the JavaScript SDK. Sandbox access opens to design partners first: request access.
// 1. Sign and store a record with post-quantum protection + IPFS + audit anchor import { MedXT } from "@medxt/sdk"; const mx = new MedXT({ network: "sandbox", did: clinicianDid }); const result = await mx.records.store({ fhir: labResultBundle, // standard FHIR R4 resource encrypt: "aes-256-gcm", // encrypted before it leaves your process sign: "post-quantum", // NIST post-quantum standards post-quantum signature storage: "ipfs" // content-addressed, decentralized }); console.log(result.cid); // bafkrei... tamper-evident fingerprint console.log(result.auditSeq); // position in the immutable audit chain // 2. Later: verify nothing was altered, anywhere, by anyone const check = await mx.records.verify(result.cid); // { intact: true, signature: "valid", chain: "unbroken" }
The cryptography in this preview is the same you can test right now in the and .
FHIR R4, HL7 v2, SMART on FHIR launch flows, DICOM for imaging, W3C DIDs and Verifiable Credentials for identity, OAuth 2.1 for authorization. If you have integrated healthcare systems before, you already know most of the surface.
Post-quantum signing, encryption, key rotation, and audit anchoring happen inside the SDK. You cannot forget to sign something: every mutating call is signed and chained automatically, the same guarantee the platform gives every user action.
Early SDK access, sandbox credentials, and direct engineering support for teams building on the platform.
Request Developer Access