> For the complete documentation index, see [llms.txt](https://oten.gitbook.io/trust-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oten.gitbook.io/trust-support/documentation/api-reference/quick-start.md).

# Quick Start

Get started with Oten Trust in just a few minutes.

In this guide, you will:

1. Create or sign in to your Oten Trust account
2. Generate an API key

{% hint style="info" %}
You can create your own account directly at [trust.oten.com](https://trust.oten.com)
{% endhint %}

***

### Step 1: Create an account or sign in

Go to <https://trust.oten.com>

If you are new to Oten Trust:

1. Click **Sign Up**
2. Create your account
3. Verify your email if prompted
4. Sign in to access the dashboard

If you already have an account:

1. Go to `trust.oten.com`
2. Click **Sign In**
3. Enter your login credentials

After signing in, you should be able to access:

* Your Oten Trust dashboard
* API key management
* Usage and request insights

{% hint style="success" %}
Once you can access the dashboard at <https://trust.oten.com>, you are ready to create your first API key.
{% endhint %}

***

### Step 2: Create an API key

After signing in to `trust.oten.com`:

1. Open the navigation menu
2. Go to **API Keys & Usage**
3. Click **+ Create New API Key**
4. Enter a descriptive name for the key, such as:
   * `Production Backend`
   * `Staging`
   * `Local Testing`
5. Confirm creation
6. Copy the secret key and store it somewhere secure

{% hint style="danger" %}
Your secret API key is shown only once. Be sure to copy and save it before leaving the page.
{% endhint %}

#### Recommended naming convention

Use names that clearly describe where the key will be used.

**Examples**

* `Production Backend`
* `Staging API`
* `Developer Sandbox`

#### Store your key securely

Do not expose API keys in frontend code or commit them to source control.

**Recommended approach**

* store the key in an environment variable
* use it only from your backend or secure server environment
* rotate keys periodically as part of your security practice

***