Research Pilot · Developer Reference

Current endpoints and proposed APIs

The current service exposes a small read-only pilot API at https://soundtitle.org/api. Generation, transmission, marketplace, partner keys and biometric matching remain design proposals and are not available.

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

EndpointMethodCurrent behavior
/api/healthGETService health and release stage.
/api/verify/:profile_idGETRead-only record-status lookup. It does not evaluate identity or purpose authorization and creates no receipt.
/api/ledger/:profile_idGETLimited event metadata for public records only. Restricted, sealed and missing records all return 404.
/api/chain/validateGETTechnical integrity check of the current legacy hash-linked receipt sequence. The response states whether the checked range is complete.
/api/registerPOSTPaused. Always returns 503 REGISTRATION_PAUSED without reading or writing submitted content.

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