Skip to main content

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.

​
2026-04-01

Initial public release of the Hasp AI API V1.

​
New endpoints

  • POST /v1/ai/chat — Native Hasp AI inference. Supports streaming and non-streaming. Full Hasp event taxonomy, PHI metadata in responses, meta.request_id on every response.
  • POST /v1/messages — Anthropic-compatible inference. Drop-in for @anthropic-ai/sdk — change baseURL only. Same compliance checks as native surface.
  • GET /v1/ai/messages/{id} — Retrieve a stored inference record by request_id. Returns original messages, token usage, model, stop reason, PHI metadata, and audit trail reference.
  • GET /v1/api_keys — List API keys for your organization.
  • POST /v1/api_keys — Create a new API key with specified scopes.
  • DELETE /v1/api_keys/{keyId} — Revoke an API key.
  • GET /v1/usage — Current billing period usage summary (credits used, credits remaining).
  • GET /v1/usage/budget — Current spend cap configuration.
  • PUT /v1/usage/budget — Update monthly credit cap.
  • GET /v1/compliance/baa — Current BAA status and template for your organization.
  • GET /v1/compliance/baa/acceptances — List BAA acceptances (signed versions).
  • GET /v1/compliance/baa/acceptances/{id} — Retrieve a specific BAA acceptance.
  • GET /v1/compliance/baa/acceptances/{id}/download — Download a signed BAA PDF.
  • GET /v1/audit — Query the audit log for your organization.
  • GET /v1/webhooks — List webhook endpoints.
  • POST /v1/webhooks — Register a new webhook endpoint.
  • DELETE /v1/webhooks/{endpointId} — Remove a webhook endpoint.

​
Models available at launch

  • claude-haiku-4-5 — Fast, low-cost. Available to all plans.
  • claude-sonnet-4-6 — Balanced. Available to all plans. Recommended default.
  • claude-opus-4-6 — Highest capability. Requires explicit opt-in per organization.

​
Authentication

API keys use the wa_live_<32-char-hex> format. The ai:chat scope is required for inference endpoints. The control:read scope is required for control-plane read endpoints. The control:webhooks scope is required for webhook management endpoints.

​
PHI handling

PHI scanning and redaction (powered by Microsoft Presidio) runs on every inference request. The compliance substrate is Hasp-owned — it runs inside the Hasp platform before any content reaches the upstream model provider. See PHI Guard for details.