> ## 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.

# Trading API revenue playbook

> Business models integrators can build on the Trading API, and which ones suit which teams.

## Overview

Bitnob provides the infrastructure. You control the business model.

This guide outlines how integrators, platforms, and apps can generate revenue using the Bitnob Trading API while delivering great experiences to users. You can apply these strategies whether you're a wallet, exchange, neobank, remittance company, or B2B fintech.

The same strategies apply across every supported pair, including the NGN pairs (naira ↔ USDT, USDC, Bitcoin), which open a naira on/off-ramp you can price and earn a spread on.

## Revenue model #1: Spread-based trading (invisible profit)

Concept: You offer a trade rate slightly less favorable than what Bitnob provides, and you keep the difference.

How it works:

* Fetch quote: the quote's `price` is Bitnob's rate, e.g. 1 BTC = 83,125 USDT
* Show your user: a slightly wider rate, e.g. 1 BTC = 85,000 USDT
* Execute trade using original Bitnob quote
* Profit = (Bitnob output - User output)

You earn in the output asset, without needing to show any fees.

Recommended when:

* You want to keep UX clean
* You're competing on convenience, not pricing
* You want to earn at scale silently

## Revenue model #2: Markup fees (transparent trade fees)

Concept: Charge users a visible fee per trade, shown in UI or baked into output.

Example:

* User sells \$100 BTC
* Fee: 1% = \$1
* User receives \$99 in USDT
* You receive \$100, keep \$1

You earn via markup, and can adjust fee tiers per user, volume, or plan.

Recommended when:

* You want users to understand your revenue model
* You support multiple B2B clients or need fine-grained billing
* You're matching competitors with clear pricing

## Revenue model #3: FX control in cross-border flows

Concept: Control the full remittance or payout flow by fixing the FX rate, while optimizing execution backend via Bitnob.

How it works:

* You promise: “\$100 worth of BTC = ₦90,000 payout”
* Internally: You use Bitnob Trading API to convert BTC to USDT
* You set a margin buffer (e.g. 1–2%) in your FX model
* Fulfill payout via stablecoin → fiat off-ramp

You earn from timing advantage or pricing spread.

Recommended when:

* You're running a remittance, gig payout, or merchant payment platform
* You need guaranteed fiat delivery while controlling your liquidity flow

## Revenue model #4: Sub-account / platform margining (B2B2C)

Concept: Provide trading access to partners or agents, while controlling the execution layer and price markup.

Flow:

* Create sub-ledgers or tenants in your system
* Fetch real quotes, inject a spread per partner
* Show that partner their custom pricing
* Route everything via your backend to Bitnob

You earn on every trade via controlled pricing.

Recommended when:

* You're a fintech infra provider, white-labeled platform, or multi-tenant wallet
* You want to build a margin-generating partner ecosystem

## Revenue model #5: Batch execution & treasury optimization

Concept: Let users initiate trades instantly, but batch execution in backend for better pricing.

Workflow:

* User sees: “Buy BTC now for \$50”
* Backend queues requests for 1–5 minutes
* You batch execute using Bitnob at optimal moment
* You keep timing-based profit delta (risk-managed)

You earn from price timing or aggregation gains.

Recommended only if:

* You have experience managing BTC liquidity or risk
* You have internal treasury or trading logic
* You're handling large volume across users

## Ledger & tracking framework

Use this reference to track and report earnings per trade.

| Field | Description |
| - | - |
| reference | Your internal trade ID |
| bitnobRate | Actual rate of the order you submitted with [Create order](https://www.bitnob.dev/api-reference/trading/submit-order.md) |
| userRate | Rate shown to user |
| inputAmount | Amount user is converting, in the input asset's smallest unit |
| outputAmount | Amount user received |
| bitnobOutput | Actual amount received from Bitnob |
| spreadEarned | bitnobOutput - outputAmount |
| feeCharged | Optional flat/percentage trade fee |
| timestamp | Time of trade |

## Playbook summary

| Model | Transparent to User | Risk Level | Revenue Potential |
| - | - | - | - |
| Spread-based pricing | No | Low | Scales silently |
| Flat/percentage trade fees | Yes | Low | Simple, visible |
| FX margin control | No | Medium | High with volume |
| Platform-wide pricing tier | Optional | Low | Works with B2B |
| Delayed batch execution | No | High | Advanced model |


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