Here for your own health? Use Caspia for yourself →
Caspia / Developers / Corpora

Our curated corpora.

Clinician-reviewed knowledge your product can use from day one, reached through the same APIs as everything else. Here is what each one holds, where it comes from, how it stays current and how to call it.

Wellness Goals API

Evidence-based SMART goals

Specific, doable health goals, each tied to the studies behind it and the conditions and people it fits.

2,000+goals

Where it comes from

Drawn from studies and clinical guidelines, all evidence based. Reviewed by board-certified lifestyle medicine clinicians.

How current it is

Continuously updated. New studies are reviewed before they are added.

How to reach it

GET/v1/goals/library
Browse and filter the goal library.
POST/v1/people/{id}/goals
Set a goal for a person and track it.
One goal (example)
{
  "id": "goal_7Hc1",
  "goal": "Walk 20 minutes after dinner, 5 days a week",
  "area": "movement",
  "fits": ["prediabetes", "high blood pressure"],
  "evidence": ["study", "guideline"],
  "reviewed": "2026-10-02"
}
Navigation API

Care navigation: health systems and insurance facts

Where to go for what. Kinds of care matched to a person's need by meaning, linked to the health systems, clinics and departments that offer them, and the insurers, plans and benefits that cover them, with referral rules, booking and quality.

19,000+plan benefit details
400+insurers
220+kinds of care

Where it comes from

Public sources read on a schedule: Medicare quality and coverage data, insurers' published coverage policies, Marketplace plan files and hospitals' published price files. Plus our own research, updates from clinics in our Clinic Directory, and what people report. Every fact keeps its source, and reports that cannot be checked against another source are marked unverified.

How current it is

Each public source is read again on its own schedule, and every value carries the date it was read and the date it stops counting as current. New experiences are added as they come in, with no link to the person who shared them.

How to reach it

POST/v1/navigation/search
Search for care that fits the person.
GET/v1/navigation/options/{id}
One option with coverage, access and sources.
One option (example)
{
  "id": "opt_2Lm8",
  "care": "MRI of the knee",
  "place": "Example Imaging Center",
  "referral_required": true,
  "covered_by": ["Example Health PPO"],
  "source": "insurer coverage policy",
  "as_of": "2026-11-10", "current_until": "2027-02-08"
}
Costs API

Costs and prices

One master list of what care costs: cash prices and insured prices for services, by place and plan, each with where it came from.

Where it comes from

Hospitals' published price files, with their cash and insured rates, and prices people share from their own bills, added without anything that identifies them. Every price keeps its source and how sure we are of it.

How current it is

Price files are read again on a schedule, and every price carries the date it was read and the date it stops counting as current.

How to reach it

GET/v1/costs/prices
Cash and insured prices, with sources.
POST/v1/costs/comparisons
Compare coverage options using these prices.
One price (example)
{
  "care": "MRI of the knee",
  "place": "Example Imaging Center",
  "cash_price": 450,
  "source": "hospital price file",
  "confidence": "high",
  "as_of": "2026-11-10"
}

Every corpus also has

  • Sources on every item. Each answer says where it came from and when.
  • Matched by meaning. A care question in any wording reaches the right kind of care.
  • Clinical judgment stays yours. The corpora inform your product. They are not medical advice.
  • Your terms. Use them through the API plans, or license a corpus directly.
License a corpus directlyTell us what you are building and which corpus you need.
Tell us what you're building

Apply with your idea.

Tell us who you serve and what you want to build. We review every idea, and accepted ideas get sandbox access.

We review every application.