Cryptographic Anchoring · Biometric Identity · Privacy-First Encryption — built for SoundExchange and the most demanding rights‑holder audits.
Every metadata reconciliation is hashed via SHA-256 and anchored to the Monad Blockchain.
Creates an immutable "Proof of Audit" that can be verified by SoundExchange, PROs, or any court at any time — without relying on a central database.
We don't rely on email verification. Our protocol requires facial-recognition identity anchoring before a Digital Handshake is finalized.
Meets institutional KYC standards and ensures that every party in a handshake is a real, verified individual — eliminating fraudulent claims and identity spoofing.
Engineered in Sweden, our data handling exceeds US standards. We utilize "Privacy-First" encryption throughout.
Sensitive rights‑holder data is only accessible to verified legal counsel and the SoundExchange ingestion portal. All other access is cryptographically blocked — even from us.
Only when all three layers are satisfied does a Digital Handshake become final and a royalty payment become triggerable. This is how we protect the industry's most valuable asset — trust.
Every audit package includes a verifiable chain‑of‑custody document that matches SoundExchange's ingestion requirements. No manual reconciliation — just cryptographic proof.
Primary endpoints powering the SMPT security stack.
/v1/isrc-integrity
Returns the health and conflict status of a recording. Verifies that ISRC metadata is consistent across all active nodes and produces a tamper-proof SHA-256 hash of the result anchored to the Monad blockchain.
/v1/verify-handshake
Confirms the SHA-256 hash of a split agreement. Validates that all parties in a Digital Handshake have been biometrically verified and that the agreement has not been altered since signing.
/v1/market-signal
Pulls the 48M+ stream data from the global node network. Returns real-time market signal data aggregated across all registered DSPs, used to trigger royalty thresholds and audit flags.
Full OpenAPI specification available via the API Documentation page.