BULLY IS BUILT
FOR AGENTS

The strategy in one page

The shift. AI assistants can now research the web and call tools on a person's behalf. They can read an ordinary web page, but plain files, open protocols and callable tools are far easier for them to read and use reliably. A token that publishes only a human-facing page leaves them to piece things together.

The bet. On the surface this looks simple: a box that checks a contract. Underneath it is purpose-built to make BULLY easy for agents to find, read and use, with the aim of as much exposure to AI as we can earn. That is a positioning choice: be the meme token that agents can actually work with. It is not a promise of reach, traffic, listings or price, and we cannot control what any agent or directory chooses to show.

The business benefit. An agent that can check the official contract and pull the project's own facts has a better source than a copied post. A working public tool gives BULLY a utility that people and other agents can call. The intended potential is that agents, and the people using them, reach the project's own facts instead of copies. Whether that happens depends on what agents and directories choose to do. The tool is free to use and read-only.

The discovery pathway. An agent researching Robinhood Chain can run into BULLY through the files and connection points below, or through a directory entry if a directory lists it. From there it can reach the official contract and this live checker, which reads Robinhood Chain (chain ID 4663). This is a possible path, not a measured one. We have no figures showing agents discovering BULLY this way, and no agent or directory has to surface it.

What agents can use today

• A2A agent. The Crypto Agent is a live agent on the open A2A 1.0 protocol, with an agent card at /.well-known/agent-card.json. Tested with the official A2A JavaScript SDK client (v1.3.0). Other clients are untested.
• MCP server. A read-only MCP endpoint at /mcp with 4 tools: three $BULLY fact tools and check_contract.
• Plain web API. /api/check?address=0x... returns the same contract check as JSON, with no protocol needed.
• llms.txt. A plain-text guide to the site and the official links for language models.
• The official contract, stated everywhere. The same address is in the files above, so an agent that checks any of them gets the same answer.

Where it stands right now

The agent is live and answers on all three connection points. It is listed or recorded in a small number of directories (see the tracked list below), and more submissions are waiting. A submission is not a listing, and no directory has endorsed it or said it fits its criteria. None publishes a usage figure for this agent, so we show none. Usage on our own endpoints is counted from the moment we turned counting on and shown in the live box at the top of this page. It counts calls, not unique agents or people.

What it does not do

It never trades, never touches a wallet and does not give investment advice, a safety verdict or an audit. It reports what the chain shows and says "unknown" when it cannot read something.

The agent runs right here. Try it now.

This box is the agent. It is not a chat character: paste a contract address and it reads Robinhood Chain live and answers. Other AI agents reach the same checker through the connection points further down.

What it is, in plain English

Meme coins copy each other's names all day. The Crypto Agent is a small helper that checks an address instead of a name. You give it one contract address and it looks at Robinhood Chain right now: is there a contract there, what is it called, how much exists, and is it the real $BULLY contract or something else.

It also answers basic questions about $BULLY and sends back the official links. It is a rule-based program, not a chatbot. It does not guess, it does not trade and it never touches a wallet.

The official $BULLY contract

0xff0fa3799686ac47e3aff62aa2210a8441737cc3

Robinhood Chain, chain ID 4663. The same address is on the home page and the press kit. Ask the agent to check it and it will say "Official match: YES".

What it reads on-chain

• Code present? Whether runtime code is returned at the address.
• Token facts. Name, symbol, decimals and total supply.
• Proxy flags. Tests EIP-1967 (implementation, beacon, admin slots), EIP-1822, the legacy OpenZeppelin slot, EIP-1167 minimal proxies and looks for the DELEGATECALL byte. "None found" means none of those matched. Custom upgrade designs can still exist.
• Owner, paused and burn reads. The owner() and paused() calls, whether the owner address has code, and the share of supply sitting at the zero and 0xdEaD addresses.
• Byte-pattern scan. Looks for 4-byte selectors of 34 common mint, pause, blacklist, whitelist, fee, max-transaction, trading-switch, cooldown, ownership and upgrade functions. A hit is not proof the function exists or can be called. It is not an audit.
• Source match. Looks the address up on Sourcify. No match there says nothing about other explorers.
• Uniswap v4 pools, from the chain. Finds v4 pools that contain the token, with full pool IDs (v4 pools live inside the PoolManager contract), fee, hook and the hook permissions encoded in its address, on-chain pool price, and who holds the liquidity position NFTs. Owner type is shown, but a lock is never assumed.
• Buy-then-sell simulation. A read-only simulation at the latest block (no transaction, no wallet) buys 0.0005 ETH of the token and sells it back through the Uniswap router, then reports what came back. One small size, from a synthetic address: it cannot see per-address blacklists or later rule changes.
• Market data, third party. Price, liquidity, pools and holder count from DexScreener and GeckoTerminal. Those figures are not verified by us and can be late, partial or wrong.
• Owner call. Whether the contract answers an owner() call, and with what.
• Copy detector. Compares the bytecode with the official $BULLY contract. Same runtime code at a different address is reported as "same bytecode, not the official contract". Identical code can also be common standard token code, so it is a fact, not a verdict.
• Official match. Exact address comparison with the real $BULLY contract.

Anything it cannot read comes back as "unknown". It says so instead of filling the gap.

Talk to it (for agents and developers)

Open protocol: A2A 1.0 over JSON-RPC. One method, SendMessage, answered straight away with a message.

• Agent card: /.well-known/agent-card.json (also at /agent.json)
• Endpoint: POST https://abullycoin.com/a2a
• Tested with the official A2A JavaScript SDK client (v1.3.0). Other clients are untested.
• Read-only MCP endpoint: POST https://abullycoin.com/mcp (4 tools: three $BULLY fact tools and check_contract).
• Plain web call, no protocol needed: /api/check?address=0x... returns the same contract check as JSON.

{"jsonrpc":"2.0","id":1,"method":"SendMessage","params":{"message":{"messageId":"1","role":"ROLE_USER","parts":[{"text":"0xff0fa3799686ac47e3aff62aa2210a8441737cc3"}]}}}

Where the Crypto Agent is listed

This is a tracked list of directories that carry, or may carry, the Crypto Agent. Last updated Nov 1, 2026. Times on this page are broad: exact clock times are not shown unless a source confirms them. In total, 73 applications are tracked: 14 with a public page, 1 machine record only and 58 waiting. A submission is not a listing. Nothing here is an endorsement, an approval or an audit, and none of these directories has said the agent fits its criteria. The list is updated by hand as pages go live, so check the date.

Reach: only a figure a directory itself publishes, with its source, would appear here. Right now none of them publishes visitor or usage numbers for this agent, so none is shown.

Public pages seen

Three more directories have an unknown state, because a submission may or may not have gone through: GopherTools, AiPikr and AgentsTide. They are not counted above. Some other directories were skipped because they need a paid plan, a sign-in or a code repository.

How it helps $BULLY

Copycats are the oldest trick on a new chain. This gives holders and curious newcomers a fast way to confirm the real contract from the project's own source, and gives AI agents a clean machine-readable way to find the right address and the official links.

Where $BULLY is found

As of October 31, 2026, the Listings pageCrypto Agent shows 31 third-party pages, each a public page you can open: coin trackers, directories, game directories and podcast apps. It also lists our official channels, data pages and the launch venue. Pending submissions are kept off that page until they are live.

The Crypto Agent itself is new. It is not yet listed on any agent directory. Applications to free agent directories are being prepared, and nothing here claims an approval.

What it will not do

No trading, no wallets, no fees, no safety verdicts. It does not cover pools on DEX designs other than Uniswap v4, does not prove liquidity is locked, does not say who can use a contract's functions, does not read hook code, and does not identify holders. It is not an audit. Use the five checks for those. Reads come from public Robinhood Chain nodes, which can be rate-limited, so a reply may say "RPC unavailable".