> 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/readme.md).

# What is Urbit?

Urbit docs site. Urbit ID, Urbit OS, Hoon, Nock, and self-hosting.

Urbit is a simple personal server (Urbit OS), a peer-to-peer network of those servers, and a decentralized identity standard (Urbit ID) for that network and beyond.

You can [get on Urbit](/get-on-urbit.md) in a few clicks with cloud hosting or host your server on your own machine at home.

## What is this site?

The Urbit docs are for developers and self-hosted users. Developers can find [courses](/build-on-urbit/environment.md), guides, and reference material for [Urbit ID](/urbit-id/what-is-urbit-id.md) and [Urbit OS](/urbit-os/what-is-urbit-os.md). The [manual](/user-manual/contents.md) section covers everything that users need to run their own server.

## Developer documentation

* [Build on Urbit](/build-on-urbit/environment.md) - Courses and tutorials for building on Urbit.
* [Urbit ID](/urbit-id/what-is-urbit-id.md) - Everything there is to know about Urbit ID, from high-level concepts to smart contract documentation.
* [Urbit OS](/urbit-os/what-is-urbit-os.md) - Documentation for Urbit OS, including step-by-step guides and kernel module APIs.
* [Hoon](/hoon/why-hoon.md) - Guides and reference material for Urbit's high-level programming language.
* [Nock](/nock/what-is-nock.md) - Guides and reference material for Urbit's low-level assembly language.

## User documentation

* [Manual](/user-manual/contents.md) - How to run your own Urbit, manage your Urbit ID, and more.


---

# 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://docs.urbit.org/readme.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.