Overview
How the pieces fit together
How Suede's creator products, social surfaces, musician apps, and x402 agent payments fit together.
Last updated
Connected products, separate boundaries
Suede spans creator tools, a social network, musician practice apps, and paid agent endpoints. The surfaces share a product family and can exchange user-approved context, but each workflow has its own availability, authentication, and payment requirements.
Rights-workflow status
Registration happens only in the IP Registry, and only when you file a work there. No other product should imply that uploading, creating, or posting automatically registers a work, proves ownership, creates enforceable permissions, or configures payment splits.
Read the proof-of-creation framework for the current status and for what a fingerprint, timestamp, and creator claim can and cannot establish.
The human surfaces
Suede Social, Strumly, and Muse are where people actually spend time. Social is distribution and community. Strumly and Muse are the practice room: an AI guitar coach and a musician companion that meet creators while the work is still being made.
The machine surfaces
Agent Studio and the x402 endpoints are where software does the buying. An agent discovers a Suede endpoint, reads a price it can parse, signs a USDC payment on Base, and receives the result in the same exchange. No invoice, no account manager, no license PDF.
The x402 protocol is the payment rail: an open standard for paying over HTTP. Each paid resource states its price and payment requirements before a call. That payment is for the resource call; it should not be described as an automatic royalty or rights settlement for an underlying work.
Suede also publishes machine-readable manifests, an x402 manifest and an agent card, at well-known URLs so that agents can discover what Suede offers without a human pointing them at it.
Registry and Vaults status
Registry registration is live; the public Vaults entry pages are not part of the current product path. Read the proof-of-creation framework for what a record does and does not prove.
Why this shape
Three design goals connect the product family:
- Keep source context and user-approved metadata portable.
- Make prices, permissions, and status legible to both humans and machines.
- Keep product boundaries explicit so one surface never silently claims an action happened elsewhere.
Boundaries worth knowing
Suede does not adjudicate disputes between claimants. A fingerprint identifies bytes; a timestamp can support evidence that a fingerprint was recorded at a time; and a creator claim remains a claim. None proves that no earlier version existed elsewhere.