> For the complete documentation index, see [llms.txt](https://docs.zk.me/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zk.me/hub/start/onboarding.md).

# Onboarding Checklist

{% hint style="info" %}
**Note:** 🗣️ Reach out to us at <mark style="color:blue;">**<contact@zk.me>**</mark> to get your project domain whitelisted asap.
{% endhint %}

{% stepper %}
{% step %}

#### Sign up for a zkMe dashboard account using a company email

* If you are implementing **zkKYC, KYT, zkOBS, or zkKYA**, please register for a **zkMe dashboard account** via [**this link**](https://dashboard.zk.me).
* If you are implementing **zkKYB**, please click [**this link**](https://kyb-dashboard.zk.me/signup) to get started.

{% hint style="info" %}
**Note:** The account is a Self-Sovereign Identity (SSI) that is tied to the email, please pick an email you will continue to use to manage the customer account from.
{% endhint %}
{% endstep %}

{% step %}

#### Accept the zkMe Terms & Conditions and the [App Privacy Policy](https://zk.me/app-privacy-policies)

{% endstep %}

{% step %}

#### Inform zkMe which [Credentials](/hub/what/catalog.md) you’d like to verify

Share your company email, the chain ecosystems you intend to support, the level of decentralization you want to support (pick from an [On-chain](/hub/start/onboarding/zkkyc-levels.md#on-chain-mint-default), or [Cross-chain](/hub/start/onboarding/zkkyc-levels.md#cross-chain) Verification), expected launch date, and anticipated traffic with zkMe in order to receive the required permissions.&#x20;
{% endstep %}

{% step %}

#### Once required permissions are assigned by zkMe, refer to the [Dashboard ](/hub/start/onboarding/dashboard.md) to access your API Key and configure your setup

{% endstep %}

{% step %}

#### **Before using production services**

For services billed through the zkMe Dashboard, ensure that Production API Access is active and your Available Credits balance is sufficient to cover the applicable charges. Purchasing Credits alone does not activate Production API Access. Follow the [Billing & Credits](https://docs.zk.me/hub/start/onboarding/dashboard/billing-and-credits) guide to complete your billing setup.

If you use a separate product dashboard or service agreement, confirm the applicable billing requirements with zkMe.
{% endstep %}

{% step %}

### Start to integrate, referring to the [Integration Checklist](/hub/start/onboarding/integration.md)

{% endstep %}
{% endstepper %}


---

# 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.zk.me/hub/start/onboarding.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.