# Agent Genesis Waitlist

- Network: BNB Smart Chain (56).
- Contract: 0xA8E0E79868Ef9Fd074b6d00A7E459708428a1e53
- Asset: United Stables (U), 0xcE24439F2D9C6a2289F741120FE202248B666666. Amount: 0 U. No U balance or approval is required.
- Binance Agentic Wallet and a .ai Agent ID are required. The participant pays the BNB network fee.

Use the EIP-712 flow below. The built-in x402-payment command rejects zero amounts; this integration uses Binance signing and the official x402 SDK.

1. Confirm the connected wallet and Agent ID. Check wallet settings: Developer Mode must be enabled and unexpired.
2. GET https://agx402.xyz/api/genesis/waitlist?identity=YOUR_WALLET. Continue only if status is READY and registrationOpen is true. If wallet.registered is true, report the existing registration and continue to Step 2 on the website.
3. GET https://agx402.xyz/api/genesis/waitlist/x402?wallet=YOUR_WALLET. Read the HTTP 402 response. Its registration.messageRequest is the exact EIP-712 request for Binance sign-message preview (--binanceChainId 56 --signType EIP712 --message JSON_REQUEST --json). Preview it and show the parsed terms and risks. Sign only after explicit user confirmation; do not execute a failed preview.
4. Obtain the 65-byte, 0x-prefixed r+s+v signature. If Binance returns a 64-byte signature and a separate signatureRecovery byte, combine them once. Insert the signature into registration.paymentPayload.payload.signature. Base64-encode the complete paymentPayload JSON as PAYMENT-SIGNATURE. Retry GET https://agx402.xyz/api/genesis/waitlist/x402 with that header. Keep the same signed payload for confirmation.
5. On HTTP 202 with status AWAITING_TRANSACTION, preview the exact returned transaction using Binance contract-call preview. Match chain 56, your wallet, this contract and zero native value. Show the simulation and BNB network fee; execute only after explicit user confirmation. Send exactly once.
6. GET https://agx402.xyz/api/genesis/waitlist/x402?transaction=TX_HASH with the same PAYMENT-SIGNATURE header. For AWAITING_CONFIRMATIONS, check the same hash every 3 seconds. For HTTP 429 or 503, respect Retry-After. Do not resend the transaction. Success requires HTTP 200, status REGISTERED and PAYMENT-RESPONSE after 12 confirmations.
7. Report the registration receipt and complete Step 2 at https://agx402.xyz/waitlist. Social submission uses a separate off-chain confirmation, with no additional transaction.

The contract settles the authorization and records the wallet and Agent ID in one atomic transaction. Do not substitute a direct token or BNB transfer; it does not register a wallet. Stop if the returned terms differ. Never report success from a signature or broadcast alone.

One entry per wallet and Agent ID. Registration does not guarantee a mint allocation.