Autopay for Music, Fans & APIs
Fans invest in tracks, artists earn what they’re worth — with on-chain pay-per-play and verifiable splits baked into HTTP.
Frictionless
No accounts, no API keys. A single Only402-Pay header does per-request royalties for players, apps and agents.
Fair & Instant
Solana + Jito priority fees ⇒ sub-second paths and low cost. Every play pays, instantly, on-chain.
Verifiable Splits
Label, artist, producer? Split trees settle on-chain. We stream live transactions below.
What you get
- On-chain Spotify-style payouts.
- Micropayment-friendly per-play pricing.
- Programmable splits, caps & routing.
- Transparent accounting via public RPC.
Trade-offs
- Public RPC rate limits apply.
- End users need a wallet or managed signer.
- Latency can vary with network congestion.
Client / Player
HTTP request with signed Only402-Pay header. The player handles retries & batching while a track streams.
Payment Router
Chooses route (Jito Tip / priority fee), verifies proof, applies split tree and forwards to the music API.
Settlement
On-chain confirmation + webhooks + receipts. Each play leaves a verifiable trail for fans & artists.
Only402-Pay per chunk/second.getSignaturesForAddress (merged across tip accounts) and resolve each new signature with getTransaction to show status & effective fee. Starts automatically.Live Royalties
Streaming via HTTPS polling (public RPC friendly)| Signature | Time | Action | From | To | Amount | Value | Token |
|---|
Why not WebSockets?
Many public endpoints block logsSubscribe in browsers (CORS / rate limits). HTTPS polling stays robust without a private RPC.
Can I bring my own RPC?
Yes. Paste any HTTPS RPC in settings; the feed restarts automatically. For production, use a pooled provider.