The Hasp AI API lets you send HIPAA-compliant AI requests from any backend. It is a separate surface from the App Builder SDK — it uses API keys instead of session cookies, and it calls a different base URL.Documentation Index
Fetch the complete documentation index at: https://docs.usehasp.com/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
Authentication
Every request requires anAuthorization header with a Bearer token:
wa_live_ identifies a live key. Keys are shown in plaintext exactly once on creation — copy it before closing the modal.
All requests also require an active Business Associate Agreement (BAA) on your organization. Without one, every request returns 402 BAA_REQUIRED. Sign the BAA in Settings → Compliance.
Your first request
Drop-in Anthropic SDK
If you already use@anthropic-ai/sdk, change one line:
API surfaces
| Surface | Path prefix | Use when |
|---|---|---|
| Native | /v1/ai/* | New integrations — full Hasp features (PHI guard metadata, store flag, future tool use) |
| Anthropic-compat | /v1/messages | Existing code using @anthropic-ai/sdk — drop-in replacement |
| Control plane | /v1/* | Manage API keys, webhooks, and inspect usage |
What’s next
- POST /v1/ai/chat — native streaming chat, full event taxonomy
- POST /v1/messages — Anthropic SDK drop-in
- PHI Guard — how PHI detection and redaction work
- API Keys — create and revoke keys programmatically