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

> ## Agent Instructions
> Bitnob API requests authenticate with an `X-Auth-Client` API key header against https://api.bitnob.com.
> Always use the sandbox environment for testing. Never put live API keys in sample code.
> Money amounts are integers in the smallest unit of the currency (satoshis for BTC, cents for fiat). Never use floats.
> Every state-changing request takes a client-supplied `reference` and must be treated as idempotent on retry.
> Quotes expire. Re-quote rather than reusing a stale quote id.

# How integrators can make money

> Spread, fee, and packaging models for earning revenue on top of the Trading API.

## Add a spread (markup) on trades

When you fetch a quote via /api/trading/quotes, you receive:

```json theme={null}
{
  "price": "83125",
  "exchange": {
    "send_currency": "USDT",
    "send_quantity": "100",
    "receive_currency": "BTC",
    "receive_quantity": "0.00120301"
  }
}
```

You can **offer the user a slightly lower rate** than what you receive.

Example:

* Bitnob rate: 1 BTC = 83,125 USDT, so 100 USDT buys 120,301 sats
* You offer: 1 BTC = 85,000 USDT, so the user receives 117,647 sats
* Effective spread: 2.2%, or 2,654 sats on this trade

When executing the trade:

* You still use the Bitnob quote (locked or live)
* You record the actual **execution amount** vs. **user-facing rate**
* **The difference = your profit**, in the output asset

This model works even at high volume and is **invisible to the user** if the rate is still competitive.

## Bundle trading into a service offering

For platforms where trading is a backend function (e.g., remittances, merchant payouts):

Offer a fixed USD (or NGN) rate to your users (e.g., “Send \$100 to Nigeria”)

**On the backend, you:**

* Accept bitcoin
* Convert to USDT using Bitnob
* Lock in a margin inside the conversion logic (e.g., build 1-2% spread into rates)

This gives you:

* **Price control**
* **Earnings from FX/timing edge**
* **Revenue on every trade**, whether the user is aware of the backend asset movement or not

Naira rails: the same model works with NGN. Accept naira from a Nigerian user, convert to USDT, USDC, or Bitcoin (or the reverse to pay out in naira), and build your spread into the NGN rate.

## Charge a platform or execution fee

Some apps transparently monetize via fees on each trade:

* Trade Value: \$250.00
* Network Fee: \$0.00
* Execution Fee: \$2.50 (1%)
* Total Charged: \$252.50

You can:

* Show this in the UI
* Bake it into the output value (user receives slightly less)
* Track this via internal metadata on each reference and order `id`

Bitnob doesn’t charge trading fees by default, so this gives you room to add your own layer.

## Tiered access for sub-Accounts (B2B2C)

If you run a platform serving other businesses or teams:

* Offer **white-labeled trading access**
* Mark up rates
* Charge monthly platform fees
* Offer volume-based discounts or rewards

You become the **merchant of record**, and Bitnob is your infrastructure layer.

## Offer instant swap with delayed fulfillment

This is an advanced strategy.

* Let users “Buy bitcoin Now” at a given rate
* Delay execution a few minutes while batching trades
* **Capture timing or price efficiency** using backend logic
* Fulfill with Bitnob once execution terms are favorable

This is similar to how Cash App and Revolut optimize behind the scenes.

Only do this if you have treasury experience or strong controls.

## Incentivized spread: Subsidize rate on buy, earn on sell

For customer acquisition:

* Offer best-in-market rate for BTC purchases (maybe break even)
* Make money on the sell side when user exits to stablecoin

This is common in wallets, trading apps, and even DeFi platforms.

## Best practices for monetizing

* **Track every trade’s input/output/spread/fees** in your internal ledger
* Use the reference field to link trades to users or business units
* Record fee revenue separately for accounting, analytics, and tiering
* Consider limits per user per day to protect against abuse


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