# Intended User Actions

### Issuer

Issuers primarily interface with Auctioneers to create markets. If they choose to use a Callback contract, it must be deployed before creating a market. After the market is created, it will need to be whitelisted on the Callback. The same Callback can be used for multiple markets across multiple Auctioneers. 

Issuers can end markets at any time on the Auctioneer and set certain variables for a market after creation, such as `tuneInterval`, `tuneAdjustmentDelay`, and `debtDecayInterval`. 

However it is not recommended to change these unless the Issuer is experienced and knowledgeable about how it will impact the market operation. <mark style="color:red;">If in doubt, please reach out to Bond Protocol team.</mark>

<figure><img src="/files/1Ena4LU2baNkVSBaUAnE" alt=""><figcaption></figcaption></figure>

### End user

End users primarily interact with the Aggregator to get market information and the Teller to purchase and redeem bonds.&#x20;

The following diagram shows the main actions expected from end users:

<figure><img src="/files/23G62xhDl0xlU9oZpM0f" alt=""><figcaption></figcaption></figure>


---

# 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://dev.bondprotocol.finance/smart-contracts/bond-system/intended-user-actions.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.