Models
Named models are pre-configured sign bundles tuned for specific health contexts. Submit audio to POST /v2/models/{model_name}/analyze with the model name that best matches your deployment context. For detailed sign composition and usage scenarios for each model, see Models reference.
Available models
| Model | Domain | Signs |
|---|---|---|
haven | Clinical Behavioral Health | mood-disruption, anxiety, stress, hypervigilance, attention-dysregulation, fatigue |
pulse | General Wellness | mood-disruption, anxiety, stress, fatigue, elevated-blood-pressure, dehydration |
clarity | Cognitive Health | cognitive-impairment |
aria | Women's Health | mood-disruption, anxiety, fatigue, elevated-blood-pressure, elevated-androgens, dehydration, iron-deficiency |
apex | Sports & Human Performance | stress, anxiety, fatigue, head-impact, cognitive-load, cardiovascular-strain, dehydration |
harbor | Recovery & Substance Use | anxiety, stress, emotional-destabilization, alcohol-use-pattern, substance-use-pattern |
tide | Cardiometabolic & Body Baseline | elevated-blood-pressure, fatigue, metabolic-load, dehydration, iron-deficiency |
breath | Respiratory Health | airway-obstruction-pattern, allergy |
How to choose a model
Choose the model that best matches the clinical or wellness context in which you are deploying. The right model is determined primarily by who your end users are and what signals are most clinically relevant for that population.
If your platform serves a general behavioral health population — primary care, teletherapy, employee wellness — start with haven or pulse. If your context is specialized — substance use recovery, cognitive assessment, sports medicine — use the corresponding specialized model, which is configured with the signs most validated for that population.
If your platform serves multiple population contexts, submit separate requests with the most specific model name for each participant group. This ensures each group's signals are evaluated with the signs most validated for that context.
Discover available models and their current sign composition at runtime with GET /v2/models or GET /v2/models/{model_name}.
See Models reference for full detail on each model. If no existing model fits your deployment context, contact support@amplifierhealth.com to discuss your requirements.