# Overview

### What Melody is

Melody is a fully on-chain music network where music becomes programmable, tradable, and interactive.

It enables artists, users, and AI agents to co-create, own, and participate in music as an emerging asset class.

Its purpose is not merely to help people listen to more songs, nor simply to help creators upload more works. Melody is designed to make music legible to markets: ownable, issuable, tradable, settleable, and programmable.\
In traditional music systems, value is concentrated in copyright registries, platform databases, distribution contracts, and opaque payment logic. In Melody, that value path is restructured into open on-chain rails.

#### One-Sentence Definition

**Melody is the infrastructure that turns music into a liquid, interactive, and on-chain market object.**

### What Melody Is Not

Melody is not positioned as:

* another attention-driven streaming platform,
* a short-term speculative wrapper around music,
* or a closed entertainment app whose value depends only on front-end experience.

Its ambition is infrastructural. It aims to define how music enters an on-chain economy.

### Melody‘s Mission

To build a standardized asset, liquidity, and settlement infrastructure for music, so that music can evolve from consumable content into a durable economic object.

### Melody‘s Vision

To make music one of the default native asset classes of the on-chain world, where creation, participation, pricing, and settlement happen within a unified and transparent structure.

### Why This Is an Infrastructure Thesis

Consumer platforms fight for traffic. Market infrastructure competes for historical position, standard-setting power, and reference-market status. Melody aims for the latter.

Once a market establishes trusted issuance rules, observable pricing, and credible settlement, it becomes progressively harder to replace. That is why Melody starts from market structure rather than content distribution


---

# Agent Instructions: 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:

```
GET https://doc.melodylabs.io/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
