# Platform Overview

Bound is organized into three core layers, each building on the one below.

<figure><img src="/files/RKkAgv5Tm9NwnIObszG5" alt=""><figcaption></figcaption></figure>

<br>

## Layer 1 - Infrastructure

* **Bound Auth** - Passkey-based authentication that creates self-custodial wallets across BTC, EVM, and Solana. All user-facing products require Bound Auth.
* **Bound APIs** - B2B API access layer for trading infrastructure and derivatives marketplace.

## Layer 2 - Trading Engine

* **Runes AMM** - Native Bitcoin token swaps and liquidity provisioning on Bitcoin mainnet.
* **SODAX Crosschain** -Native cross-chain swaps across BTC, ETH, SOL, USDC, and more - no wrapping, no bridging.

## Layer 3 - Products

* **Launchpad** - Token creation and launch via Virtual Mint. Uses Runes AMM for post-launch liquidity.
* **Lend / Borrow** -Liquidation-free loans and overcollateralized loans against BTC.
* **Derivatives (Options)** - Covered calls and put options for BTC yield and downside protection.

## bUSD - Settlement layer

bUSD is Bound's native Runes-based stablecoin on Bitcoin, backed 1:1 by other stablecoins. It acts as the settlement layer for all Bound structured products - every loan, option, and escrow settles in bUSD.


---

# 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://bound-1.gitbook.io/bound-docs/readme/platform-overview.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.