Four modules
Every module builds on the same AIR Account, so a user who signs in once can hold credentials, transact, and delegate to agents.
Use only the modules you need. Identity does not require Money, and an agent binding never grants wallet authority.
System overview
The SDK manages user interaction and calls AIR APIs. AIR routes issuance requests to the registered issuer service. The issuer service owns authorization, source data, credential creation and signing, encryption, and storage. Credential storage and on-chain proof verification are separate operations. See Account Services for login and wallet details, and Keys & cryptography for every key and token involved.
How each flow works
Credential issuance
Trust setup, SD-JWT construction, holder binding, X25519 + AES-256-GCM envelope encryption, DStorage, and revocation.
Credential verification
Programs, holder-side decryption, selective disclosure, key-binding JWTs, backend checks, and ZK proofs.
Issuance modes
In every mode the issuer builds the SD-JWT, binds it to the holder’s P-256 key (
cnf.jwk), signs it with its did:web key, encrypts it to the holder’s X25519 key, and stores the envelope in DStorage. AIR never sees the plaintext. See How credential issuance works.
Verification at a glance
1
Start verification
The partner app calls
verifyCredential() with a verification program and a backend-generated nonce. The SDK loads the program and ensures the holder is logged in to AIR.2
Find a matching credential
The SDK requests matching credential metadata and DStorage paths. If none exists, verification cannot succeed: pass
redirectUrl to send the user to an accepted issuer, and handle the credential/not-eligible rejection.3
Decrypt and review
The SDK fetches the encrypted credential, decrypts it on the holder’s device, and shows the requested claims.
4
Consent and present
After consent, the SDK attaches only the requested disclosures and signs a key-binding JWT over your nonce and
programId.5
Verify on your backend
The SDK returns the result and Verifiable Presentation. Your backend verifies the SD-JWT and KB-JWT before acting on it.
Off-chain and on-chain verification
The verification program selects the mode. Both paths use the credential discovery, decryption, and consent steps above.
Using DStorage or anchoring issuer state does not, by itself, mean that verification runs on-chain. The verification mode describes where the proof is checked. See How credential verification works.
Account at a glance
The AIR Account is the user’s sign-in and identity account. It holds their DID and credentials, and it is what agents bind to.- Login. Google and passwordless email are on by default. Wallet (EOA) login is available on request, and the wallet address then serves only as a login identifier; account control stays with AIR’s MPC-based account. With Custom Auth, your backend signs a Partner JWT with the user’s email, and AIR creates or loads that user’s account. The first login to your app sends an email one-time code.
- Session.
login()returns a JWT issued by AIR withsub,partnerId, and, once available,abstractAccountAddress. Validate it on your backend against AIR’s published JWKS. Returning users are signed in automatically for up to 30 days unless they log out, or unless you setskipRehydration. - MFA. Passkey MFA is required before any wallet request; AIR Kit prompts for setup automatically if your app has not. By default, the abstract account address appears in user info and the token only after MFA is set up.
Money at a glance
Money separates the AIR Account (who the user is) from the smart account (what holds assets and sends transactions). Smart accounts are ERC-4337 accounts, one per chain, and AIR’s MPC wallet signs for them.- Deployment. A smart account is deployed on first use: AIR Kit bundles deployment with the first transaction, or your app calls
deploySmartAccount(). Deployment gas is sponsored by AIR Kit. - Transactions. Your app uses the standard EIP-1193 provider with existing EVM tooling such as wagmi, or AIR Kit’s built-in wallet screens (beta) for send, receive, swap, and history.
- Gas. For each operation, the paymaster checks the partner’s policy: allowed contracts and function selectors, budgets, per-user limits, a maximum gas cost, and active time windows. If it qualifies, the paymaster signs the sponsorship; otherwise the user pays, optionally in supported ERC-20 tokens. Policy changes currently go through the AIR team.
- Session keys (beta). The user grants a scoped permission once, and your app executes matching actions without a prompt each time. Session keys are a wallet feature, not agent delegation.
- Chains. Base, BSC, Gnosis, Kaia, and Soneium on mainnet, with matching testnets, depending on your partner configuration.
Agents at a glance
An agent backend binds a key to the user’s AIR Account with the user’s consent and a fixed set of scopes. It then mints a 15-minute agent JWT per operation, runs verification programs server-side through the Credential API, and, withcommerce.checkout, mints a checkout token whose audience is a single merchant. Identity binding never grants wallet or payment authority. See How agentic commerce works.
Integrating with existing systems
Your issuer backend can connect to loyalty platforms, KYC providers, ticketing systems, and payment processors. Those systems can trigger Direct Issuance, while the SDK supports user-present issuance, later claims, and verification. See the vertical integration guides for examples.Service independence and login requirements
Choose the service capabilities your app needs. An AIR login is required for the user-present flows below; it does not imply that your app must also integrate wallet operations, gas sponsorship, or other Account Services features.Next steps
Quick Setup
Install and initialize the SDK in minutes.
Solutions by vertical
Business overview and developer guide for Loyalty, Identity, Fintech, Gaming, Ticketing, Telco, and Advertising.
Quickstart: Issue Credentials
Step-by-step credential issuance walkthrough.
Direct Issuance
Issue without an active user session; users claim credentials when they log in.