> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xentfi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# XentFi Pro Overview

> Programmatic liquidity and trading on XentFi's hybrid off-chain matching / on-chain settlement order book.

**XentFi Pro** is XentFi's programmatic liquidity and trading platform — an order book with off-chain matching for exchange-grade speed and on-chain settlement for real, self-custodied funds. It sits on top of your existing XentFi wallets; no separate custody model, no new private keys to manage.

## Base URL

XentFi Pro is served from its own base URL, distinct from the core XentFi API:

<CodeGroup>
  ```bash theme={null}
  https://api.pro.xentfi.com
  ```
</CodeGroup>

<Warning>
  This is different from the core platform's `https://api.xentfi.com`. Wallets, assets, and blockchains are shared across both — an order's `walletId` is the same XentFi wallet ID you'd see in the core [Wallet Management](/essentials/master-wallets) API — but order book requests must go to the `api.pro.xentfi.com` host.
</Warning>

## Prerequisites

<Card title="You need a Pro account and an API key with the Trade scope" icon="key">
  XentFi Pro is not self-serve today. [Contact **support@xentfi.com**](mailto:support@xentfi.com) to request access, or complete the [Pro access request form](https://xentfi.com/pro/access) — support responds within **2 hours**. See [Authentication](/xentfi-pro/authentication) for how the Trade scope and API key work once you're set up.
</Card>

## How it works

```mermaid theme={null}
flowchart TB
    subgraph Client["Your application"]
        API[XentFi Pro API calls]
    end

    subgraph Pro["XentFi Pro"]
        Risk[Risk engine<br/>rate limits, price bands, balance reservation]
        Engine[Matching engine<br/>batch auctions, price-time priority]
        Settle[Settlement service<br/>hub-and-spoke via Master Wallet]
    end

    subgraph Chain["Blockchain"]
        Master[Settlement Master Wallet]
    end

    API --> Risk --> Engine --> Settle --> Master
    Engine -.realtime fills.-> API
```

1. **Place an order** — `POST /v1/orderbook/orders` runs risk checks and an atomic balance reservation, then admits the order to the book. This never touches the blockchain, so there's no signature or quote latency on the request path.
2. **Matching** — every `batchAuctionIntervalMs` (default 250ms), the market's batch window drains and resting orders are matched price-time priority.
3. **Settlement** — matched trades are netted per wallet/asset every 2 seconds and settled on-chain through the market's settlement master wallet — see [Liquidity & Settlement](/essentials/liquidity).

## What you can build

<CardGroup cols={2}>
  <Card title="📈 Market making" icon="chart-line">
    Post and manage resting `LIMIT`/`POST_ONLY` orders programmatically, with realtime fill updates over websocket.
  </Card>

  <Card title="⚡ Algorithmic execution" icon="bolt">
    `MARKET`, `IOC`, and `FOK` orders for latency-sensitive execution, protected against thin/stale books by a reference price oracle.
  </Card>

  <Card title="📊 Market data" icon="chart-bar">
    Order book depth, recent trades, 24h ticker, and OHLCV candles for every market.
  </Card>

  <Card title="🔍 Settlement visibility" icon="magnifying-glass">
    Per-wallet settlement leg status (`txHash`, confirmations, failures) for every batch your trades settle in.
  </Card>
</CardGroup>

## Explore the tab

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/xentfi-pro/quickstart">
    List markets, check the book, and place your first order.
  </Card>

  <Card title="Authentication" icon="key" href="/xentfi-pro/authentication">
    Get an API key with the Trade scope.
  </Card>

  <Card title="Order Book concepts" icon="list-ordered" href="/essentials/orderbook">
    Markets, order types, fees, and the order lifecycle.
  </Card>

  <Card title="Liquidity & Settlement concepts" icon="waves" href="/essentials/liquidity">
    How trades settle on-chain and how to keep a market funded.
  </Card>
</CardGroup>

Full endpoint-by-endpoint request/response schemas are below in this tab's **API Reference** section.