> For the complete documentation index, see [llms.txt](https://ordinox.gitbook.io/ordinox-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ordinox.gitbook.io/ordinox-docs/ordinox-developer-tooling/using-ordinox-dashboard/creating-an-ordinox-account.md).

# Creating an OrdinoX Account

OrdinoX currently uses an account based model to help in a quick developer experience. Current API based inscription services like OkX and Unisat, require you to transfer BTC from your server / bot platform to an address given by the API dynamically. \
\
Based on the amount of bitcoin development experience you carry, this can be quite challenging, considering that you might have start this off by setting up a local bitcoin-wallet using `bitcoin-cli` and then using RPC either remotely or locally to transfer BTC to fullfill inscriptions. 

Fret no more, with OrdinoX developer platform, you can use your favourite wallet to load some sats upfront into your OrdinoX account and then retroactively use it as "credits", so you can bulk-inscribe into your destination wallets without the need to pay as you go.

### Creating an Account

<figure><img src="https://1711746550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtPXb2zqZDpNv1VvfPoYK%2Fuploads%2FwCdtx7aue41ExqynxekM%2Fimage.png?alt=media&amp;token=79fac67d-8057-42f4-808b-b5e020573fe3" alt=""><figcaption></figcaption></figure>

We currently use a super simple email-based auth. In the future, we plan to make this more "web3" by adding wallet support and letting you sign over your requests for authentication.