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

# Overview

We make any transaction gasless and bridgeless, restore fungibility and fluidity of stablecoins, connect onchain accounts with the offchain world in minutes

Orby, is an Orchestration and Abstraction Layer that abstracts complexity and unifies execution across chains, accounts, stablecoins, and platforms. It focuses on three types of orchestration:

1. [Onchain Transaction Orchestration](/getting-started/onchain-transaction-orchestration.md): enable your users to transact gaslessly and bridgelessly with unified balances. 
2. [Stablecoin Abstraction and Orchestration](/getting-started/stablecoin-abstraction-and-orchestration.md): instantly network all stablecoins, restore fungibility and capture yield generated by stablecoins held by your users.
3. [Onchain-Offchain Capital Orchestration](/getting-started/onchain-offchain-capital-orchestration.md): enable your users to use CEX or bank balances directly onchain.

These can be use by any wallets, exchanges, platforms, and agents to offer one-click transactions, gas abstraction, chain abstraction, stablecoin abstraction, and the use of off-chain balances.  Furthermore, Orby enables all this functionality on dapps.  


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs-orby.orblabs.xyz/getting-started/overview.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 `build a script that syncs our docs to a CMS` 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.