> For the complete documentation index, see [llms.txt](https://hinkal-team.gitbook.io/hinkal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hinkal-team.gitbook.io/hinkal/hinkal-api/getting-started.md).

# Getting Started

Hinkal's privacy protocol is exposed through the **API** — a REST API whose server runs inside a secure enclave (a GCP Confidential VM, AMD SEV). Private key material never leaves it.

The API is the foundation. On top of it, Hinkal offers a higher-level product — [Wallet-as-a-Service (WaaS)](/hinkal/hinkal-waas/quick-start.md) — for a different integration style. Both run on the same enclave and the same host, `https://api.hinkal.io`.

## Ways to integrate

### API (direct)

The core API. The caller keeps their **own wallet** (EVM, Solana, or Tron) and signs each request with it — a session signature authorizes all requests for 24 hours by default, or a per-transaction EIP-712 typed-data (EVM/Tron) / ed25519 (Solana) signature authorizes individual operations. The enclave custodies only the Hinkal shielded key that operates the privacy layer.

→ [API Overview](/hinkal/hinkal-api/description/overview.md)

### Wallet-as-a-Service (WaaS)

A managed-wallet layer. Hinkal generates and custodies EVM, Solana, and Tron wallets for your users inside the enclave, organized under an organization / user / policy model. Requests are authenticated with an Ed25519 **X-Stamp** signature.

→ [WaaS Quick Start](/hinkal/hinkal-waas/quick-start.md)

## Which one should I use?

|                           | API                                   | WaaS                         |
| ------------------------- | ------------------------------------- | ---------------------------- |
| Who holds the wallet      | The caller                            | Hinkal (managed)             |
| Authentication            | EVM, Tron, or Solana wallet signature | Ed25519 X-Stamp              |
| Org / user / policy model | No                                    | Yes                          |
| Typical integrator        | Dapp / wallet                         | Team wanting managed wallets |

## Next steps

* [API Overview](/hinkal/hinkal-api/description/overview.md) — how the enclave model works
* [API Authentication](/hinkal/hinkal-api/description/authentication.md) — signing requests
* [API Examples](/hinkal/hinkal-api/description/examples.md) — runnable code
* [WaaS Security & Architecture](/hinkal/hinkal-waas/description/hinkal-approach.md) — enclave security model