# Welcome

### Understanding orda <a href="#understanding-orda" id="understanding-orda"></a>

Developers use orda to submit an intent (e.g., “swap 1,000 USDC → BRZ”) and the network finds the best execution through competing solvers.

The orda network is the coordination layer that makes global value movement efficient:

* **Intents:** Developers define *what* they want.
* **Solvers:** Competing participants fulfill those intents at the best price.

### Why orda exists

Moving value today is fragmented. The same value can cost anywhere between **0–300 bps** to transfer, depending on who you are and how you connect:

| Market Segment     | Typical Fees | Access Mechanism           | Settlement Time |
| ------------------ | ------------ | -------------------------- | --------------- |
| Tier 1 Interbank   | 0–8 bps      | Bilateral                  | T+0             |
| Institutional      | 12–18 bps    | Prime Broker               | T+0 – T+1       |
| Corporate Treasury | 16–50 bps    | Bank Desk Markup           | T+0 – T+2       |
| Processors         | 25–70 bps    | Aggregator RFQ             | T+1 – T+3       |
| Retail / SME       | 100–300+ bps | Card Networks & Bank Rails | Instant – T+3   |

Different participants pay radically different spreads for the *same movement of value*, because of float fragmentation and layers of intermediaries.

### How orda changes it

orda collapses this complexity by acting as a **coordination layer**:

* **Unified access:** One integration to reach banks, blockchains, and stablecoin systems.
* **Solver competition:** Multiple counterparties compete to fulfill each intent, compressing spreads toward interbank levels.
* **Vaults:** Shared liquidity replaces pre-funding, making float productive and settlement faster.

Instead of multiple pricing tiers, developers get **a single fair price,** all from **a single interface**.

{% hint style="info" %}
Whether you’re building an exchange, wallet or payments app, orda abstracts the mess of FX and liquidity into a single priced, programmable layer.
{% endhint %}

### Use Cases

{% tabs %}
{% tab title="🌍 Cross-Border / FX" %}
Move value between fiat and stablecoin corridors at competitive spreads.

**Example scenarios:**

* Remittance platforms sending USD → BRL in real-time
* Treasury desks converting USDC → BRL for local operations
* Marketplaces settling payouts to sellers across borders

**How to build it:**

* Use the **API or SDK** to integrate quickly
* **Generate wallets** for settlement flows
* **Create recipients** with bank or crypto details
* **Begin quoting** FX intents and fulfill at best price
  {% endtab %}

{% tab title="💳 Ramps" %}
Embed on/off-ramping into your app with a few lines of code.

**Example scenarios:**

* Wallets adding local bank deposits/withdrawals
* Exchanges offering direct top-ups
* Fintech apps letting users buy stablecoins instantly

**How to build it:**

* Create a Recipient with bank or crypto settlement details
* Request a quote and pass it to the end user to execute
* Use the widget for plug & use
  {% endtab %}

{% tab title="🔄 Swaps & Bridges" %}
Unify fragmented liquidity across blockchains and stablecoins.

**Example scenarios:**

* Swap USDC on Ethereum → BRZ on Base
* Bridge AUSD from Plasma → Solana
* Build network & currency abstracted apps with intent-based routing

**How to build it:**

* Use the **API** or **SDK** for cross-chain swaps
* Or embed the Widget for a drop-in swap UI
* Let solvers compete for best execution across chains
  {% endtab %}

{% tab title="⚙️ Advanced" %}
Push beyond basic flows with primitives that unlock infrastructure-level use cases.

**Example scenarios:**

* **On-chain liquidity management:** Borrow from vaults, rebalance float and monitor utilization without fragmented pre-funding
* **Chain-abstracted infrastructure:** Submit one intent and let solvers handle routing across chains and assets
* **Unified balances:** Power wallets with a single spendable balance (fiat + stablecoins + chains), bridging abstraction but extended to banks.
* **Solver strategies:** Run custom solver bots to capture spreads, arbitrage across corridors, or internalize margins as a PSP
  {% endtab %}
  {% endtabs %}

### Get started

* [**Quickstart**](https://docs.orda.network/developers/quickstart)**:** Make your first request in 5 minutes
* [**Developer Portal**](https://app.orda.network/)**:** Authentication Access
* [**SDKs**](https://docs.orda.network/developers/sdks)**:** Use orda in TypeScript & React (more coming soon)
* [**API Reference**](https://docs.orda.network/developers/api)**:** Full endpoint documentation


---

# 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://docs.orda.network/readme.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.