> For the complete documentation index, see [llms.txt](https://docs.hashsphere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashsphere.com/development/creating-initial-accounts.md).

# Creating Initial Accounts

This guide covers account bootstrap on a newly provisioned HashSphere. It assumes you already have network connectivity to your private endpoints.

### What you are given

Every HashSphere environment is provisioned with an **operator account**. The HashSphere team provides this during onboarding.

You will be provided with:

* Operator Account ID
* Operator Public Key
* Operator Private Key
* Network address book (node addresses and IDs)

Together, these allow you to initialize a Hiero SDK client and create additional accounts.

By the end of this guide, you will be able to:

1. Connect to your HashSphere using a Hiero SDK
2. Create and fund new HashSphere accounts
3. Retrieve new Account IDs and manage their key pairs
4. Extend this pattern for automated or large-scale account provisioning

### Using the Hiero JavaScript SDK

#### Prerequisites

Before you begin, ensure you have:

* [ ] Operator Account ID (provided during onboarding)
* [ ] Operator Private Key (provided during onboarding)
* [ ] Network address book (provided during onboarding)
* [ ] Network access to your HashSphere endpoints
* [ ] A Node.js project with the Hiero JavaScript SDK installed ([install guide](https://docs.hedera.com/hedera/getting-started-hedera-native-developers/create-an-account#install-the-sdk))

{% hint style="info" %}
The Operator Private Key is a sensitive credential.

* Do not store it in source control.
* Do not transmit it in plaintext.
* Use environment variables, secure parameter stores, wallet solutions, or KMS/HSM integration where available.
  {% endhint %}

#### Setting up the client

To create accounts, your client must connect directly to your private HashSphere network. Configure the SDK with the node address book and your operator credentials.

For reference on client configuration patterns, see:

* [Building your Hedera client](https://docs.hedera.com/hedera/sdks-and-apis/sdks/client)
* [SDK Client Configuration](/development/application-development-on-hashsphere/sdk-client-configuration.md)

#### Creating an account

To create a new account, use the `AccountCreateTransaction` API from the Hiero SDK.

A code example to create a new account using the `AccountCreateTransaction` can be found in the Hedera documentation [here](https://docs.hedera.com/hedera/getting-started-hedera-native-developers/create-an-account#step-3-create-your-first-account-on-hedera).

#### Verifying account creation

You can confirm that your new account was created successfully using one of the following methods.

#### Option 1: HashScan

The HashSphere team will provide an environment-specific explorer URL.

To verify:

1. Navigate to the HashSphere explorer link
2. Search for the newly created Account ID
3. Confirm the transaction and account details

Access may be restricted to approved network environments.

#### Option 2: Mirror Node Query

You may also verify the account using the Mirror Node REST API. Sample code and the endpoint to query can be found [here](https://docs.hedera.com/hedera/getting-started-hedera-native-developers/create-an-account#step-4-query-the-account-balance-using-mirror-node-api).

Query the mirror node for the newly created Account ID to confirm:

* Account existence
* Transaction history
* Current balance

### Next steps

You now have the ability to:

* Create accounts programmatically
* Fund accounts using the Operator account
* Capture Account IDs and key pairs
* Integrate account creation into automated workflows

This same pattern can be extended for:

* Bulk account provisioning
* User onboarding systems
* Enterprise identity mapping


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hashsphere.com/development/creating-initial-accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.