> For the complete documentation index, see [llms.txt](https://support.rabet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.rabet.io/operation.md).

# Operation

Rabet currently supports up to 17 Stellar Operations. 

1. Payment
2. Path payment strict send
3. Path payment strict receive
4. Manage offer
5. Manage passive offer
6. Inflation
7. Set flag
8. Clear flag
9. Master wight
10. Home domain
11. Signer
12. Threshold
13. Change trust
14. Allow trust
15. Account merge
16. Manage data
17. Bump Sequence

To perform the operation, first, click on the operation button on the home page. Next, enter the operation page. Here there is a box for each operation. By clicking on the Create operation button, create a new operation. By clicking on the Delete button inside each box, delete that operation. Moreover, change the typing of that operation by clicking on the select input at the top of each box. When you have fully entered the information of the operations you want to send, click on the Send button. Then check the information once again on the Confirm page to make sure that it is correct. Eventually, click on the Confirm button.

![](/files/-MTSbzoyqBgB6jjpMyPi)


---

# 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://support.rabet.io/operation.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.