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

# Getting Started

This guide explains how to use AI inside extensions.

There are two ways to leverage the power of AI inside your extensions.

{% hint style="info" %}
To use AI APIs or AI Extensions, you need to subscribe to \[Raycast Pro]\(<https://raycast.com/pro>).
{% endhint %}

## AI APIs

Use our [AI APIs](/api-reference/ai.md) to generate content such as summaries, translations, and more. For example, the [Notion extension](https://raycast.com/notion/notion) uses `AI.ask(...)` as part of its Quick Capture command to generate a summary of a website.

## AI Extensions

Create an [AI Extension](/ai/create-an-ai-extension.md) to enable natural language interactions in Quick AI, AI Chat, and AI Commands. For example, the [Linear extension](https://www.raycast.com/linear/linear) allows you to manage your team's issues or check your personal priorities by simply chatting to it.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://developers.raycast.com/ai/getting-started.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 `build a script that syncs our docs to a CMS` 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.