> 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/readme.md).

# Developer Toolkit

A complete platform for issuing, holding, and verifying digital credentials, for people, organizations, and the AI agents acting on their behalf.

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask anything about the Developer Toolkit...</button>

<button type="button" class="button secondary" data-action="ask" data-query="How do I issue my first digital credential?" data-icon="rocket-launch">Issue my first credential</button> <button type="button" class="button secondary" data-action="ask" data-query="How do I register for the private beta?" data-icon="pen-to-square">Register for the private beta</button><button type="button" class="button secondary" data-action="ask" data-query="Which issuance flow should I use, and how does the tx_code reach the Holder?" data-icon="signs-post">Pick a flow</button> <button type="button" class="button secondary" data-action="ask" data-query="How do I accept credentials from EUDI Wallets?" data-icon="earth-europe">Accept EUDI Wallets</button> <button type="button" class="button secondary" data-action="ask" data-query="How can I use AP2 to delegate authority to my agents?" data-icon="robot">Delegate to agents</button>

&#x20;

<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-file-signature" style="color:$primary;">:file-signature:</i></h3></td><td><strong>Issue</strong></td><td>Turn a statement about your customer into a signed credential in their wallet.</td><td><a href="/docs/issuance/overview.md">Overview</a></td></tr><tr><td><h3><i class="fa-user-check" style="color:$primary;">:user-check:</i></h3></td><td><strong>Verify</strong></td><td>Ask for proof and get back only the claims you need.</td><td><a href="/docs/presentation/overview.md">Overview</a></td></tr><tr><td><h3><i class="fa-robot" style="color:$primary;">:robot:</i></h3></td><td><strong>Delegate</strong></td><td>Let an AI agent act for your user, within limits the user signed.</td><td><a href="/docs/agentic/delegation.md">Delegation</a></td></tr></tbody></table>

&#x20;

&#x20;

{% columns %}
{% column width="58.33333333333333%" %}

<figure><picture><source srcset="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2FiMYV6f2QVZV1EfLQmD56%2FEQUS_Issuance_Presentation_dark.svg?alt=media&#x26;token=a7beb26e-5b7c-41b5-927d-48ed4433ea1d" media="(prefers-color-scheme: dark)"><img src="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2FA0JEmIOaGpnEcZFTMDrx%2FEQUS_Issuance_Presentation_light.svg?alt=media&#x26;token=fd7d7e9e-1a56-4e38-a3e6-44940dc96088" alt="Your product issues and verifies credentials; users and their agents hold them and present proof back"></picture><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="41.66666666666667%" valign="middle" %}

## What is EQUS Developer Toolkit

EQUS Developer Toolkit (DTK) lets your company issue and verify credentials from your existing applications, without building from scratch. You decide who receives which credential and what proof to ask for.

<a href="/docs/about-the-system/overview.md" class="button primary" data-icon="book-open">Read the overview</a>
{% endcolumn %}
{% endcolumns %}

&#x20;

&#x20;

{% columns %}
{% column width="41.66666666666667%" valign="middle" %}

## Get started in minutes

Access is approval only during the private beta. Try the whole flow in the Operator Portal first, then bring it into your code.

{% hint style="info" icon="right-to-bracket" %}
**Already in the beta?** [Sign in to the Operator Portal](https://portal.us.equs.ai/).
{% endhint %}

<a href="/docs/onboarding/registration.md" class="button primary" data-icon="rocket-launch">Join the private beta</a>&#x20;
{% endcolumn %}

{% column width="58.33333333333333%" %}
{% stepper %}
{% step %}

#### Join the private beta

[Request access](/docs/onboarding/registration.md), and your application will be reviewed. Once approved, you will be sent client credentials to access the Operator Portal.
{% endstep %}

{% step %}

#### Configure in the Operator Portal

Create an [Issuer and a VC Schema](/docs/issuance/configuration-issuer-and-vc-schema.md): who signs the credential, and what it holds.
{% endstep %}

{% step %}

#### Issue your first credential

Send an Offer [from the Portal](/docs/issuance/flow-1/trigger-by-user-for-any-wallet-email-tx_code-delivery/method-3-operator-portal.md) and collect it in any compliant wallet. No code yet.
{% endstep %}

{% step %}

#### Integrate into your code

Run the [same flow from your back end](/docs/issuance/flow-1/trigger-by-user-for-any-wallet-email-tx_code-delivery/method-1-api.md), using the Issuer and VC Schema you already have.
{% endstep %}
{% endstepper %}
{% endcolumn %}
{% endcolumns %}

&#x20;

&#x20;

{% columns %}
{% column width="50%" %}

## Built on open source

The Developer Toolkit is built on **EQUS Credentials SDK**, our library for issuing, holding, presenting and verifying credentials for people, organizations and AI agents. Its Rust core ships with wrappers for Node.js, WASM, Kotlin and Swift, under the Apache 2.0 license. Issues and pull requests are welcome.

<a href="https://github.com/equs-ai/equs-credentials-sdk" class="button primary" data-icon="github">Join us on GitHub</a> <a href="https://github.com/equs-ai/equs-credentials-sdk/blob/main/CONTRIBUTING.md" class="button secondary" data-icon="code-pull-request">Contributing guide</a>
{% endcolumn %}

{% column width="50%" %}

## Built on open standards

Any wallet that speaks them can join the same journeys.

`OID4VCI 1.0` `OID4VP 1.0` `DCQL` `SD-JWT VC` `ISO mDocs` `Token Status List` `did:web` `did:key`

<a href="/docs/about-the-system/standards.md" class="button secondary" data-icon="list-check">All supported standards</a>
{% endcolumn %}
{% endcolumns %}

&#x20;

&#x20;

<table data-card-size="large" 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-book-open" style="color:$primary;">:book-open:</i></h3></td><td><strong>Documentation</strong></td><td>Concepts, flows and guides for every part of the Developer Toolkit.</td><td><a href="/docs/about-the-system/overview.md">Overview</a></td></tr><tr><td><h3><i class="fa-code" style="color:$primary;">:code:</i></h3></td><td><strong>API Reference</strong></td><td>Every endpoint of the Control, Integration, Web Wallet and Identity Manager APIs.</td><td><a href="/api/integration-api.md">Integration API</a></td></tr></tbody></table>

&#x20;


---

# 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/readme.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.