> For the complete documentation index, see [llms.txt](https://t1t.gitbook.io/t1c-js-guide-v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t1t.gitbook.io/t1c-js-guide-v3/master.md).
# Introduction
Trust1Connector v3 Documentation
## A Word of Introduction
The Trust1Connector Javascript SDK is a library that functions as a proxy towards the Trust1Connector API. This Library does not contain any business logic and is a refernce implementation for the Trust1Connector API (HTTP/JSON).
{% hint style="warning" %}
Sample code uses ES6 language features such as arrow functions and promises. For compatibility with IE11, code written with these features must be either transpiled using tools like `Babel` or refactored accordingly using callbacks which are also available on the Trust1Connector Javascript SDK.
{% endhint %}
The Trust1Connector is a middleware which interacts with **hardware tokens** and **system certificate stores** (where certificates are stored and protected within the operating system).
### Trust1Connector's ambitions
The ambitions of the Trust1Connector is to:
* provide a **generic interface** to hardware tokens and smart cards
* operating **system agnostic** (works for all operating systems)
* **browser agnostic** (not depending on a browser plugin)
* facilitate the **onboarding** and **identity dematrialization**
* facilitate the derivation towards a **mobile identity**
* favours a decentralized approach and **privacy-first**
* facilitate user **authentication** and **digital signatures**
* facilitates identity information **validation** and **secured transport**
* favours a [**Zero-Knowledge**](https://en.wikipedia.org/wiki/Zero-knowledge_proof) approach
* exchange [**Verifiable Claims**](https://www.w3.org/TR/vc-data-model-2.0/)
---
# 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://t1t.gitbook.io/t1c-js-guide-v3/master.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.
