Skip to main content

Coming Soon

SDK endpoints and packages are in development. Use this page as a preview of the planned surfaces; production access is not live yet.

Quick facts

  • First language: TypeScript/Node
  • Surfaces: HTTPS APIs, health event schemas, on-chain Solana interfaces
  • Goal: let external oracles, apps, and capital plug into OmegaX

OmegaX SDK

The OmegaX Protocol is designed as open infrastructure: anyone should be able to plug into the health oracle layer and the on-chain health capital markets. The SDK exists to make that practical.

It gives external builders a way to:

  • Create and manage reward pools and future coverage structures.
  • Connect their own apps, devices, or platforms as health data sources or oracles.
  • Read pool state, payouts, and health events in a normalized way.
  • Integrate with the protocol as:
    • Employers / HR platforms
    • Digital health apps and device makers
    • Insurers and TPAs
    • DeFi / capital providers

The SDK is not a walled garden. It wraps:

  • Standard HTTPS APIs
  • Standardized health event schemas
  • On-chain contract interfaces on Solana

into a developer-friendly surface.

Support will roll out gradually, starting with:

  • TypeScript/Node

What You Can Build​

With the OmegaX SDK, third parties will be able to:

  • Sponsor & manage pools
    • Create reward pools for their users, employees, or patients.
    • Define health event conditions and payout logic.
    • Fund pools and track utilization over time.
  • Act as a health oracle
    • Emit health attestations for your own users, if you run your own health logic.
    • Use OmegaX’s scoring endpoints to convert raw data into standardized events.
  • Build capital & analytics products
    • Read pool states, event aggregates, and payout flows.
    • Build dashboards, structured products, or risk views on top of OmegaX data.

OmegaX is opinionated about what should exist (verifiable health events driving capital), but flexible in who plugs in and how.

SDK Surfaces​

The SDK is organized into several modules:

  1. Admin / Sponsor Module (employers, providers, insurers, HR / benefits platforms)

    • Create & configure reward pools.
    • Manage cohorts, enrollment, and eligibility.
    • Read pool performance and health outcome aggregates.

  2. Oracle Module (digital health apps, device makers, platforms acting as oracles)

    • Register your platform as a trusted data source.
    • Submit health attestations for your users.
    • Optionally use OmegaX scoring APIs for risk & outcome computation.

  3. Analytics & Markets Module (capital providers and analytics platforms)

    • Read pool state and payout history.
    • Query event aggregates and health improvement statistics.
    • Plug OmegaX into internal risk and pricing models.

  4. Core Models

    • Pool
    • Member
    • HealthEvent
    • Attestation
    • Payout
    • FeeEvent

These models mirror the protocol’s internal objects so you can speak the same language as the chain and the oracle.

Integration Modes​

Choose one or more modes:

  • Off-Chain First (SDK + API)

    • Use SDK methods that call OmegaX HTTPS APIs.
    • Ideal for HR platforms, SaaS providers, or digital health apps.

  • Hybrid (SDK + On-Chain)

    • Use the SDK for pool and event management.
    • Interact directly with Solana contracts when you need more control.

  • On-Chain First

    • For teams already on Solana:
      • Interact with OmegaX contracts directly.
      • Use the SDK for event schema helpers and attestation tooling.

Coming Soon​

The protocol and SDK are being developed in parallel with:

  • Documentation for Solana contracts and ABI-style interfaces.
  • A stable health event schema registry.
  • Sandbox and test environments for integration.

The goal is to make integrating with OmegaX feel less like “healthcare” and more like any serious DeFi or infra protocol:

  • Clean primitives
  • Clear contracts
  • No hidden manual processes behind the scenes