For the complete documentation index, see llms.txt. This page is also available as Markdown.

API Integration

The Hinkal API lets you add confidential balances to any application with a few API calls. Users get private deposits, withdrawals, transfers, swaps and more on-chain without running any cryptography, managing custody, or changing the wallets they already use.

Every request is authorized by the user's own wallet. You connect a signer, Hinkal handles the privacy, and users keep full control of their funds throughout.

What you can build

  • Private deposits, withdrawals, transfers, and swaps, with a few API calls

  • No custody, every operation is authorised by the user's own wallet signature

  • Compatible with any wallet that produces a standard signer, including embedded wallets

  • No zero-knowledge cryptography to run or maintain on user side

Embedded Wallets

Embedded-wallet providers give each user a wallet from a familiar login - email, social, or passkey - with no seed phrase to manage. Hinkal works directly with these wallets: because it only needs a standard signer to operate, an embedded wallet can hold a private, shielded balance and transact confidentially with no change to how it is created or secured.

The provider's role stays the same - it issues the wallet, manages keys, and produces signatures. Hinkal uses that signer to open a session and authorize private operations on the user's behalf, without ever taking custody.

Supported providers

Provider
Supported

Privy

Turnkey

Dynamic

DFNS

Last updated