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

# Glossary

> Comprehensive glossary of trading terms, cryptocurrency concepts, and WhiteBIT platform terminology.

## A

<AccordionGroup>
  <Accordion title="Active orders">
    [Orders](#orders) running for the duration of the trading day.
  </Accordion>

  <Accordion title="ADL Grade">
    An indicator value from 0 to 4 reflecting a position's place in the per-market [Auto-Deleveraging](#auto-deleveraging-adl) ranking. Higher Grade signals higher likelihood of selection as an ADL counterparty. Grade 4 corresponds to the asymptotic top 5% of the ranked list. See [ADL Grade](/concepts/auto-deleveraging#adl-grade).
  </Accordion>

  <Accordion title="AML">
    Anti-Money Laundering. Controls and checks to detect and prevent money laundering. WhiteBIT runs AML checks on deposit and withdrawal flows.
  </Accordion>

  <Accordion title="Ask">
    Sell [order](#orders).
  </Accordion>

  <Accordion title="Assets">
    A digital representation of value transferable, storable, or tradable electronically.
  </Accordion>

  <Accordion title="Attribution">
    In Model B (customers' own accounts), the mechanism that links an end user's WhiteBIT account and activity to the partner that onboarded the user, so fee-share and reporting apply without the partner holding the account. See [Integration models](/concepts/integration-models).
  </Accordion>

  <Accordion title="Auto-Deleveraging (ADL)">
    Final-stage liquidation mechanism on the futures market. Activates only when standard market liquidity cannot fully cover a liquidated position. Closes profitable counterparty positions on the opposite side at a calculated price, ensuring no user balance becomes negative. See [Auto-Deleveraging](/concepts/auto-deleveraging).
  </Accordion>
</AccordionGroup>

## B

<AccordionGroup>
  <Accordion title="B2B partner account">
    An account designation for business-to-business (B2B) institutional partner services. Certain endpoint groups require a B2B partner account — for example fixed [lending](/products/lending/overview) plans and the [Travel Rule](#travel-rule) API — and canceled orders are not recorded in order history. Request access through the [institutional services form](https://whitebit.com/institutional-services/b2b).
  </Accordion>

  <Accordion title="Balance Collateral">
    Balance for [margin](#margin-trading) and [futures trading](#futures-trading)
  </Accordion>

  <Accordion title="Balance Main">
    A balance accepting deposits and withdrawals of cryptocurrency and national currency.
  </Accordion>

  <Accordion title="Balance Spot (Balance Trade)">
    Balance for [spot trading](#spot-trading). This balance supports non-marginal trading ([order](#orders) placement) and currency exchange.
  </Accordion>

  <Accordion title="Best-bid-offer (BBO)">
    Best-bid-offer (BBO) determines [limit order](#limit-order) prices based on market conditions. In the counterparty method, for buy orders the system uses the lowest ask price in the [order book](#order-book); for sell orders, the highest bid price. The queue method uses the highest current buy price (Bid) for buy orders and the highest ask price for sell orders.
  </Accordion>

  <Accordion title="Bid">
    Buy [order](#orders).
  </Accordion>
</AccordionGroup>

## C

<AccordionGroup>
  <Accordion title="Card token">
    A unique identifier for a card, used to facilitate payments and manage subscriptions without exposing the actual card information.
  </Accordion>

  <Accordion title="Codes">
    See [WhiteBIT Codes](#whitebit-codes)
  </Accordion>

  <Accordion title="Collateral">
    The cryptocurrency [asset](#assets) pledged by the borrower as a guarantee of loan repayment.
  </Accordion>

  <Accordion title="Colocation">
    The practice of placing trading servers in close physical proximity to an exchange's [matching engine](#matching-engine) to minimize [latency](#latency). Colocation is crucial for [high-frequency trading (HFT)](#high-frequency-trading-hft) operations.
  </Accordion>

  <Accordion title="Conditional orders">
    "Conditional orders" is a collective term for [orders](#orders) with conditions. Currently, these include [OTO](#one-triggers-the-other-oto) (One Triggers the Other) and [OCO](#oco-orders) (One Cancels the Other) orders.
  </Accordion>

  <Accordion title="Crypto Lending">
    Crypto Lending enables earning passive income by lending funds to the exchange in a chosen cryptocurrency for a set period.
  </Accordion>
</AccordionGroup>

## D

<AccordionGroup>
  <Accordion title="Deal (Trade)">
    A transaction where two parties buy or sell an [asset](#assets) at an agreed-upon price. The trade record includes the price, amount, date, and any [fees](#fee).
  </Accordion>

  <Accordion title="Demo tokens (DBTC/DUSDT)">
    Test assets for risk-free Spot trading on the live platform. WhiteBIT has no public testnet — activate free demo tokens (0.5 DBTC + 1,000 DUSDT) from the [WhiteBIT Codes page](https://whitebit.com/codes) with no KYC required, and trade the `DBTC_DUSDT` pair through the standard API endpoints. Demo tokens support Spot trading only.
  </Accordion>

  <Accordion title="Derivative">
    Crypto derivatives are contracts deriving value from a primary underlying [asset](#assets). The primary asset is a cryptocurrency such as Bitcoin.
  </Accordion>

  <Accordion title="Depth">
    See [Order book](#order-book).
  </Accordion>
</AccordionGroup>

## E

<AccordionGroup>
  <Accordion title="Effective leverage">
    A position-level metric used in the [Auto-Deleveraging](#auto-deleveraging-adl) Rating formula. Defined as `|position size in money| / account equity`. Distinct from configured account [leverage](#leverage) — effective leverage scales with position size relative to the account's [collateral balance](#balance-collateral), not with the leverage setting alone. See [Rating formula](/concepts/auto-deleveraging#rating-formula).
  </Accordion>

  <Accordion title="European Economic Area (EEA)">
    The EEA is an international agreement enabling the extension of the European Union's single market to non-EU member states. The EEA consists of the EU member states and three EFTA states (Iceland, Liechtenstein, and Norway).
  </Accordion>

  <Accordion title="Express Withdraw">
    A gated B2B payment feature that charges a specific amount from a WhiteBIT user's [Main balance](#balance-main) to the partner's Main balance through a signed, single-use payment token valid for 90 seconds. The transfer settles instantly, off-chain, and without a [fee](#fee). See the [Payment Integration guide](/guides/payment-integration#express-withdraw-payments).
  </Accordion>
</AccordionGroup>

## F

<AccordionGroup>
  <Accordion title="Fast API Key">
    An OAuth-issued WhiteBIT API key that a partner platform obtains on behalf of an end user through the OAuth API key consent flow, replacing manual key creation and copy-paste. The API secret is retrievable by the partner exactly once through a Bearer-authenticated endpoint. Any IP restriction on the key is the end user's own account-level control, not a partner-managed allowlist. See the [Fast API Key integration guide](/guides/fast-api-key-integration).
  </Accordion>

  <Accordion title="Fee">
    The platform charges a fee for crypto transactions.
  </Accordion>

  <Accordion title="Fiat">
    A currency (a medium of exchange) established by government regulation as [money](#money) but without intrinsic value (value independent of the nominal value, such as a precious metal might have).
  </Accordion>

  <Accordion title="Finished orders">
    A list of all completed (executed) [orders](#orders) including order ID, date, amount, price, conditions, and other relevant data.
  </Accordion>

  <Accordion title="Futures">
    See [Perpetual futures](#perpetual-futures)
  </Accordion>

  <Accordion title="Futures trading">
    Futures trading supports opening Long and Short positions and using [leverage](#leverage). Traders pay a [fee](#fee) for using borrowed funds to each other, not to the exchange.
  </Accordion>
</AccordionGroup>

## G

<AccordionGroup>
  <Accordion title="Grid trading">
    An automated strategy that places [limit orders](#limit-order) at fixed price intervals around a center price. When a buy order fills, the strategy places a sell order one grid level above; when a sell order fills, the strategy places a buy order one level below. Profit comes from price oscillation within the grid range. See the [Trading Bot guide](/guides/building-a-trading-bot) for the strategy walkthrough.
  </Accordion>
</AccordionGroup>

## H

<AccordionGroup>
  <Accordion title="Hedge mode">
    An account-level setting for collateral trading accounts that allows simultaneous long and short [positions](#position-side) on the same market; when disabled, the account operates in one-way mode. Toggling requires zero open positions. See [Collateral account hedge mode](/api-reference/trading/collateral-account-hedge-mode) and [Update collateral account hedge mode](/api-reference/trading/update-collateral-account-hedge-mode).
  </Accordion>

  <Accordion title="High-frequency trading (HFT)">
    An automated trading strategy involving executing a large number of [orders](#orders) at extremely high speeds, typically utilizing [colocation](#colocation) services to minimize [latency](#latency).
  </Accordion>

  <Accordion title="HMAC-SHA512">
    A keyed hash algorithm that signs private REST API requests: the client computes `hex(HMAC_SHA512(payload, key=api_secret))` and sends the result in the `X-TXC-SIGNATURE` header. See [Authentication](/api-reference/authentication) for the full signing scheme.
  </Accordion>
</AccordionGroup>

## I

<AccordionGroup>
  <Accordion title="IP whitelisting">
    Restricting an API key to accept requests only from pre-approved IP addresses, with up to 50 addresses per key. Configure the whitelist at the API settings page. See [Security Best Practices](/best-practices/security) for key-management guidance.
  </Accordion>
</AccordionGroup>

## J

## K

<AccordionGroup>
  <Accordion title="Kill-switch timer">
    A function to cancel all [orders](#orders) on a specific market automatically when the timer expires. Each timer covers a single market and can be restricted to spot, margin, or futures order types.
  </Accordion>

  <Accordion title="KYB">
    Know Your Business. Verification of a business entity's identity and ownership, the corporate counterpart of [KYC](#kyc). Part of [Institutional Onboarding](/institutional/onboarding).
  </Accordion>

  <Accordion title="KYC">
    Know Your Customer. Identity verification of an individual customer before trading or withdrawing.
  </Accordion>
</AccordionGroup>

## L

<AccordionGroup>
  <Accordion title="Latency">
    The time delay between sending a trading order and order execution. In [high-frequency trading](#high-frequency-trading-hft), traders measure latency in milliseconds or microseconds.
  </Accordion>

  <Accordion title="Lending plans">
    See [Crypto Lending](#crypto-lending)
  </Accordion>

  <Accordion title="Leverage">
    The ratio of [margin](#margin-trading) to borrowed funds shows how many times credit exceeds available [assets](#assets).
  </Accordion>

  <Accordion title="Limit order">
    A limit order specifies a fixed price for buying or selling an [asset](#assets).
  </Accordion>
</AccordionGroup>

## M

<AccordionGroup>
  <Accordion title="Maker">
    A maker is a trader who places [limit orders](#limit-order) on the [order book](#order-book), setting the price and quantity of the [trade](#deal-trade), and waits for another trader to accept the [order](#orders).
  </Accordion>

  <Accordion title="Margin trading">
    The use of exchange's funds to trade [assets](#assets) enables placing [orders](#orders) for sums exceeding the initial deposit several times. The initial deposit is called "margin," and the margin size depends on the [leverage](#leverage).
  </Accordion>

  <Accordion title="Market">
    [Assets](#assets) tradable for each other on an exchange.
  </Accordion>

  <Accordion title="Market activity">
    [Market](#market) information (last price, [volume](#volumetrade-volume), high, low, change) for the last 24 hours.
  </Accordion>

  <Accordion title="Market order">
    A market order specifies an [asset](#assets) for immediate purchase or sale at the best available price.
  </Accordion>

  <Accordion title="Market pair">
    See [Market](#market)
  </Accordion>

  <Accordion title="Matching engine">
    The core system of an exchange pairing buy and sell [orders](#orders). In [colocation](#colocation) setups, exchanges position trading servers close to the matching engine to minimize execution time.
  </Accordion>

  <Accordion title="Memo (destination tag)">
    A special identifier some cryptocurrency networks require for transactions. Depositing and withdrawing some cryptocurrencies, such as Ripple (XRP) and Stellar (XLM), requires specifying a memo.
  </Accordion>

  <Accordion title="MiCA">
    Markets in Crypto-Assets. The European Union's regulatory framework for crypto-asset service providers. See [Regulatory Compliance](/institutional/compliance).
  </Accordion>

  <Accordion title="Model A">
    The partner-operated sub-account model: the partner creates and manages one WhiteBIT sub-account per end user under a master account and holds the sub-account API key. Used by account operators and managed-trading platforms. See [Integration models](/concepts/integration-models).
  </Accordion>

  <Accordion title="Model B">
    The customers'-own-accounts model: each end user holds a standalone WhiteBIT account and the partner connects through a [Fast API Key](#fast-api-key); WhiteBIT runs the KYC, and activity is linked to the partner by [attribution](#attribution). See [Integration models](/concepts/integration-models).
  </Accordion>

  <Accordion title="Money">
    The currency used to buy and sell [assets](#assets) on a trading platform.
  </Accordion>

  <Accordion title="Multinetwork">
    Cryptocurrency like USDT exists on different networks (e.g. OMNI, Tron, Ethereum). Traders select the network when making a deposit or withdrawal.
  </Accordion>
</AccordionGroup>

## N

<AccordionGroup>
  <Accordion title="Nonce">
    An arbitrary number used only once in a request.
  </Accordion>
</AccordionGroup>

## O

<AccordionGroup>
  <Accordion title="OCO orders">
    An OCO order combines a [limit order](#limit-order) with a [stop-limit](#stop-limit-order); only one executes. When one order fills, the platform automatically cancels the other.
  </Accordion>

  <Accordion title="Omnibus account">
    A single pooled account holding multiple end users' funds together. WhiteBIT does not offer a pooled omnibus model for partner integrations — pooled custody conflicts with MiCA client-fund segregation and Travel Rule requirements, so each model keeps segregated sub-accounts. See [Integration models](/concepts/integration-models).
  </Accordion>

  <Accordion title="One Triggers the Other (OTO)">
    OTO is a trading feature where fulfilling a primary [order](#orders) automatically sets corresponding stop loss and take profit orders. OTO allows specifying prices for stop loss and take profit when creating the primary order.
  </Accordion>

  <Accordion title="Order book">
    A separated list of buy (bids) and sell (asks) [active orders](#active-orders) for a specific [market](#market).
  </Accordion>

  <Accordion title="Orders">
    Simple contracts specifying the crypto to buy or sell, the quantity, and the price. Orders consist of [trades (deals)](#deal-trade). The execution of all deals executes the order. There are different types of orders: [Market order](#market-order), [Limit order](#limit-order), [Stop market order](#stop-market-order), [Stop limit order](#stop-limit-order), [OCO order](#oco-orders). Orders have either [executed (finished)](#finished-orders) or [unexecuted (active)](#active-orders) status.
  </Accordion>

  <Accordion title="Orders pending">
    [Orders](#orders) requesting an exchange to buy or sell an [asset](#assets) at a set price and conditions.
  </Accordion>
</AccordionGroup>

## P

<AccordionGroup>
  <Accordion title="Pair">
    See [Market](#market)
  </Accordion>

  <Accordion title="Perpetual futures">
    A type of [derivative](#derivative) contract for trading cryptocurrencies with no expiration date and daily rollover.
  </Accordion>

  <Accordion title="PNL">
    Profit and loss on a position. `grossPnl` is the realized profit and loss before funding, with trading fees already deducted; `netPnl` is `grossPnl` minus total funding. See [Closed-position PNL](/api-reference/trading/closed-position-pnl).
  </Accordion>

  <Accordion title="Position side">
    Defines the position direction for a trade when hedge mode is enabled, and only for [perpetual futures](#perpetual-futures) trading [Market](#market).
    "LONG": Represents a long (buy) position.
    "SHORT": Represents a short (sell) position.
    "BOTH": Applies to both long and short positions, typically used in query contexts.
  </Accordion>

  <Accordion title="Precision">
    The number of digits to the right of the decimal point.
  </Accordion>

  <Accordion title="Price-time priority">
    The order-matching rule used by the [matching engine](#matching-engine): better-priced [orders](#orders) fill first, and orders resting at the same price fill in the sequence of arrival at the engine.
  </Accordion>

  <Accordion title="Provider">
    [Fiat](#fiat) currencies have different providers facilitating deposits and withdrawals by bank transfers.
  </Accordion>
</AccordionGroup>

## Q

## R

<AccordionGroup>
  <Accordion title="Refund">
    Refund returns funds for a canceled [deposit](#whitebit-deposit-to-main-balance). The refund address must support the same network and [asset](#assets) as the original deposit. The refund address cannot be a WhiteBIT address. Use the [Refund deposit endpoint](/api-reference/account-wallet/refund-deposit) to request a refund.
  </Accordion>

  <Accordion title="Retail Price Improvement (RPI)">
    Retail Price Improvement (RPI) defines a [limit order](#limit-order) mode improving execution for retail users and keeping the order out of public market data feeds. RPI is a two-sided feature: makers submit RPI orders with `rpi=true`, and takers eligible to match against those orders set [`retail=true`](#retail-flag).

    **Visibility**

    Public `depth` and `bookTicker` feeds exclude RPI orders in both WebSocket and REST responses. Private active order endpoints and private WebSocket streams return RPI orders. The exchange UI [order book](#order-book) (web and mobile) displays RPI orders.

    **IOC compatibility**

    RPI orders use post-only behavior by design. An RPI order does not support the IOC flag. The API returns error code `40` when a request sets both `rpi=true` and `ioc=true`.

    **Fees**

    RPI executions apply a specific [fee](#fee) or rebate model defined for the account. When a user trades through a [sub-account](#sub-account), the system applies the effective sub-account fee configuration. Use [`Query Market Fees`](/api-reference/trading/query-market-fee) to retrieve account-wide fees, or [`Query Market Fee For A Single Market`](/api-reference/trading/query-market-fee-single) to retrieve the effective fee for one market.
  </Accordion>

  <Accordion title="Retail flag">
    The `retail` request parameter on the [Create Limit Order](/api-reference/trading/create-limit-order) and [Bulk Limit Order](/api-reference/trading/bulk-limit-order) endpoints marks a [limit order](#limit-order) as a retail-source taker eligible to match against orders submitted by [Retail Price Improvement (RPI)](#retail-price-improvement-rpi) makers. The Retail flag is the taker-side counterpart to the `rpi` flag, which marks the maker side of the same feature.

    **Eligibility**

    The Retail flag must be enabled on the account before `retail=true` can be sent from a private-API source. Contact the account manager to enable the Retail flag.

    **Behavior**

    A retail taker is eligible to match against RPI-maker liquidity and may receive price improvement at execution. The flag has no effect when combined with `postOnly=true` — post-only orders are makers, never takers.

    **Combination with RPI**

    The Retail flag can be sent together with the `rpi` flag. An order with both `retail=true` and `rpi=true` is an RPI maker and matches exactly like an order with only `rpi=true`: the Retail flag has no effect on it, as on any post-only order. See [Order Parameter Rules](/guides/order-parameter-rules) for the complete list of unsupported parameter combinations.
  </Accordion>

  <Accordion title="Reduce-only">
    Reduce-only is an order parameter that guarantees an order only decreases or closes an existing position — never increases the position or opens a new one in the opposite direction.

    **Behavior**

    If the order amount exceeds the current position size, the system automatically reduces the order to match — the response returns the adjusted amount. This applies on placement and execution.

    **Rejection**

    The API returns error code `116` if no open position exists or the order direction matches the position direction. This is a synchronous rejection — the order is never created.

    **Auto-cancellation**

    If a position closes while a reduce-only [limit order](#limit-order) is still pending, the backend auto-cancels the order with status `AUTO_CANCELED_REDUCE_ONLY`. [Auto-Deleveraging](#auto-deleveraging-adl)-triggered closure also auto-cancels pending reduce-only orders with the same `AUTO_CANCELED_REDUCE_ONLY` status — no ADL-specific cancel status was introduced.

    **Availability**

    Available on collateral (margin and futures) markets only. See [Order Types — Reduce-only orders](/concepts/order-types#reduce-only-orders) for details and endpoint links.
  </Accordion>
</AccordionGroup>

## S

<AccordionGroup>
  <Accordion title="Self-trade prevention (STP)">
    STP is a mechanism preventing traders from executing trades against own [orders](#orders). STP helps avoid unintentional self-trading and ensures market integrity by automatically canceling or modifying orders resulting in a self-match.
  </Accordion>

  <Accordion title="Smart Plans">
    See [Crypto Lending](#crypto-lending)
  </Accordion>

  <Accordion title="SMART staking">
    See [Crypto Lending](#crypto-lending)
  </Accordion>

  <Accordion title="Spot trading">
    Buying and selling [assets](#assets) for immediate settlement.
  </Accordion>

  <Accordion title="Stock">
    An [asset](#assets) tradable on an exchange.
  </Accordion>

  <Accordion title="Stop limit order">
    A stop-limit [order](#orders) has both the [stop](#stop-price) and the limit prices. When the market price at the [pair](#market) reaches the [stop price](#stop-price), the order activates and executes as a basic [limit order](#limit-order).
  </Accordion>

  <Accordion title="Stop market order">
    A stop-market [order](#orders) executes when the market price reaches the [stop price](#stop-price). Traders use stop-market orders to limit losses during market volatility.
  </Accordion>

  <Accordion title="Stop price">
    A price set in advance to trigger a stop order.
  </Accordion>

  <Accordion title="Sub-account">
    A main account manages a sub-account. The main account assigns specific permissions to the sub-account (for example, the main account disables [margin trading](#margin-trading)).

    Crypto deposits are a separately enabled capability and are disabled by default. Once enabled for the account, the capability applies to the account and its sub-accounts; to request it, contact the assigned Account Manager or email [institutional@whitebit.com](mailto:institutional@whitebit.com).

    A sub-account can use a custom trading [fee](#fee) or rebate model defined for the sub-account. Use [`Query Market Fees`](/api-reference/trading/query-market-fee) to retrieve effective fees when an API key belongs to a sub-account.

    [RPI](#retail-price-improvement-rpi) trading uses account-specific fees or rebates. When a user places RPI orders through a sub-account, the system applies the effective sub-account fees. Use [`Query Market Fees`](/api-reference/trading/query-market-fee) to verify fees for RPI executions.
  </Accordion>
</AccordionGroup>

## T

<AccordionGroup>
  <Accordion title="Take profit/stop loss (TPSL)">
    A risk management feature to automatically close positions at predefined price levels. Take Profit (TP) closes at a higher price; Stop Loss (SL) closes at a lower price. These [orders](#orders) help traders manage risk and lock in profits automatically.
  </Accordion>

  <Accordion title="Taker">
    A taker accepts an existing [order](#orders) from the [order book](#order-book), taking liquidity from the [market](#market).
  </Accordion>

  <Accordion title="Ticker">
    An alphabetic and/or numeric abbreviation of the name of a digital [asset](#assets). (BTC - Bitcoin ticker).
  </Accordion>

  <Accordion title="Trade">
    See [Deal](#deal-trade)
  </Accordion>

  <Accordion title="Trade volume">
    See [Volume](#volumetrade-volume)
  </Accordion>

  <Accordion title="TradFi futures">
    Traditional-finance (TradFi) futures contracts on assets such as equities (for example, `AAPL_USD`). These contracts carry `type: tradfiFutures` and `isTradFiFutures: true` in the [markets](/api-reference/market-data/market-info) response, and availability is region-gated. Placing or modifying an order on a TradFi market additionally requires the account to hold the TradFi futures permission — see [Markets & Trading Pairs](/concepts/markets) for both gates. See [Perpetual futures](#perpetual-futures) for crypto-settled contracts.
  </Accordion>

  <Accordion title="Travel Rule">
    A regulatory requirement for Virtual Asset Service Providers (VASPs) to share originator and beneficiary information for cryptocurrency transfers above certain thresholds, mandated by frameworks such as the Financial Action Task Force (FATF) recommendations and Markets in Crypto-Assets (MiCA). WhiteBIT can hold deposits under statuses 27 (awaiting verification) and 28 (confirmation in progress) until verifying the required data. See [Travel Rule](/concepts/travel-rule) for when the rule applies and the API workflow.
  </Accordion>
</AccordionGroup>

## U

## V

<AccordionGroup>
  <Accordion title="Volume (Trade Volume)">
    The total number of shares or contracts buyers and sellers exchange in a [market](#market) on a given day.
  </Accordion>
</AccordionGroup>

## W

<AccordionGroup>
  <Accordion title="Webhook">
    An HTTP callback the platform sends to a partner-configured URL when an event occurs, such as a deposit or withdrawal status change. WhiteBIT signs each delivery so the consumer can verify the origin. See [Webhooks](/platform/webhook) for setup, the event catalog, and retry behavior.
  </Accordion>

  <Accordion title="WhiteBIT Codes">
    WhiteBIT Codes enable converting funds into a unique alphanumeric code. Easy and free to use.
  </Accordion>
</AccordionGroup>

## X

## Y

## Z


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.