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

# Getting Started

{% hint style="info" %}
New to Lucky Orange? This documentation covers how to implement Lucky Orange from a technical point-of-view. If you'd like to learn more about the features offered by Lucky Orange, take a look at our [Help Center](https://help-preview.luckyorange.com).
{% endhint %}

## Choose your environment

{% content-ref url="/pages/-MWBAjrefRQ36-Nh9KiH" %}
[Browser](/libraries/browser.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MWBAw6Y6Oho3Ow5a-d8" %}
[Node.js](/libraries/node.md)
{% endcontent-ref %}

## Looking for Lucky Orange Classic?

The developer documentation found here is for the new Lucky Orange. The developer API has been completely overhauled to be more consistent, powerful, and easier to use. If you are using Lucky Orange Classic, please see the [existing help documentation](https://help.luckyorange.com/).

Even though the API has completely changed, in order to help with the transition, the new browser library offers various backwards compatible functionality. Use the link below to learn more about how to migrate.

{% content-ref url="/pages/-MWPH2MK6JmJ3AOF2pYi" %}
[Moving From Classic](/moving-from-classic.md)
{% endcontent-ref %}


---

# 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:

```
GET https://developers.luckyorange.com/master.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.