# [Deprecated] Account Kit

> Account Kit (v4) is deprecated. Wallet APIs is the supported successor.

> For the complete documentation index, see [llms.txt](/docs/llms.txt).

Account Kit, including embedded wallets, signer support, and key management (React SDK, embedded UI components, login methods, etc) is deprecated. 

Use [Wallet APIs](/docs/wallets) for all new integrations. Wallet APIs are signer agnostic and allow for sponsored transactions. We recommend using Privy or another provider for signer support alongside Wallet APIs.

## What Alchemy wallets support today

We still run the transaction layer for embedded wallets. Your signer handles login and keys, and [Wallet APIs](/docs/wallets) handle everything after that: [gas sponsorship](/docs/wallets/transactions/sponsor-gas/overview) on EVM and Solana, batched and parallel calls, automatic fee bumps when you [resend a stuck call](/docs/wallets/transactions/retry-transactions), [session keys](/docs/wallets/reference/wallet-apis-session-keys), and [EIP-7702](/docs/wallets/transactions/using-eip-7702) upgrades that turn an existing embedded wallet into a smart wallet without changing its address. Wallet APIs work with [Privy](/docs/wallets/third-party/signers/privy) (recommended), [Turnkey](/docs/wallets/third-party/signers/turnkey), [Openfort](/docs/wallets/third-party/signers/openfort), and any viem-compatible signer through a [custom integration](/docs/wallets/third-party/signers/custom-integration). Signers that can't sign EIP-7702 authorizations, such as Openfort's, use [non-7702 mode](/docs/wallets/transactions/using-eip-7702#how-to-use-non-7702-mode), which creates a separate smart wallet address.

## Support

For migration questions, please see the migration [guide](/docs/wallets/wallet-integrations/privy/signer-migration-overview).

The [Export private key](/docs/wallets/signer/export-private-key) page remains available for ongoing migrations.