Developer Reference — SoundTitle

No audio or biometric API

Do not send recordings, voiceprints, embeddings, identity documents or other sensitive information to any current endpoint. Browser cross-origin API access is disabled.

Current public pilot

Endpoint	Method	Current behavior
`/api/health`	GET	Service health and release stage.
`/api/verify/:profile_id`	GET	Read-only record-status lookup. It does not evaluate identity or purpose authorization and creates no receipt.
`/api/ledger/:profile_id`	GET	Limited event metadata for public records only. Restricted, sealed and missing records all return 404.
`/api/chain/validate`	GET	Technical integrity check of the current legacy hash-linked receipt sequence. The response states whether the checked range is complete.
`/api/register`	POST	Deprecated / retired. It is not an account, password or identity endpoint.

Account registration

Use account.soundtitle.org/register for passwordless email verification or Passkey sign-in. Google and Apple entry points are available only when their provider configuration is complete. Do not send recordings or identity documents to this API.

Verification response

{
  "profile_id": "STO-0001",
  "registration_status": "ACTIVE",
  "queried_purpose": "commercial",
  "purpose_authorization": "NOT_EVALUATED",
  "assurance_level": "SELF_DECLARED",
  "notice": "Record status only; identity and purpose authorization have not been verified."
}

registration_status and purpose_authorization are deliberately separate. Clients must never interpret ACTIVE as approval for the queried purpose.

Proposed v1 capabilities — not implemented

The whitepaper explores identity and liveness assurance, scoped consent, revocation, signed receipts, generation, real-time transmission, partner access and payment settlement. None of these capabilities is available in the current public service. A live call is not consent by itself: any future session must have explicit, purpose-limited, revocable authorization.

Integration rules