> ## 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 has two APIs. The Business API (payouts, cards, trading, virtual accounts, stablecoin and bitcoin transfers) is at https://api.bitnob.com. The Enterprise API (non-custodial wallets) is at https://api.platform.bitnob.com.
> Business API auth: sign every request with HMAC-SHA256 and send four headers: `X-Auth-Client` (your client ID), `X-Auth-Timestamp` (Unix seconds), `X-Auth-Nonce` (16 random bytes, hex), and `X-Auth-Signature`, the hex HMAC-SHA256 of `CLIENT_ID:TIMESTAMP:NONCE:BODY` keyed with your client secret. BODY is the exact request body string you send, or an empty string. A missing header, a bad signature, or a timestamp more than about 5 minutes off returns `401`.
> Enterprise API auth: send your key in the `X-API-Key` header. Write requests such as creating a transaction also need an `Idempotency-Key` header, or they fail with `idempotency_key_required` before anything happens.
> Sandbox and production share the Business API base URL. The credentials you sign with select the environment, and `GET /api/whoami` returns it in `data.environment`. Use sandbox credentials in sample code and tests, and never put live credentials in code.
> Amounts are strings unless stated otherwise. Never parse them into floats. Balances, transactions, withdrawals (`POST /api/withdrawals`) and virtual accounts use integer strings in the smallest unit: satoshis for BTC, 6 decimals for USDT and USDC, kobo for NGN, and cents for KES and UGX (100 is 1 KES or 1 UGX). A mobile money collection takes `amount` as a JSON integer in cents.
> Payouts and trading use decimal strings in major units: a payout quote `amount` of `"1"` is 1 USDT, and a trading `quantity` of `"0.0001"` is 0.0001 BTC. Payout responses also carry `cent_amount`, the settlement amount in minor units.
> Card amounts are micro-units (1 USD = 1,000,000). Send them as JSON integers. Card responses return them as integer strings, and card webhooks as integers.
> Generate a unique `reference` for each money movement before the first attempt, and reuse it on retries. A reused reference returns `409` on payout quotes (`ALREADY_EXISTS`), withdrawals (`DUPLICATE_KEY_ERROR`) and card creation (`ALREADY_EXISTS`). It returns the existing record on NGN-pair trading orders, NGN virtual accounts and active mobile money collections. On a mobile money collection that has closed or failed it returns `409` `DUPLICATE_REFERENCE`. It isn't checked on crypto-pair trading orders, so look the order up with `GET /api/trading/orders/{reference}` before resending.
> Quotes expire at `expires_at`; read it from the response instead of assuming a window. An expired trading quote returns `422` `PRECONDITION_FAILED`, and an expired payout quote returns `400` `VALIDATION_ERROR`. Create a new quote rather than retrying. A payout quote can be initialized once, and a trading quote is consumed by the order that fills it.
> Webhooks: verify the `x-bitnob-signature` header, the hex HMAC-SHA512 of the raw request body keyed with your webhook secret, before parsing JSON. Compare in constant time and de-duplicate on `event_id`. A successful API response means accepted: confirm the outcome from the webhook, such as `payouts.withdrawal.success`.
> Errors return `status`, `code` and `detail`. Branch on `code`, never on `detail`. Since the November 5, 2026 response format change, each company gets either the current or the new error codes until its cutoff date, so handle both: `PROVIDER_ERROR` or `PROCESSING_ERROR`, and `BVN_PROVIDER_UNAVAILABLE` or `BVN_VERIFICATION_UNAVAILABLE`. A body that fails to parse returns `{"error": {"code": "BAD_REQUEST"}}`.

# Private key generator

> An educational secp256k1 key generator showing how a Bitcoin private key relates to its WIF encoding and public key.

Bitcoin private key generator

Generated locally in your browser. Nothing leaves this page.

For education and testing only. Browser-generated keys are not safe for real funds. Never
send bitcoin to an address derived from a key made with this tool.

Generate private key

Clear

Private key (hex, 32 bytes)

WIF (mainnet, compressed)

> [!WARNING]
>
> **Educational use only. Never put real funds behind a key generated in a web browser.**
>
> Browser memory can be read by extensions, the page can be cached, and you cannot audit what the page did with the key. Real keys belong in a hardware wallet or an audited offline generator. For production custody, see the [Bitnob Enterprise API](https://www.bitnob.dev/docs/platform/overview.md), where keys are generated inside a hardware-isolated enclave and never exported.

A Bitcoin private key is simply a 256-bit number below the secp256k1 curve order. Its public key is derived by multiplying the curve's generator point by that number, and the address is a hash of the public key. Each step goes one way only: you can derive an address from a key, never the reverse.

## The chain of derivation

```
private key (256-bit number)
  → public key   (elliptic curve point multiplication)
    → address    (hash + checksum encoding)
```

## Key formats

| Format | Looks like | Notes |
| - | - | - |
| Raw hex | 64 hex characters | The underlying number |
| WIF | Starts with `K`, `L`, or `5` | Base58Check with a network byte and checksum |
| WIF (testnet) | Starts with `c` or `9` | Testnet version byte |

`K` and `L` indicate a compressed public key, which is what modern wallets use; `5` indicates the older uncompressed form.

## What real wallets do instead

Production wallets do not generate independent keys. They generate one BIP-39 seed phrase, then derive an unlimited tree of keys from it deterministically (BIP-32). That way a single backup recovers every address. The course module on [wallets and addresses](https://www.bitnob.dev/learn/courses/bitcoin-core-cli/module-3.md) walks through this from the CLI.


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