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

# Registration

Get access to the Operator Portal and start using the EQUS Developer Toolkit.

Access to EQUS Developer Toolkit is by approval only. You request access, EQUS approves it and sets up your **Tenant**, and you receive an email inviting you to the **Operator Portal**: the web console where you manage your Tenant and find the client credentials your back end needs to call the platform APIs.

Once the invitation arrives, setting up your account takes a few minutes.

### 1. Request access 📨

Submit [the access request form](https://www.equs.ai/contact#developer) on behalf of your organization. When EQUS approves the request, the invitation is sent to the email address you provided.

### 2. Open the invitation 📬

The email subject is "*EQUS is inviting you to set up \<your organization> on Developer Toolkit"*. Open the link in it to start setting up your account. You don't need a password yet: the link itself confirms that the email address is yours.

The link is personal and works once:

* It expires after 72 hours. If it has expired, contact EQUS for a new invitation. A new invitation cancels any earlier link.
* Once you've set your password, the link is used up. To come back later, sign in to the [Operator Portal](https://portal.us.equs.ai/) instead.
* Keep it private: anyone with the link can set up your organization's account.

### 3. Set your password 🔑

The first screen asks you to choose a password and confirm it. The password rules are checked as you type. You can't use the rest of the portal until this step is done.

<figure><img src="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2FQQrGWQ8Yr1X7ARxUc3Ap%2Fkeycloak.qa.dsr.gaminghub.bc-labs.dev-2026-09-28.png?alt=media&amp;token=3ad71f53-ad75-4f26-b5c5-1bfb55a2b189" alt=""><figcaption></figcaption></figure>

### 4. Add a passkey (optional) 👆

Register a passkey to sign in later with your fingerprint, face, or device lock instead of your password, or skip this step.

<figure><img src="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2FlTweOQJaAjnpb51ZwXNT%2Fkeycloak.qa.dsr.gaminghub.bc-labs.dev-2026-09-28%20(1).png?alt=media&amp;token=1985bde9-768e-483d-96d1-9e77e67166eb" alt=""><figcaption></figcaption></figure>

### 5. Save your client credentials 🔒

The last step shows your **Client ID** and **Client Secret**. Your back end uses them with the OAuth 2.0 Client Credentials flow to authenticate its calls to the platform APIs. See [Authentication](/standards/api/authentication.md).

{% hint style="danger" %}
**The Client Secret is shown only once.** EQUS doesn't store it, so it can't be displayed again. Copy it to a secure place, such as your secrets manager, before you finish. Seriously, copy it now. Future you will thank you 🙏
{% endhint %}

Tick **I verify that I have securely saved the secret,** and then select **Finish** to enter the portal.

If you lose the secret, generate a new one in the portal under **Instructions → APIs**. Your Client ID stays visible there at any time.

<figure><img src="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2F01rLIuLe4XWG23zPZb8n%2Foperator-portal.qa.dsr.gaminghub.bc-labs.dev-2026-09-28.png?alt=media&amp;token=7567df83-cb56-4586-8704-9a487608495c" alt=""><figcaption></figcaption></figure>

### After you sign in 🎉

The portal opens on **Issuance**. From the header you can reach:

* **Issuance** - set up Issuers and VC Schemas, and issue and revoke credentials without writing code.
* **Verification** - set up Verifiers and VP Schemas.
* **Instructions** - your API credentials, integration guides and OpenAPI specs, Embedded UI setup (allowed origins and [branding](/standards/embedded-ui/styles-and-branding.md)), and links to the mobile test wallets.
* **Settings** - your Tenant's configuration, including connecting [your own identity provider](/standards/onboarding/bring-your-own-idp.md).

Two indicators may appear across the portal:

* A **Sandbox** label, if your Tenant was set up as a sandbox rather than for production.
* A banner with the time remaining, if your access has an end date. When it ends, the portal and your client credentials stop working. Contact EQUS to extend it.

<figure><img src="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2FIpth05mVrleNJWHbrWny%2Foperator-portal_edited.png?alt=media&amp;token=09ff289d-d711-4b62-b395-47990769c065" alt=""><figcaption></figcaption></figure>

### Next steps 🚀

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-lock" style="color:$primary;">:lock:</i></h3></td><td><strong>Authentication</strong></td><td>Use your client credentials to call the APIs.</td><td><a href="/standards/api/authentication.md">Authentication</a></td></tr><tr><td><h3><i class="fa-id-card" style="color:$primary;">:id-card:</i></h3></td><td><strong>Issuance</strong></td><td>Issue your first credential.</td><td><a href="/standards/issuance/overview.md">Issuance</a></td></tr><tr><td><h3><i class="fa-qrcode" style="color:$primary;">:qrcode:</i></h3></td><td><strong>Presentation</strong></td><td>Request your first presentation.</td><td><a href="/standards/presentation/overview.md">Presentation</a></td></tr></tbody></table>


---

# 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.toolkit.equs.ai/standards/onboarding/registration.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.