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

# When to use AIR Kit

> Decide whether AIR Kit fits your use case — when AIR Account login and verifiable credentials are a good fit, and when another approach works better.

AIR Kit has two main parts you can adopt separately: **AIR Account** for login and wallets, and **AIR Credentials** for issuing and verifying claims about users. Use this page to check whether each one fits.

## AIR Account

**A good fit when you want to:**

* Let users sign in with Google or email and get a wallet, without installing anything or managing a seed phrase.
* Share one account with other apps in the AIR ecosystem, so returning users don't sign up again.
* Add a wallet to an app that already has its own login, by passing your users in with [Custom Auth](/get-started/authentication/custom-auth).

**Consider another approach when:**

* You need full control over the identity provider, account recovery, and user database, and don't want users to have a shared account across apps.
* Your users must sign in only with their own external wallet. Wallet login is available as an add-on, not by default. See [EOA wallet authentication](/get-started/authentication/login#eoa-wallet-authentication-optional-add-on).

## AIR Credentials

**A good fit when you want to:**

* Let users prove something about themselves, such as a KYC result, membership tier, or age, without sending you the underlying documents.
* Reuse a check another issuer has already done, so users don't repeat KYC or onboarding for every app.
* Issue claims from your own data that users can present to partners, with no direct API integration between you and each partner.
* Receive only the fields you need, so you store less personal data.

**Consider another approach when:**

* The data changes faster than you can reissue credentials, such as a live account balance. Query it directly from the source instead.
* You need predicate checks, such as "older than 18" without revealing the birth date, or on-chain verification. These need [Iden3 credentials](/products/identity/iden3-credentials), which the AIR team enables on request.
* The check depends on a person reviewing documents or images. Do that review in your own flow, then issue a credential with the result.

## Next steps

* [What is AIR Kit?](/get-started/what-is-airkit)
* [Credential formats](/products/identity/credential-formats) to compare SD-JWT and Iden3 credentials
* [Login quickstart](/get-started/quickstarts/login)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.