> For the complete documentation index, see [llms.txt](https://docs.ocutrap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ocutrap.com/getting-started/app/adding-a-trap-to-your-account.md).

# Adding a trap to your account

You need to be logged into [base.ocutrap.com](https://base.ocutrap.com) and have the POD with you to register a trap.

## Trap ID and serial number

The **serial number** is printed on a label inside the POD. After you register the trap, the app shows it as your **Trap ID**. Support may ask for either — they refer to the same device.

## Register a new trap

1. Locate the POD for the OcuTrap you wish to register.
2. Open the POD and find the **serial number** on the label inside.
3. Log in at [base.ocutrap.com](https://base.ocutrap.com/signuplogin).
4. Go to **Account** and tap **Add Trap** at the bottom of the page.
5. Enter the serial number when prompted.
6. When registration completes, the trap appears on your dashboard.

<figure><img src="/files/riGB5aGKNEwlLLgKtIGW" alt="" width="188"><figcaption></figcaption></figure>

<figure><img src="/files/rDu78KOTuthm0A2asQyD" alt="" width="188"><figcaption></figcaption></figure>


---

# 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.ocutrap.com/getting-started/app/adding-a-trap-to-your-account.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.