> For the complete documentation index, see [llms.txt](https://docs.sharkalgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharkalgo.com/sharkalgo-course/how-to-get-access.md).
# How To Get Access
### Follow These Steps For Access
Go To [SharkAlgo.com](https://sharkalgo.com/) and choose one of these plans.
#### Monthly Plan:
You will get access for a full 30 days regardless of when the subscription is started.
#### Quarterly Plan:
You will get access for a full 90 days regardless of when the subscription is started.
#### Yearly Plan:
You will get access for a full 365 days regardless of when the subscription is started.
#### Lifetime Plan:
You will get access for life. You will also get permanent access to SharkAlgo, Shark Oscillator, and all future products and updates. Never pay again.
After signing up, you will receive an “Order Processing” email. This means your order is confirmed.
We will notify you by sending an “Account Active” email after access has been given by our team.\
All you need to do is refresh the page after getting that email.\
If you gave the wrong Tradingview username and/or do not see it, please reach out to our Admin team VIA Discord, Email, or Live Chat.
Please Note: Access usually takes 30 minutes to 1 hour for most cases. In some cases during high volume or peak hours, it can take up to 8 hours to receive access.
---
# 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.sharkalgo.com/sharkalgo-course/how-to-get-access.md?ask=&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.