> For the complete documentation index, see [llms.txt](https://docs.miuro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miuro.ai/creator-ownership-structure/miuro-pay-protocol-real-time-royalty-settlement.md).

# Miuro Pay Protocol — Real-Time Royalty Settlement

### Core Concept: Record = Execute

On traditional music platforms, royalty settlement usually takes 3–6 months and the process is often opaque.

MIURO uses smart contracts to enable near real-time automatic revenue distribution.

### General Workflow

The process works as follows:

1. A user plays, remixes or commercially uses a song.
2. Rights Graph queries the ownership relationship of that song.
3. Miuro Pay Protocol triggers the smart contract.
4. Royalties are automatically and instantly distributed to the relevant parties, including creators, remixers, token holders and node operators.

### Practical Value

* Creators no longer need to wait months for settlement.
* Multiple contributors can receive fair and timely rewards.
* The entire value flow becomes open and transparent, reducing disputes.
* The system supports high-frequency, small-value real-time revenue distribution scenarios.

### Complete Creation and Ownership Loop

These three modules work together to form MIURO’s complete closed loop for creation and ownership:

* **Miuro OS** handles efficient creation and operations.
* **Rights Graph** clearly records ownership relationships.
* **Miuro Pay Protocol** handles real-time value settlement.

Together, they make the entire process from content generation to monetization traceable, measurable and automated.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.miuro.ai/creator-ownership-structure/miuro-pay-protocol-real-time-royalty-settlement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.