Build
Developer guide
MoryToken is meant to be an open foundation — one shared layer for access, rewards and proof that anyone can build solutions on.
Status
The public Developer API is in active development. The examples below are illustrative and show the intended shape — endpoints and auth may change before release.
Get started
- 1
Create a Morylen developer account
Register your app and get a client id. Users authenticate with their own MoryAudio / Morylen account.
- 2
Read points & proofs
Query a user's point balance and their earned badges and proofs.
- 3
Grant access
Unlock content or features when a user holds the right points, membership or badge.
- 4
Go on-chain (later)
Once enabled per country, read on-chain badges and verify proofs on Polygon.
Authenticate
Server-to-server calls use a bearer token issued for your app. Never expose secrets in the browser.
Authorization
Authorization: Bearer <app-token>
Content-Type: application/jsonRead a proof
GET /v1/proofs/:userId
curl https://api.moryaudio.com/v1/proofs/usr_8f2c \
-H "Authorization: Bearer <app-token>"
# 200 OK
{
"userId": "usr_8f2c…",
"badges": ["verified_artist", "top_reviewer"],
"memberships": ["community_pro"],
"onchain": false
}On-chain design
What goes on-chain, and what never does:
- On-chain — token transfers, NFT badges, access proofs, memberships and activity hashes.
- Never on-chain — personal data, emails, messages, payment details or copyrighted originals.
Non-custodial
Integrations never custody user funds or private keys. On-chain features are enabled gradually, per country, after legal review.