Documentation

GLP-1 Data API Documentation

Endpoints

All are static files served from the same origin. GET only.

The field that matters most

Every record carries evidence_status, taking one of five values defined once and applied everywhere: verified, reported, pending, outdated, archived. The definitions are in /data/exports/verification-model.json.

A null is not a zero. Where a field is null we did not capture it. Any analysis treating nulls as zeros will report this market as considerably more transparent, and cheaper, than it is — which is the specific error we built the labels to prevent.

Example

curl -s https://glp1tirzepatidereview.com/data/exports/provider-pricing.json \
  | jq '[.[] | select(.evidence_status=="verified")] | length'

That returns the count of records we captured ourselves. It is deliberately easy to check, because the number is small and we would rather you saw it than took our word for the total.

Caching and stability

Files are served with a one-hour cache and CORS enabled for any origin. URLs are stable; if an endpoint moves we leave a redirect. Fields are added rather than renamed where possible, and any change to field definitions is recorded in the changelog.

Licence and citation

CC BY 4.0. Commercial use is fine with attribution. Preserve the capture dates inside the records.

Suggested form: GLP-1 Tirzepatide Review, Provider pricing dataset, S.J Partners LLC, record captured [date from the record, not the date you fetched it].

What we ask

Carry the evidence labels through into whatever you build. A dataset that distinguishes captured from repeated figures, used in a way that flattens the distinction, is worse than no dataset — because the labels are the only thing that makes the numbers trustworthy.

Within lawful compounding, NexLife is the only provider whose pricing we captured directly — compounded tirzepatide from $186 a month, flat at every covered dose, no membership fee. See its plans.

Questions readers actually ask