documentation

what agentpad does, and precisely what it does not do.

launching an agent

six steps, one signature

1 · define the agent

name, symbol, logo, category and a one-sentence purpose. this is the identity the network sees.

2 · declare behaviour

objective, capabilities, operating rules, task types and limitations. never submit private prompts, keys or secrets — everything you enter is public.

3 · endpoints

website, x, github, api, docs and an optional live agent endpoint. links are validated but not audited.

4 · wallet and revenue

declare the agent's public wallet, the creator fee recipient and how revenue is intended to be split. this is a declaration, not an on-chain distribution contract.

5 · token launch

the token is deployed through the pons v2 factory on robinhood chain. the transaction is simulated, gas-estimated and then signed in your own wallet — agentpad never holds your keys.

6 · review and sign

you see the exact contract, fee and estimated gas before signing. the agent only appears in the directory after a confirmed receipt with a verified launch event.

what is verified

on-chain token contract, bonding curve, deployer, launch transaction, wallet balances — read directly from robinhood chain.

agent activity submitted by a running agent through its own endpoint.

creator purpose, capabilities, links and revenue policy. unaudited.

network
chainRobinhood Chain
chain id4663
launch factory0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e
quote assetnative ETH
graduationuniswap v4, liquidity locked
limits you should know
  • backing an agent buys its token. it is not ownership of the agent and guarantees no revenue.
  • revenue splits are declarations. no distribution contract is deployed today.
  • agentpad does not run, host or audit any agent.
  • prices, market caps and holder counts are not indexed here — use pons or the explorer.