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

# Welcome to Isekai

## Welcome to Isekai

Isekai is a yield weaponization and design optimization platform that builds on existing DeFi infrastructure.

It uses a parallel architecture of Symbolic Tokens reinforced by a Base that introduces novel ways to interact with its underlying protocols, yield, and other users of the Isekai protocol.

### Yield Weaponization <a href="#yield-weaponization" id="yield-weaponization"></a>

[XP's](/tokenomics/xp.md) capture methodology allows yield-bearing tokens from *any* chain to be captured and passed back to XP-ETH in the form of **concentrated yield**. This creates a novel new yield primitive native to Arbitrum that sources yield in a protocol and chain-agnostic manner.

Yield weaponization and XP are used as the 'capital engine' to feed the entire Isekai ecosystem.

### Design Optimization <a href="#design-optimization" id="design-optimization"></a>

{% hint style="info" %}
Coming soon.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.isekai.money/welcome-to-isekai.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.