Trust as a service
Add Keyra trust
to your music application
Ciright Beats is the flagship verified direct-to-fan network. Keyra is designed so third-party music platforms can consume the same trust plane.
Features can be copied. Trust infrastructure is the moat.
API surface
Keyra Trust APIs
Native attestation endpoints are BETA when KEYRA_API_KEYS is set. External Keyra federation remains not live.
Beta Authenticate with Authorization: Bearer <key> or X-Keyra-Api-Key
POST /api/keyra/v1/verify— Verify Fan / Artist / Venue / Ticket attestationGET /api/keyra/v1/fan-status?userId=— Check Fan Status (passport ladder)POST /api/keyra/v1/content-authorization— Check Content AuthorizationPOST /api/webhooks/stripe·POST /api/webhooks/keyra— inbound webhooks
VerifyFanVerify FanBetaVerifyHumanVerify HumanPlannedVerifyArtistVerify ArtistBetaVerifyRepresentativeAuthorityVerify Representative AuthorityBetaVerifyDeviceVerify DevicePlannedCheckAgeEligibilityCheck Age EligibilityPlannedCheckFanStatusCheck Fan StatusBetaAuthorizePresaleAuthorize PresaleBetaVerifyTicketTransferVerify Ticket TransferBetaAuthorizeTransactionAuthorize TransactionBetaVerifyAIAgentVerify AI AgentPlannedVerifyArtistCommunicationVerify Artist CommunicationBetaCheckContentAuthorizationCheck Content AuthorizationBetaRecordConsentRecord ConsentIn developmentRevokeAuthorizationRevoke AuthorizationBeta
Design principles
Evidence over assertion
Every response should carry evidence level, scope, timestamp, and revocation state where applicable.
- Progressive trust — match assurance to risk
- Purpose limitation — collect only what the action requires
- Privacy by design — minimize sensitive payload exposure
- Auditability — material actions produce events
- Revocation first — every grant can be withdrawn
- No fraud labels from missing records alone
- Partner-safe — integrate with systems of record you already use
- Agent accountability — no unlimited implicit AI authority