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

# Example Apps

### Single query

Refers to one-to-one queries. For example, ENS on Ethereum can be used to authenticate other Layer2s or issue new NFTs or Fungible Tokens in a more secure way.

### Multiple queries

Refers to one-to-many queries. For example, there is a cross-chain yield aggregator that queries the APY of each lending protocol for each chain, compares them, and rebalances them to the most optimal lending protocol.

**Omni-chain lending**: Deposit, withdraw, lend and borrow across any chains.

{% embed url="<https://mirror.xyz/0xd10ee2A60B617531e4084a392cC87313ef9597EF/jEStiyfotp11c0UxIXx0CzoWs2Em7iSBZPI_qwNJNC8>" %}

**Cross chain governance:** cross-chain voting system that allows voting from multiple chains and aggregating the voting data.

{% embed url="<https://futaba-dev.notion.site/Cross-chain-Governance-Proposal-2115f44a818a4fea986b2441ad8f8583?pvs=74>" %}


---

# 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://futaba.gitbook.io/docs/guide/example-apps.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.
