# TL;DR

### What is XIO?

XIO is an **agentic neobroker**&#x20;

* "Hyperliquid wrapper today"
* "Agent control panel for perps, yield, and spend tomorrow"

***

### Why XIO?

Because markets run 24/7 and your attention doesn’t, XIO turns trading into a supervised system you can step away from.

***

### Who this is for?

XIO is built for **high intent on-chain users**.

***

### Why now?

The rails are ready.\
The control panel is not.\
\
The execution stack is mature. Agents can monitor markets, route orders, and manage risk. What’s missing is a single place to supervise them.

***

### What success looks like&#x20;

#### (0–3 months)

XIO ships as a non-custodial Hyperliquid-first terminal. Manual but sharp. Traders get a clean wrapper with pro tools for routing, PnL and portfolio tracking.

#### (3–6 months)

XIO becomes a default non-custodial front end for a meaningful slice of Hyperliquid perps flow, ranking alongside top builder-code fronts.&#x20;

#### (6mo –1 year)

XIO expands beyond Hyperliquid into a multi-venue agent network across perps, spot, yield and prediction markets, available through web app, mobile and third-party integrations.

#### (1–3 years)

XIO becomes an operating system for a slice of global perps and stablecoin users.

The majority of trading and risk management on XIO is handled by agents and automations, not by manual clicking.

Traders use XIO as the control panel to configure, supervise and pause their agents.


---

# Agent Instructions: 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:

```
GET https://xio-docs.gitbook.io/xio-docs/info/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
