# Getting Started

> **Preview**: toani Control is under development. The steps, endpoints, and SDK API **may change**; refer to the released console and OpenAPI specification for official documentation.

***

toani Control provides **policy-driven secure execution** for enterprise AI applications: your application references a `policyId`, action, and parameters; **credential plaintext is handled by the Execution Plane in TEE**, and returns an **Execution Receipt** and audit reference.

***

## Pre-Integration Setup (Overview)

Before writing business logic, enterprise admins typically complete these steps in the console:

### Step One: Enable Tenant and Environment

* Obtain **Tenant ID**, **API Key** (and Webhook Secret if using callbacks).
* Confirm environment: `sandbox` / `production` (names per release).

### Step Two: Configure Credential Plane

* Create **Vault namespaces** (e.g., `prod-schwab-service`, `user-brokerage-accounts`).
* Write credentials via **Management API** (**mTLS**, admin JWT plus MFA); responses contain `credential_id` and **fingerprint**, not plaintext.

### Step Three: Define and Publish Policy

* Configure **agent binding**, **credential\_ref** (with scenario A/B/C), **allowed\_actions**, **constraints**, **hitl**, optional **zkme\_requirements**.
* Policies are **versioned**; old versions remain queryable.

### Step Four: Initialize SDK on Application Side

* Initialize with tenant-level `apiKey` / `tenantId` (see [SDK](/toani-control/getting-started/sdk.md)).
* Configure `idempotencyKey` for idempotence and retry (design supports it).

***

## Next Steps

| Documentation                                          | Description                                                |
| ------------------------------------------------------ | ---------------------------------------------------------- |
| [SDK](/toani-control/getting-started/sdk.md)           | `execute` / `executeAsync` / batch pre-authorization, etc. |
| [API](/toani-control/getting-started/api-reference.md) | HTTP endpoints and secure transport agreements             |

***

## Comparison with toani Vault Integration Path

| Dimension                  | toani Vault                      | toani Control (Preview)                                |
| -------------------------- | -------------------------------- | ------------------------------------------------------ |
| Console focus              | Credentials plus Sandbox session | Vault namespaces plus Policy plus compliance dashboard |
| Authentication             | PASETO v4 (toani Vault Token)    | Enterprise API Key plus Action Token (execution chain) |
| Preferred code entry point | `toaniVaultSDK` plus `sandbox.*` | `toaniControl` plus `execute*`                         |

If you already use toani Vault, check whether **toani Control** offers a better fit for enterprise procurement and **batch/HITL** delivery.

***

## Support and Feedback

Before GA, integration questions: contact toani.ai via sales/technical support or internal ticketing channels. **Documentation URLs and anchors** may redirect after site information architecture changes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.toani.ai/toani-control/getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.