Skip to content

SDKs

Thin wrappers over the REST API. Same resources, same error types, idiomatic types per language.

Not published

None of these packages exist yet. Until they do, the REST API is the only supported interface — it is stable, documented, and a handful of lines in any HTTP client.

Planned

Python

Soon
pip install vemon3.10+

TypeScript

Soon
npm i @vemon/sdkNode 20+

Go

Soon
go get vemon.io/go1.22+

CLI

Soon
brew install vemonmacOS, Linux

Intended shape

Resource methods mirror the endpoint paths, so anything in the API reference maps predictably onto a method name.

python
from vemon import Client

client = Client("vm_live_…")

result = client.healthcare.prices(
    procedure="5372",
    state="FL",
)

print(result.summary.median_charge)
for row in result.data:
    print(row.facility, row.submitted_charge)
typescript
import { Vemon } from "@vemon/sdk";

const client = new Vemon(process.env.VEMON_KEY!);

const result = await client.healthcare.prices({
  procedure: "5372",
  state: "FL",
});

console.log(result.summary.medianCharge);

Until then

The API is plain HTTP with a bearer token. This is the whole integration:

python
import requests

r = requests.get(
    "https://api.vemon.io/v1/healthcare/prices",
    params={"procedure": "5372", "state": "FL"},
    headers={"Authorization": "Bearer vm_live_…"},
    timeout=10,
)
r.raise_for_status()
print(r.json()["summary"]["median_charge"])