Introduction

The Amplifier Health API analyzes voice recordings (WAV, FLAC, MP3, or M4A, up to 32 MB per file) and returns structured health signals—scores, levels, and workflow-oriented fields—for behavioral, cognitive, and metabolic models.

Analyze endpoints

All endpoints use multipart/form-data: an audio file plus a selector field. Successful responses return a job object (JSON). Errors return a JSON object with code, message, and status — see Error Reference.

Endpoint	Selector	Best for
`POST /v2/models/{model_name}/analyze`	`model_name` in URL	Named multi-sign bundles; returns summary + `signals[]` + `audio_quality`.
`POST /v2/signs/{sign_name}/analyze`	`sign_name` in URL	Single sign; returns one `signal` object + `audio_quality`.

Details, optional fields (e.g. diarization, per-request webhooks), and examples: Model API, Sign API.

Job flow

Submit returns a job object right away (job_id, status: running, result: null). When analysis finishes, obtain the completed job by webhook and/or GET /v2/jobs/{job_id} — see Jobs.

Typed, enumerated values are meant for routing in apps, wellness products, and clinical-adjacent workflows; how to display and interpret them is covered in Interpreting Results and Response Schema.

Per-model evidence tiers (how much published voice-based research supports each model): Model Overview, Models.

Key concepts

Auth (v2). Send X-Account-ID and X-API-Key on every request. Keys and account ID live in the console under API Keys. Legacy v1 uses X-Secret-Key — Legacy API. Walkthrough: Getting Started.
Routing fields. Use enumerated level and recommended_action for UI and automation; keep raw score internal. For model jobs, read result.summary.recommended_action first; for sign jobs, read result.signal.recommended_action. Narrative text under description is supporting context only — follow Interpreting Results for display rules.
audio_quality. Check issues before acting on a result; see Audio Requirements for recording guidance and issue codes.
Outputs are biomarker signals, not diagnoses. recommended_action supports workflow routing; clinical decisions belong with qualified staff.

Note

As-is. All models and API outputs are provided as-is.

Labels such as Established, Emerging, and Investigational describe the depth of published academic and scientific research behind each model and how named model bundles combine those models. They are not a separate commercial tier, contract, or entitlement.