> 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/l2-star.md).
# Layer 2 for stars
How star owners can use Azimuth's Layer 2 rollup.
This is a brief summary of the three possible options for star owners with respect to use of [layer 2](/urbit-id/l2.md).
## One-way trip
Stars have three options with respect to layer 2:
* Layer 1
* Layer 1 with Layer 2 spawn proxy
* Layer 2
A layer 1 star can move to layer 1 with layer 2 spawn proxy, or to layer 2. A star on layer 1 with layer 2 spawn proxy can move to layer 2. None of these actions are currently reversible.
Moving between layers has no effect on sponsorship status of any of its sponsees, nor its sponsorship status with its galaxy. It also has no effect on planets spawned by the star prior to moving between layers.
## Layer 1
A star on layer 1 performs all Urbit ID-related actions on layer 1, except for sponsorship actions, which can be performed on either layer.
## Layer 1 with Layer 2 spawn proxy
A star on layer 1 with layer 2 spawn proxy can spawn planets on layer 2 using either their ownership proxy or spawn proxy. They will no longer be able to spawn planets on layer 1. They may also perform sponsorship actions on either layer, identical to layer 1 stars.
## Layer 2
A star on layer 2 must perform all Urbit ID related actions on layer 2. All planets spawned by the star will be on layer 2.
---
# 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/l2-star.md?ask=&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.