> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quantumapi.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Qustody API

> Non-custodial, Fireblocks-compatible custody and orchestration API for the post-quantum blockchain

Build on a **post-quantum secure** blockchain with an API you already know. The Qustody API provides a Fireblocks-like operating model: multi-tenant vault management, policy-enforced transactions, and webhook-driven event delivery, all powered by quantum-safe signatures.

## Get started

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Create your first vault, register a wallet, and submit a transaction in minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Set up API credentials and secure your integration.
  </Card>

  <Card title="Architecture" icon="diagram-project" href="/architecture">
    Understand the non-custodial signing model and transaction lifecycle.
  </Card>

  <Card title="API reference" icon="terminal" href="/api-reference/introduction">
    Explore all 27 endpoints with request/response examples.
  </Card>
</Columns>

## Key concepts

<Columns cols={2}>
  <Card title="Vaults & wallets" icon="vault" href="/concepts/vaults-wallets">
    Organize addresses into vault accounts with multi-wallet support.
  </Card>

  <Card title="Transactions" icon="arrow-right-arrow-left" href="/concepts/transactions">
    Full lifecycle from creation through signing to on-chain confirmation.
  </Card>

  <Card title="Policies" icon="shield-check" href="/concepts/policies">
    Enforce spending limits, whitelists, and approval workflows.
  </Card>

  <Card title="Webhooks" icon="bell" href="/concepts/webhooks">
    Receive HMAC-signed event notifications for every state change.
  </Card>
</Columns>

## Why Qustody?

* **Post-quantum security.** Quantum-safe signatures protect against quantum computing threats
* **Non-custodial.** Your keys never touch our servers; signing happens via secure callback
* **Fireblocks-compatible.** Familiar operating model for institutional integrators
* **Policy engine.** Configurable rules enforce compliance before transactions are broadcast
* **Webhook delivery.** HMAC-SHA256 signed events with exponential backoff and dead-letter handling