Royal

Royal is a music-and-crypto company backed by a16z and Paradigm that originally let fans buy tokenized shares of songs (Limited Digital Assets, or LDAs) so they could earn streaming royalties alongside the artists they support. As of mid-2026 the public site at royal.io states the company is "reinventing itself" and is between products, keeping only its legal pages and LDA support live; it publishes no developer portal, documentation, OpenAPI, SDKs, or public API surface at this time. This profile tracks Royal as an API Evangelist network company and will be enriched further if and when a public API or developer program appears.

Royal is profiled on the APIs.io network. Tagged areas include Company, Music, Royalties, Crypto, and Web3.

Royal’s developer surface includes support and 4 more developer resources.

11.8/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
0 APIs
CompanyMusicRoyaltiesCryptoWeb3NFTFan Engagement

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 11.8/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.9 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/royal: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Royal Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: royal
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/royal.png
name: Royal
description: Royal is a music-and-crypto company backed by a16z and Paradigm that originally let fans buy tokenized shares
  of songs (Limited Digital Assets, or LDAs) so they could earn streaming royalties alongside the artists they support. As
  of mid-2026 the public site at royal.io states the company is "reinventing itself" and is between products, keeping only
  its legal pages and LDA support live; it publishes no developer portal, documentation, OpenAPI, SDKs, or public API surface
  at this time. This profile tracks Royal as an API Evangelist network company and will be enriched further if and when a
  public API or developer program appears.
url: https://raw.githubusercontent.com/api-evangelist/royal/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- paradigm
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Music
- Royalties
- Crypto
- Web3
- NFT
- Fan Engagement
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://royal.io
- type: TermsOfService
  url: https://royal.io/legal/tos.html
- type: PrivacyPolicy
  url: https://royal.io/legal/privacy.html
- type: Support
  url: https://royal.io/lda-support.html
- type: DomainSecurity
  url: security/royal-domain-security.yml
x-enrichment:
  date: '2026-07-21'
  status: minimal
  artifacts_added: 1
  pass: local-v1