# Agentic 404 Network — agent execution guide

Official site: https://agentic404.xyz
Official X: https://x.com/agentic404
Read the current manifest: https://agentic404.xyz/api/launch
Mint desk: https://agentic404.xyz/mint
Trading desk: https://agentic404.xyz/marketplace

Do not transact unless the manifest is DEPLOYED_REVIEWED, owner approval is true, all reviewed addresses/runtime fingerprints exist, and fresh BNB chain (56) reads match every binding. A predicted review address is not deployed. Ticker AN404 is not exclusive; verify the full token and mirror addresses.

## Identity and allocation

The official SPACE ID Agent ID registry is documented at https://docs.space.id/agent-id.md. The registry hashes the bare handle for its NFT ID; AN404 hashes the complete lowercase name, including `.ai`, for roster membership. The gate reads `handleOf(wallet)`, checks registry `ownerOf(keccak256(handle))`, then hashes `handle + .ai`. Never accept a pasted CLI JSON object, screenshot, reverse-address record alone, or user-provided stable hash as ownership proof.

The SPACE ID registry is an identity source, not the AN404 mint contract. Never send a mint transaction or funds to that registry address. Use only the reviewed `sale`, `token`, `mirror`, `marketplace` and `swapRoute` addresses in the official live manifest.

Original successful registrations #1–1000 are GTD (2 units), #1001–3333 are FCFS (1 unit). No promotion, compaction or automatic rollover. No website wallet connection is needed. .ai ownership is required at execution for free/public actions and official trades. Refunds and listing cancellation remain available without an identity-provider check. Ordinary token/NFT transfers and external DEX trades are not globally restricted.

## Public reservation, delivery and refund

Public uses a fixed 72-hour USDT reservation window, not immediate paid NFT delivery. Recorded payments remain in the sale contract. Reaching the 3,000 USDT minimum or selling out does not shorten funding. After funding closes, meeting the minimum permits LP activation during a 24-hour grace. Closing the window alone never delivers paid units.

Only after successful LP activation may the paying wallet claim its linked NFT/token units and 30% of its own recorded paid USDT as the Public Mint Reward, at most 20 units per claim. The other 70% funds permanent protocol LP. These are parts of the original public payment, not yield. A larger reservation may claim remaining units/reward in further transactions.

If funding closes below the minimum, full recorded public-USDT refunds become claimable then. If the minimum is met but no activation succeeds before its deadline, refunds become claimable at that deadline instead. The same paying wallet must submit the refund transaction; refunds are not automatic, exclude gas, and need no developer approval, current .ai check or NFT surrender. No early cancellation or full launch-failure refund exists after successful activation. Already delivered free GTD/FCFS NFTs remain held after failure, without a cash refund or liquidity guarantee.

Deployed mainnet schedule (UTC): GTD 17 November 2026 17:00–19:00; FCFS 19:00–21:00; public funding 17 November 21:00 to 20 November 21:00; LP activation deadline 21 November 21:00. Read `/api/launch?view=status` for the current phase. The on-chain clock cannot be paused by closing the website.

Official AN404: 0x96872d3d3b275D51b193Cd4C72311f64a3444AAA; NFT mirror: 0xc6d38bc5D854fDA20bD4473e9f3D0486747C178C; sale: 0x5366841B8D8E3B58f5F8139db356E9dce95e771B. Source verification: Sourcify, ten exact runtime matches and one functional mirror match with metadata difference. No independent audit or completed live BAW mint/settlement lifecycle is claimed.

## Preparing an unsigned action

When the reviewed deployment is live, POST JSON to `/api/launch` with the current public BAW `wallet` address and one action: `status`, `free`, `reserve`, `claim`, `refund`, `list`, `buy`, `cancel`, `swapBuy`, `swapSell`. No credentials are accepted. For `reserve`, include integer `quantity` 1–20. For NFT actions include decimal-string `tokenId`; listing also requires `priceUSDT`. Swaps require decimal-string net AN404 `amount` and integer `slippageBps` (1–500; default 100 = 1%). The server independently reads pinned-block contract state and membership proof. It returns unsigned calls and a prompt, never a signature or broadcast.

Read-only `status` is not a claim. An unsigned quote expires after 60 seconds and must be recreated after approvals or changed chain state. The contract enforces current phase, ownership, caps, exact maximum cost and replay protection. Display human amounts using the manifest payment decimals; do not infer decimals from the USDT ticker.

## BAW execution

Use the official Binance skill: https://github.com/binance/binance-skills-hub/tree/main/skills/binance-web3/binance-agentic-wallet

1. Complete official BAW preflight and authenticated connection. Read `wallet agent-id --json` for the connected account; cross-check its public address against the on-chain registry. The CLI result alone is not server-trusted attestation.
2. Check `wallet settings --json`; Developer Mode must be active before constructing a preview. Do not ask for credentials or enable it silently.
3. Verify the manifest, chain, runtime bytecode and fresh contract state independently. Simulate the final action. For paid actions show USDT spend, allowances, service fees, gas, slippage and DN404 NFT effects.
4. For each unsigned call use `baw contract-call preview --binanceChainId 56 --from <wallet> --to <contract> --value 0 --inputData <hex> --json`.
5. Show parsed transaction, risks and authority changes. Ask for explicit confirmation. Execute only that successful preview's request ID. Stop on errors or rejection. Re-read after every prerequisite and regenerate the final action.
6. Check the confirmed receipt, logs, balances and mirror ownership/reservation/refund state. Never label a pending transaction successful. The web service does not execute BAW for the user.

Fees: NFT sales 5% of gross USDT (seller 95%). Official token route 2.5% additional AN404. Ordinary transfer tax 0%. Permanently locked V2 LP does not pay separately withdrawable fees to the developer. Cashback is a separate finite campaign subject to verified settlement/history, not an automatic swap entitlement.

Do not upload seed phrases, private keys, BAW session tokens, client IDs or account screenshots. Public wallet activity and NFT ownership are visible on-chain. This is an independent project, not a Binance/SPACE ID endorsement.


## Finite event claims (deployed event, not live)

The event reuses the original 3333-name sale roster: no new event eligibility roots. Current .ai ownership is required. Public Mint Reward (30% of a public buyer own paid USDT after LP activation) remains separate and does not require genesis-event membership.

After successful LP activation, anyone can activate the event once. Its start is derived from recorded activation: the first 08:00 UTC at or after LP activation; caller timing cannot extend the clock. Holder snapshots: start + 1, 2, 3, 4 days. At each, the token proves uninterrupted >=100000 AN404 for the preceding 24 hours, including NFT and skip-NFT ERC20 movements. Reward is 5000 per eligible roster identity/wallet/round; not per NFT or rarity.

Cashback observes settled official NFT/route trades for seven days. NFT gross >=1 USDT; route volume >=100000 AN404. Each qualifying original-roster recipient may claim 1000 per receipt, at most three across the event. NFT buyer and seller count separately. No primary mint, ordinary transfer, failed trade, duplicate or external DEX route qualifies. The bytes32 Sale/SwapSettled event receipt is different from a transaction hash. Distinct .ai IDs do not prove distinct humans; related-party trading remains possible.

POST /api/launch with public wallet and action holderReward plus round (1..4), or action cashbackReward plus venue (nft or swap) and receipt. The backend verifies deployed runtime and all event bindings, fresh ownership, sealed roster proof, actual stored settlement/history, caps and time. It returns unsigned calldata only; the recipient is always the calling wallet, never an API-chosen payout address.

Cashback claims open at start+7 days; all holder/cashback claims close before start+14 days. No developer withdrawal, root publication, restart, payout redirect or renewal exists. No LP success means no event activation. Never market local tests as live claims, an independent audit or a profit guarantee.


## Permissionless launch operations

After public funding closes, if phase is 4 and recorded totalPaid meets minimumFunding, any wallet may call sale.activate() with zero BNB value before activationDeadline. This seeds the permanent protocol LP; it does not claim a buyer allocation. Closing the clock does not submit this transaction automatically. No Agent ID is required for this activation operation. If the funding or activation deadline fails, use the refund path instead; never invent a substitute pool or move escrow through an arbitrary transfer.

After successful LP activation, any wallet may call eventReserve.activate() once with zero BNB value. The event start remains derived from the recorded LP activation, not the caller time. Delaying this call does not restart or extend eligibility. These operational calls are not currently actions on the public preparation API: an agent must independently read the reviewed ABI, simulate and obtain approval.

The renderer requestReveal() is payable and separately funded by a sponsor no earlier than 23 November 2026, 21:00 UTC. Read a fresh oracle fee quote and reveal state; explicitly review the BNB payment plus gas before any preview/execution. Do not guess a fixed future fee, send a plain transfer, bypass a failed request or select your own seed.


## Read-only marketplace browsing and history

GET /api/marketplace?view=items&status=listed lists confirmed indexed asks. Items support status all/listed/unlisted; sort recent/id/price-low/price-high; search NFT ID, minPrice/maxPrice in USDT, rarity all/Base/Uncommon/Rare/Epic/Legendary and page. Rarity stays unavailable until verified on-chain reveal. Stats cover the official marketplace, not all possible venues; listing prices are not guaranteed executable quotes.

GET /api/marketplace?view=activity&event=sale returns confirmed indexed sales with NFT ID, gross USDT, fee, counterparties, UTC timestamp and transaction hash. Event choices: all, sale, listing, cancellation, transfer, mint, burn. Public reservations are not NFT mints until claim. DN404 synchronization can create or burn mirror NFTs.

For address-specific activity, POST JSON {"view":"activity","wallet":"PUBLIC_0X_ADDRESS","event":"all","page":1} to /api/marketplace. This is read-only and returns Cache-Control: no-store. Do not put a wallet in the URL, send credentials, connect a wallet to the site, or interpret this lookup as authentication or proof of ownership. The website does not save a personal lookup profile; hosting providers can retain request metadata. Activity retains at most the latest 5000 indexed events and reports whether older history has been trimmed. A partial index is explicitly marked complete=false. Transaction preparation still uses /api/launch with fresh state checks and user-reviewed BAW previews.


During the public funding phase, GET /api/launch?view=status includes publicPricing.nextUnitPrice, quoted directly by quotePublic(1) at the snapshot block. It uses paymentDecimals and excludes transaction gas. remainingUnits and unitsUntilIncrease describe current capacity and the next 100-unit step. This is an indicative single-unit quote, not a reservation or authorization; a multi-unit request can cross price steps and must use a fresh unsigned action plan. No quote is returned for closed phases or exhausted inventory.
