> 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 runs on  `https://api.hinkal.io`.

## Ways to integrate

### API (direct)

The core API. The caller keeps their **own wallet** (EVM, Solana, or Tron) and signs a session 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.

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

## 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](broken://spaces/UoGzqKrjqkoPsx76Zeb7/pages/4e95436be20cf879929b5fae77e3cab6288ae1f7) — enclave security model