> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/developers/tools.md).

# Developer Tools

Official wallets, explorers, code repositories, and samples for building on XYO Layer One.

Use this page as a directory. Each tutorial names the exact tools and versions it requires.

## Wallets

* [XL1 browser wallet](/developers/xl1-wallet.md) — manage an XL1 account and approve browser-based activity.

## Explore and verify

* [XYO Block Explorer](/developers/xyo-block-explorer.md) — inspect Sequence blocks, transactions, payloads, and signatures.
* [XYO GitHub organization](https://github.com/XYOracleNetwork) — source code, samples, issues, and release history.

## Samples

* [Local XL1 guides](/developers/how-to-request-xl1-testnet-tokens-1.md) — run a local chain with React or Node.js.
* [XYO AI SDK quickstart](/ai-sdk/xyo-ai-sdk-quick-start.md) — build an XL1 sample with the XYO skill stack.

{% hint style="info" %}
Versions differ between samples. Check [Prepare Your Tools](/developers/getting-started/tooling.md) before installing dependencies.
{% endhint %}


---

# 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.xyo.network/developers/tools.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.