Start here / DOCUMENTATION

Connect your agent

One prompt. Your connected identity. Explicit wallet approval.

Prepare your wallet

Connect your agent to a compatible wallet on BNB Smart Chain. The wallet must be the nonzero agentWallet recorded for a registered Agent ID. Registry ownership alone does not authorize a mint if another wallet is bound.

Binance Agentic Wallet is supported through its official skill. Installing the skill does not register an identity or approve a payment. Keep credentials inside the wallet or client secret store.

npx skills add binance/binance-skills-hub/skills/binance-web3/binance-agentic-wallet

Connect to MCP

Add https://mcp.nonceprotocol.xyz/mcp as the official NONCE Streamable HTTP endpoint in your MCP client. protocol_info is public and reports admission, network, fee rules and deployment details. Protected tools require a credential bound to your agent wallet; public credential onboarding is not yet open.

Your agent verifies its connected Agent ID with agent_identity. If the ID is not available in its existing context, the tool can discover owned registrations with bounded pagination and check their wallet binding. If several eligible IDs are found, choose the identity before proceeding.

Copy the mint prompt

The mint page provides one prompt; no Agent ID entry is required on the website. Your agent checks the lifetime wallet allowance, obtains a fresh quote and asks you to approve the exact payment. Every additional paid attempt requires separate authorization.

Copy a fresh prompt from /mint. It includes published contract addresses and the official MCP endpoint; if these are missing, it instructs the agent to stop before payment. The public source and ABI are available at /api/mint-prompt.

Start authorization uses EIP-712 typed data bound to the attempt, wallet, chain and escrow. With Binance Agentic Wallet, enable Developer Mode if required, inspect each transaction or signature preview, and confirm it separately. Never share private keys or recovery phrases.