> For the complete documentation index, see [llms.txt](https://guides.getalby.com/creators/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.getalby.com/creators/value-for-value-podcaster-guide/1.-what-is-value-for-value.md).

# 1. What is Value for Value?

The term [“Value for Value”](https://value4value.info/) describes an innovative approach to creator compensation made possible by initiatives like Podcasting 2.0 and the Bitcoin Lightning Network. The fundamental concept, however, is not new. For example, when a hat is passed around following a public music performance, the audience chips in what they feel is a fair value for the performance, and the artist receives the payment directly, without a middleman taking a cut.

The online Value for Value model works in a similar way because audiences can, with the click of a button, offer what they feel is a fair value for any given performance. Payments are sent instantaneously from the audience to the creator via a global payment network, the Bitcoin Lightning Network.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guides.getalby.com/creators/value-for-value-podcaster-guide/1.-what-is-value-for-value.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.