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

# Authorizing in Lab Terminal

{% stepper %}
{% step %}
In the opened window, click "**Log in via Telegram.**"

You can also choose to log in via Google, but this will create a new account in Lab Terminal.\
Click "**Get code**" — the Telegram app will open, and in the Lab Terminal bot, you will receive a one-time confirmation code.
{% endstep %}

{% step %}
Copy the code and paste it into the corresponding field in the extension.
{% endstep %}

{% step %}
Click "Verify" to complete the authorization.

After a successful login, you will be redirected to your Lab Terminal account
{% endstep %}
{% endstepper %}

Congratulations! The <mark style="color:green;">**Lab Terminal**</mark> extension is successfully installed and ready to use.

Now, when you visit token pages on services like Dexscreener, Dextools, Axiom, GMGN, Photon, or Bullx, the corresponding token trading section in Lab Terminal will automatically open.

<br>


---

# 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://docs.lab.pro/authorizing-in-lab-terminal.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.