How to verify Agent ID sign-in
ATLAS uses the official Binance Agentic Wallet CLI (baw) for first-time Agent ID verification and passkeys for returning users. Here is what to run, what to check, and what every error means.
The wizard generates exact preview → execute → result commands from your own live challenge. You run them; ATLAS never does.
If signing fails (e.g. Agentic Wallet bug #400 / 953004), send one registerIdentity transaction to the ATLAS Identity Registry on BSC instead. If the API ever reports the contracts as not deployed, this step is disabled, never faked.
After verifying, add a passkey for one-tap social sign-in. Wallet proof is still required for anything financial.
With a real Agent ID (about 5 minutes)
- Install the CLI:
npm i -g @binance/agentic-wallet, and connect it to your own wallet (baw wallet status --json). - Check
baw wallet agent-id --jsonshowsclaimed: true, and Developer Mode is on (baw wallet settings --json). - Open /onboarding, enter your wallet, pick your shell (macOS/Linux, PowerShell 7+, or Command Prompt).
- Copy the preview command. In its output, check domain ATLAS Social, your wallet, the ATLAS audience, a loginId matching the page, and no Permit/spender/amounts. Paste the output back.
- Copy the generated execute command (it now contains your requestId). Approve in the Binance App if asked, run the result command, paste the output. The signature fills in automatically.
- Press Verify signature. Expect "Agent ID verified" and an offer to add a passkey.
- Optional negatives: wait for the countdown to hit 0 (commands go stale, verify is refused), or paste an old signature (refused).
Without an Agent ID (about 2 minutes)
- On /onboarding, enter any wallet without an Agent ID. ATLAS checks the official registry live and refuses it with
NOT_AGENT_ID_HOLDER. No account is created. - Read the error catalog the UI uses: /api/auth/errors. Every code has a message, a fix and a next action.
- Check honesty about contracts: /api/config shows
contractsDeployed. When it is true the on-chain path uses the verified BSC contracts; if it were false, the on-chain path would be disabled with no fake success. - Browse the API contract at
/docson the API host (OpenAPI), and the tests in the public repo (apps/api/test/onboarding.test.ts,packages/auth/test/onboarding.test.ts,tests/e2e/onboarding.spec.ts).
What counts toward "30 Agent ID addresses interacting"
Only on-chain transactions from an Agent ID holder to an ATLAS contract: registerIdentity (the fallback, or the Home "Anchor your Agent ID" card), publishing a thesis or review. A signature-only login is not an on-chain interaction, and ATLAS doesn't present it as one.
Security controls (unchanged by the wizard)
Domain "ATLAS Social", primaryType AtlasLogin, chain-bound. The statement says it authorizes no transaction, transfer or approval.
The message carries the ATLAS origin (audience). A signature made for a phishing site is rejected here.
32 random bytes per challenge, stored server-side. Replays return ALREADY_USED.
Visible countdown. Expired or regenerated challenges are marked stale and refused by the API.
A rejected signature can't be retried against the same challenge.
ecrecover for normal wallets; ERC-1271/6492 for smart-contract wallets.
Ownership is read from the official Agent ID registry on BSC (0x60b92624…) at challenge and at verify time.
A second wallet presenting the same Agent ID, or a wallet linked to another Agent ID, is refused.
20 sign-in attempts per minute per address.
Sign-in is a signature from your own wallet CLI. Nothing on ATLAS asks for a seed phrase, key, QR or pairing code.
Financial and on-chain actions always need a fresh wallet proof (10 minutes).
Every error, explained
The same catalog drives the wizard, so what you see here is what users see. Codes marked → on-chain send the user to the guided registerIdentity fallback.
| Code | What it means | Fix |
|---|---|---|
EXPIRED | Challenge expired Each ATLAS challenge is valid for 5 minutes and this one ran out. That protects you if a signature leaks later. | Generate a new challenge and run the new commands. Commands from the old challenge will not work. |
ALREADY_USED | Challenge already used This challenge was already used or burned by a rejected attempt. Every challenge works exactly once, so a copied signature can never be replayed. | Generate a new challenge and sign the new commands. |
CHALLENGE_SUPERSEDED | Old commands You generated a newer challenge, so these commands were invalidated. | Use the commands shown now (the newest challenge). |
CHALLENGE_NOT_FOUND | Unknown challenge The server does not know this challenge. It may be from another device, tab or deployment. | Generate a new challenge on this page. |
CHALLENGE_CONTEXT_MISMATCH | Challenge belongs to another session This proof was started in a different session. | Start the verification again from this tab. |
AUDIENCE_MISMATCH | Wrong website The challenge was issued for a different ATLAS address. A signature made for another site is useless here, which is what protects you from phishing. | Open ATLAS at its real address and start again. |
CHAIN_MISMATCH | Chain mismatch The challenge was signed for a different chain than ATLAS uses (BNB Smart Chain, chain 56 in production). | Run the commands exactly as generated. Do not change --binanceChainId. |
SIGNATURE_REQUIRED | No signature Nothing was pasted in the signature field. | Paste the full signature value from baw sign-message execute or result. |
SIGNATURE_TRUNCATED | Signature looks cut off A signature is 64 or 65 bytes (128 or 130 hex characters). What you pasted is shorter, which usually means the terminal wrapped or truncated it. | Copy the whole signature value again. Using --json output and copying the quoted value avoids line wraps. |
MALFORMED_SIGNATURE | Signature isn't valid hex The signature must be hexadecimal (0-9, a-f), optionally starting with 0x, with no spaces or quotes. | Paste only the signature value, without quotes, spaces or line breaks. |
BAD_RECOVERY | Recovery value looks wrong The recovery value must be 00, 01, 1b or 1c (from signatureRecovery). | Paste signatureRecovery exactly, or leave it empty and ATLAS will try both. |
SIGNER_MISMATCH | Signature doesn't match this wallet The signature is valid, but it was not made by the wallet you entered for this exact challenge. Usually baw is signed in to a different wallet, or the commands came from an older challenge. | Check baw wallet address --json matches the wallet above, then sign the current commands. Rejected attempts burn the challenge, so you'll get new commands. |
BAD_SIGNATURE | Signature rejected The signature does not prove ownership of this wallet for this challenge. | Sign the current commands with the wallet that holds your Agent ID. |
ERC1271_REJECTED→ on-chain | Smart-wallet check failed This wallet is a smart contract and it did not approve the signature (ERC-1271). | Use the on-chain proof instead: one registerIdentity transaction from the same wallet. |
WALLET_MISMATCH | Proof came from another wallet The on-chain proof was sent from a different wallet than the one you entered. | Send registerIdentity from the wallet that holds your Agent ID. |
NOT_AGENT_ID_HOLDER | No Agent ID on this wallet ATLAS checked the official Agent ID registry live and this wallet does not hold an Agent ID. | Claim one in the Binance App (Web3 wallet → Agent ID), then enter the wallet that holds it. baw wallet agent-id --json shows whether you have one. |
AGENT_ID_NOT_HELD | Agent ID no longer held This wallet no longer holds the Agent ID linked to your account. | Use the wallet that holds the linked Agent ID. |
AGENT_ID_ALREADY_REGISTERED | Already registered This Agent ID or wallet already belongs to an ATLAS account. One Agent ID maps to exactly one account. | Sign in with that account, or use its passkey. |
WALLET_CHANGED | Agent ID linked to another wallet This Agent ID is already linked to a different wallet. ATLAS never silently replaces the verified wallet. | Sign in with the originally linked wallet, or contact support to re-verify. |
IDENTITY_MISMATCH | Wallet linked to another Agent ID This wallet is already linked to a different Agent ID. | Sign in with the Agent ID that is linked to this wallet. |
AGENT_ID_REVOKED | Association revoked This Agent ID's association with ATLAS was revoked. | Contact support to re-verify. |
ACCOUNT_SUSPENDED | Account suspended This account is suspended. | Contact support. |
ACCOUNT_UNAVAILABLE | Account unavailable The account linked to this passkey is unavailable. | Sign in with your Agent ID wallet instead. |
CONTRACTS_PENDING | Contracts pending deployment The ATLAS registries are not deployed on this chain yet, so the on-chain proof cannot run. Nothing was sent or recorded. | Use the signature path for now. The on-chain proof opens once the contracts are deployed and verified. |
PROOF_PENDING | Transaction not found yet ATLAS could not find your registerIdentity transaction on-chain yet. It may still be confirming. | Wait about 10 seconds for confirmation, then press verify again. |
RATE_LIMITED | Too many attempts Sign-in endpoints allow 20 attempts per minute per network address. | Wait a minute, then try again. |
BAD_ORIGIN | Blocked cross-site request The request came from a page that isn't ATLAS. | Open ATLAS directly and try again. |
VALIDATION | Invalid input Something in the request wasn't in the expected format. | Check the wallet address (0x + 40 hex characters) and the pasted values. |
NETWORK | Can't reach ATLAS The ATLAS API didn't answer. On the free tier it sleeps when idle and takes 30–60 seconds to wake. | Wait a moment and retry. |
PASSKEY_UNKNOWN | Passkey not recognised This passkey isn't registered on ATLAS (it may have been removed or made on another site). | Sign in with your Agent ID wallet, then add a new passkey in Settings → Security. |
PASSKEY_REJECTED | Passkey check failed Your device's passkey response couldn't be verified. | Try again, or sign in with your Agent ID wallet. |
PASSKEY_CANCELLED | Passkey cancelled The passkey prompt was closed or timed out. | Try again. If this device has no ATLAS passkey, sign in with your Agent ID wallet. |
CHALLENGE_INVALID | Passkey challenge expired The passkey prompt took longer than 5 minutes or was already used. | Start the passkey sign-in again. |
STEP_UP_REQUIRED | Fresh wallet proof needed Adding a passkey needs a wallet proof from the last 10 minutes. | Verify with your Agent ID wallet again, then add the passkey. |
BAW_953004→ on-chain | Known Agentic Wallet bug (#400, error 953004) baw sign-message preview fails with 953004 for some EIP-712 logins. This is a known issue in the Agentic Wallet, not something you did wrong. | Use the on-chain proof: one registerIdentity transaction from your wallet (no value, no approval). It also counts as an on-chain ATLAS interaction. |
BAW_DEV_MODE_OFF | Developer Mode is off or expired External signing needs Developer Mode, which lasts 7 days (error 351802 when expired). | Binance App → Agentic Wallet → Settings → Developer Mode → accept the risk warning. Then re-run baw wallet settings --json. |
BAW_DEV_MODE_BALANCE_CAP | Balance above the Developer Mode cap Developer Mode can't be enabled while the wallet balance is over its cap (351804). | Move funds below the cap in the Binance App, then enable Developer Mode. |
BAW_RISK_BLOCKED | Blocked by wallet risk checks The Agentic Wallet intercepted this request as risky (351803). ATLAS offers no way around it, by design. | Do not execute. Check you're on the real ATLAS site and the preview shows ATLAS Social. Report it to us. |
BAW_PREVIEW_EXPIRED | Wallet preview expired baw's preview cache expired before execute ran. | Run the preview command again, then execute with the new requestId. |
BAW_NOT_SIGNED_IN | baw isn't signed in The CLI isn't connected to your wallet. | Run baw auth signin and finish Binance's own sign-in in your Binance App, then check baw wallet status --json. |
BAW_SIGN_REJECTED | Signature request rejected The request was rejected or expired in the Binance App, so no signature exists. | Run the preview again with a fresh challenge. |
BAW_PENDING | Waiting for approval in the Binance App The signature needs your approval in the Binance App. | Approve it in the App, then run the result command shown here. |
BAW_SIMULATION_FAILED | Wallet simulation failed The wallet's simulation of the transaction failed (351805). | Read the message in the output. For registerIdentity it usually means the commitment was already used: generate a new challenge. |
BAW_AGENT_ID_SERVICE | Agent ID service unavailable The Agent ID backend is temporarily unavailable (20003008). This doesn't mean you lack an Agent ID. | Try again in a minute. |
STALE_PREVIEW | Preview is for an old challenge This preview output belongs to an older challenge (different loginId), so its signature would be rejected. | Run the preview command shown now. |
WRONG_MESSAGE | Preview isn't an ATLAS login The parsed message isn't the ATLAS Social login (domain, wallet or type differs). Do not execute it. | Copy the preview command from this page again, unchanged. |
BAW_UNKNOWN_ERROR→ on-chain | baw returned an error The Agentic Wallet returned an error ATLAS doesn't recognise. | Read the error message. If signing keeps failing, use the on-chain proof. |