> For the complete documentation index, see [llms.txt](https://documentation.record.nexus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.record.nexus/otc/instructions-for-otc-transactions.md).

# Instructions for OTC Transactions

To simplify the process of purchasing RECORD tokens, the Web3 Music Association has established a straightforward mechanism. Please follow the steps outlined below: 

### 1. Submission of Interest 

Complete and submit the attached form to express your interest and secure approval for the OTC terms with W3M. 

### 2. Finalising Terms 

Once we receive your form, we will follow up via email to confirm and finalize the transaction details, including: 

* Amount of tokens 
* Price 
* Lock period 
* Release schedule 
* Discount

### 3. Simplified Future Transactions 

Once the initial terms are agreed upon, the conditions will remain valid for future OTC transactions with the same wallet address. This means you won’t need to sign or approve multiple times for subsequent transactions. 4. Data Usage • All information provided will be used exclusively for the purpose of completing token OTC transactions.

This mechanism ensures an efficient and seamless process for multiple deals associated with your specified wallet address.

If you have any questions or require further clarification, please feel free to contact us.

{% hint style="info" %}
Form: [https://forms.gle/qUXchNsL9CLrmH6w5<br>](<https://forms.gle/qUXchNsL9CLrmH6w5&#xA;>)GTC: <https://resources.web3music.org/otc/w3m-token-otc-transaction>
{% endhint %}


---

# 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://documentation.record.nexus/otc/instructions-for-otc-transactions.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.