> 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/changelog/readme.md).
# Changelog
New updates and improvements
{% updates format="full" %}
{% update date="2026-10-05" tags="feature,new-feature,improvement,fix" %}
## Version 0.1 — Private Beta
The first release of the EQUS Developer Toolkit: one toolkit to issue, hold, and verify digital credentials for people, organizations, and the AI agents acting on their behalf. Access is by approval during the private beta, and free for 90 days from the day your account is activated.
### **Operator Portal**
* Manage API keys, credential schemas, and templates
* Issue and revoke credentials
* Bring your own identity provider, so your team signs in with the accounts it already has
### **APIs and Embedded UI**
* REST APIs to issue, present, and verify credentials
* Embedded UI: white-label issuance and presentation flows you can drop into your web app, as an iframe or as web components
### **EQUS Wallet**
* Non-custodial mobile wallet for iOS and Android, with keys held in the Secure Enclave or StrongBox
* Available through Apple TestFlight and Google Play's testing track during the beta
### **Credential formats**
* SD-JWT VC: issue, present, and verify
* ISO mDoc (ISO 18013-5): verify, including US mobile driver's licenses
* AP2 delegated SD-JWT: signed mandates that let an AI agent prove who authorized it and what it may do
### **Exchange and transport**
* OpenID4VCI 1.0 and OpenID4VP 1.0
* QR engagement (ISO 18013-5) and the Digital Credentials API
### **Trust, revocation, and identifiers**
* Revocation with IETF Token Status Lists
* did:web, did:key, and did:peer
* X.509 certificate verification
### **Hosting**
* Hosted in the US (us-west-2) and the EU (Frankfurt, eu-central-1), with data kept in the region you choose
* New accounts start in sandbox, for test data only. When you're ready to go live, request production access; production is set up as a separate account and needs a different email address
* Rate limits apply to all beta accounts
### **EQUS Credentials SDK**
* The Rust core the Toolkit is built on, open source under Apache 2.0 and available on GitHub
* Bindings for Android, iOS, JVM, JavaScript, WebAssembly, and Linux
### **Known limitations**
* **Sandbox and production are separate accounts** during the beta, each with its own sign-in and email address.
* **Custodial wallets and the non-custodial web wallet** are available on request rather than by default.
* **W3C Verifiable Credentials, did:webvh, did:ethr, and pluggable key management** are available in the Credentials SDK but not yet in the Toolkit APIs.
* **mDoc issuance** is not yet available in the Toolkit; verification is.
* **EUDI Wallet and HAIP conformance** testing is in progress.
* **Usage reporting and billing** are not yet in the Operator Portal. Beta use is free.
### **What we're building next**
* Full verification of EU Digital Identity Wallet credentials, including X.509 relying party certificates
* Full AP2 support across the APIs and the EQUS Wallet
* Usage reporting, alerts, and billing in the Operator Portal
Read our launch blog
{% endupdate %}
{% endupdates %}
---
# 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/changelog/readme.md?ask=&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.
