> For the complete documentation index, see [llms.txt](https://docs.humanity.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humanity.org/working-with-llms/cursor-integration-guide.md).

# Cursor Integration Guide

Integrate Humanity docs with Cursor IDE using native documentation indexing. Enable AI autocomplete and chat with full context of our API reference.

{% embed url="<https://cursor.com/>" %}

## 1. Add Humanity docs to Cursor

1. Open **Cursor → Settings**
2. Go to **Features → Docs**
3. Click **Add new doc**
4. Enter the GitBook URL:

   ```
   https://docs.humanity.org
   ```
5. Name it something like **Humanity Docs**
6. Wait until Cursor finishes indexing (status shows *Ready*)

***

## 2. Reference the docs in Cursor prompts

Once indexed, explicitly reference the docs in Cursor chat:

```
@Humanity Docs
Build an off-chain integration using the Humanity SDK.
Follow the Off-Chain → Quick Start guide.
```

Being explicit about **which section** to follow improves accuracy.

***

## 3. Scope Cursor’s output

When prompting Cursor, include:

* Which surface to use (**Off-Chain**)
* Whether to use **SDK or raw API**
* The desired outcome (e.g. OAuth login + preset verification)

Example:

```
@Humanity Docs
Implement the Off-Chain Quick Start using the Humanity SDK.
Use OAuth with PKCE and verify the is_human preset.
```

***


---

# 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.humanity.org/working-with-llms/cursor-integration-guide.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.