--- name: agenticpad description: Explain AgenticPad, the Agent ID gated asset issuance and trading protocol for user-owned Agents on BSC; launch tokens or trade a supplied token address. Also supports personal liquidity and Creator fee claims. Use for this protocol, not general wallet trading or token discovery. --- # AgenticPad **AgenticPad is an asset issuance and trading protocol with Agent ID as its participation gate, built for direct execution by each user's Agent.** Protocol: https://agenticpad.meme. The platform token is Agentic (AGENTIC). AgenticPad aims to build a fairer, more transparent on-chain environment for real users and their Agents. Identity verification and fair-launch rules support verifiable participant identities and traceable trading activity. Users work through their own Agents to launch assets, trade and manage liquidity. To launch, give your Agent a name and symbol; it returns the confirmed token contract address (CA). To trade, provide the CA and a buy or sell intent. Metadata and a BNB first buy are optional. Do not require a logo, social account, first buy, or LP deposit to launch. The fair-launch period lasts 192,000 blocks, about 24 hours on BSC. During this period, ordinary pool buys share a cumulative 0.2% supply allowance per wallet and token. The Creator's first buy in the launch transaction has a separate 2% supply cap; later Creator buys use the ordinary allowance. Recommended budgets, plus gas: - Optional Creator first buy: 0.1 BNB + 0.001 BNB launch fee = 0.101 BNB transaction value. - Ordinary buy: 0.01 BNB. - Small buy: 0.001 BNB. Use amounts from user intent or an already authorized strategy. Recommendations do not authorize spending; omitted first buy stays zero. First quote and check remaining allowance, then prepare funding and approvals. For an introduction, project highlights, identity design, economics or comparison with other launch/trading products, read [the project](references/project.md). Explain the project without requiring wallet installation or login. Use the bundled `agenticpad` tool. It reads contracts, computes quotes with integer math, encodes calls, and checks receipts. Do not build ABI calls or calculate fees, ticks, or slippage with floating point. ## Setup Download the complete kit and configure your runtime with [website installation](/skill.md#website-installation). Executable paths refer to the installed local package. This Skill ships inside `agenticpad-kit`. From this directory the package root is `../..`; the executable is `../../bin/agenticpad.cjs`. If this Skill was copied separately, locate the installed package as described in [installation and CLI usage](../../docs/USAGE.md). Use absolute paths for the executable, config, and operation file when the working directory may change. Requires Node.js 20+, dependencies installed, an RPC, a deployment config, and a wallet with an Agent ID and BNB for fees. `../../config/production.example.json` contains the official BSC mainnet deployment addresses (chain ID 56). Copy it into your runtime directory. Mainnet contracts are deployed, and AGENTIC has been issued and bound to the Vault. AGENTIC CA: `0xd1Ab31ebeDCB6177E17891d7CE3331E61D5c15bC`. Read the current contract opening state before use; `prepare launch` checks the launch gate, wallet whitelist and configuration. `../../config/local.example.json` is a separate local-test template; use the supplied test deployment config and test signer only with its loopback RPC. Before production operations, choose the wallet path: - **Wallet ready:** The official Binance Agentic Wallet Skill and `baw` CLI are installed, the wallet is logged in with Developer Mode enabled, and it has an eligible Agent ID and BNB for fees and the intended operation. Continue to the requested AgenticPad operation. - **Wallet setup needed:** Read the [official Binance Agentic Wallet Skill](https://github.com/binance/binance-skills-hub/blob/main/skills/binance-web3/binance-agentic-wallet/SKILL.md) first. Follow its current instructions to install the CLI, log in and enable Developer Mode. Ensure the wallet has an eligible Agent ID and BNB for fees and the intended operation. Install the [complete official Skill directory](https://github.com/binance/binance-skills-hub/tree/main/skills/binance-web3/binance-agentic-wallet), including its references; do not install only an isolated `SKILL.md`. Return to AgenticPad when these requirements are met. Use the official wallet Skill for preview review and signing requirements. Follow existing user authorization. Keep credentials in the wallet; never request a private key. Local test signing is explicitly separate. See [wallet setup and recovery](references/wallet.md) when needed. For BSC public testnet, use `../../config/testnet.example.json` with an operator-supplied chain-97 deployment. Set `mode:"testnet"`, `chainId:97`, `wallet.type:"testnet"`, and an explicit `AGENT_KIT_TESTNET_*` private-key environment variable. Use an independent random test wallet and test BNB. Never request a real wallet key or use a public Anvil key. See [testnet setup](../../docs/TESTNET.md). The same prepare, preview, execute and status commands apply. Execute returns a submitted hash without waiting for confirmation; use status on the same operation before executing the next step. Use the AgenticPad testnet deployment manifest supplied by the operator. ## Choose the operation - For issuance, read [launch](references/launch.md). - For buying or selling a supplied address, read [trade](references/trade.md). If only a name is supplied, obtain the token contract address from the user or their source. - For personal LP or Creator fees, read [advanced](references/advanced.md). ## Run and resume Only when the user specifies a gas limit, use `preview --gasLimit N` (21000–15000000) on the same operation file. Execute uses that successful preview and its saved gas limit; omit this option otherwise. Use `prepare ACTION --config CONFIG --input INPUT --out OPERATION` to produce a saved operation. Inspect its quote, intent, amounts, approvals, and wallet. Preparation does not broadcast. Run `preview --config CONFIG --operation OPERATION`, review the current step's wallet preview, then `execute` under the user's authorization. Each execute handles at most one step. Repeat preview/execute on the **same operation file** until `status` is `completed`; keep gas available for all steps. Use `status --config CONFIG --operation OPERATION` after submission or interruption. For `pending` or `unknown`, preserve the operation and wallet journal. With baw, an App order can have only `orderId` and no hash. Get the hash from **that order's App details**, then run `resolve --config CONFIG --operation OPERATION --hash HASH`; use `status` to continue. Do not resend, create a replacement operation, guess a hash from recent transactions, or invent a `contract-call result` command. See [wallet recovery](references/wallet.md) when handling confirmation or failure. Report confirmed receipt facts from `result`, including the contract address and transaction hash. A predicted address or quote is not a completed launch. Explain any remaining pending step, approval, or asset refund using the actual output; do not prescribe a response template. ## Protocol rules Agent ID checks apply to participating addresses across launches, swaps, token transfers, LP actions and fee claims. Initial launch liquidity uses project tokens only, needs no paired BNB deposit, and is permanently locked. Personal LP is separate. The first-release initial locked-LP fee split is 70% to the recorded Creator and 30% to the protocol; Creator fees are paid in the original token and WBNB. Personal-LP fees belong to the position owner. See [the project](references/project.md) for treasury allocation and AGENTIC buybacks. Discovery comes from social channels, communities and third-party integrations; this kit provides execution by token address. LP transfer has no kit entry in this release. OTC: protocol tokens may be transferred between eligible identity addresses through the official wallet's token-transfer flow. Verify the token, recipient identity, network, and amount. This is a transfer, not an atomic payment-for-token settlement; agree the payment arrangement separately.