> For the complete documentation index, see [llms.txt](https://docs.octora.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.octora.xyz/documentation/introduction/what-is-octora.md).

# What is Octora

Octora is a privacy-focused execution layer for Meteora LP actions on Solana.

Its core goal is simple: help liquidity providers enter positions without making their main wallet the obvious on-chain source of the strategy.

In a direct wallet-to-pool flow, LP actions can be easy to trace. That makes strategies more legible to copy traders, bots, and anyone watching public wallet activity. Octora is designed to reduce that visibility by separating the user’s public wallet from the wallet that ultimately interacts with the liquidity venue.

Today, Octora is best understood as an experimental but meaningful step toward private LP execution. The system includes a frontend app, a backend orchestration layer, a mixer flow, a relayer, stealth wallet handling, and an executor program for liquidity actions.

Octora currently centers on Meteora as its first venue.


---

# 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://docs.octora.xyz/documentation/introduction/what-is-octora.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.
