> For the complete documentation index, see [llms.txt](https://docs.bloxroute.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxroute.com/getting-started/register-an-account.md).

# Create An Account

Creating an account with bloXroute is fast and easy – simply follow the steps below.

1. Either click "Getting started on bloXroute's website, or go directly to the registration page of the [Account Portal](https://portal.bloxroute.com/registration).

<figure><img src="https://content.gitbook.com/content/ZgMW6iwGsmn9ejYuG9vP/blobs/QjZ7ea5oseCXy0eyhkTe/image.png" alt="" width="375"><figcaption></figcaption></figure>

2. Fill out the fields, verify humanity (if prompted), and click “Sign Up"
3. Go to your email inbox and click the link in the verification link that was sent to you.

**That’s it, your registration is complete!**

You are now on the **Introductory** plan, which allows you to send transactions on all supported chains and begin connecting to bloXroute services.

From here, you can enhance your setup by adding the services you need, such as real-time data streams, gateways, or additional execution services. Review the [pricing page](https://bloxroute.com/pricing/) for a breakdown of available bundles and services.

You can view and configure available services anytime in the Account Portal.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bloxroute.com/getting-started/register-an-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
