> For the complete documentation index, see [llms.txt](https://docs.urbit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.urbit.org/user-manual/id.md).

# Urbit ID

This section covers managing your Urbit ID with Bridge, and some other practical information about using Urbit ID.

This section covers managing your Urbit ID with Bridge, and some other practical information about using Urbit ID.

* [Using Bridge](/user-manual/id/using-bridge.md) - How to use Bridge, our web app for managing your Urbit ID.
* [Proxies](/user-manual/id/proxies.md) - How to use proxy addresses, which allow you to use your Urbit ID without having to use its master key.
* [HD Wallet (Master Ticket)](/user-manual/id/hd-wallet.md) - Your Urbit ID is a hierarchical deterministic crypto wallet (or "HD wallet"). This explains what that is and how it works.
* [Bridge Troubleshooting](/user-manual/id/bridge-troubleshooting.md) - Help for common issues with Bridge.
* [Creating an Invite Pool](/user-manual/id/creating-an-invite-pool.md) - Guide for star owners on inviting people to the network with their planets.
* [Guide to Factory Resets](/user-manual/id/guide-to-resets.md) - Step-by-step guide for resetting your Urbit ID in the event that your Urbit server suffers an unrecoverable error.
* [Layer 2 for planets](/user-manual/id/layer-2-for-planets.md) - How to use the [Layer 2](/urbit-id/l2.md) solution with your planet.
* [Layer 2 for stars](/user-manual/id/l2-star.md) - How to use the Layer 2 solution for your star.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.urbit.org/user-manual/id.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 `automate deployments from our CI pipeline` 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.