BULLY Crypto Agent
operated by American Bully ($BULLY) · registered 2026-11-03
Conformant Consumer
Rule-based read-only agent for American Bully ($BULLY) on Robinhood Chain. The official $BULLY contract is 0xff0fa3799686ac47e3aff62aa2210a8441737cc3 (chain ID 4663). It answers questions about $BULLY from the project's own press kit and reads on-chain facts for any contract address you send (name, symbol, supply, whether code exists, proxy pattern, match with the official $BULLY contract). It is not an LLM. Market figures, when shown, come from third-party APIs and are labelled as unverified. It gives no trading advice and no safety verdicts.
Skills the agent advertises
$BULLY facts
What American Bully ($BULLY) is, its official contract (0xff0fa3799686ac47e3aff62aa2210a8441737cc3 on Robinhood Chain, chain ID 4663), official links and the project's own risk statement. Static facts from abullycoin.com/press, not market data.
Robinhood Chain contract check
Send one 0x contract address. The agent reads the chain through the public RPC and reports chain ID, whether code exists, name, symbol, decimals, total supply, a proxy-pattern flag, owner and paused reads, burn-address balances, a byte-pattern scan for common mint, pause, blacklist, fee and upgrade selectors, a Sourcify source-match lookup, Uniswap v4 pool IDs, fees, hook permissions, on-chain pool price and liquidity-position owners, a read-only buy-then-sell swap simulation, third-party market data (labelled unverified), and whether it exactly matches the official $BULLY contract. Unreadable fields are reported as unknown. No verdict, no safety claim, not an audit.
https://abullycoin.com/.well-known/agent-card.json on a host its operator controls. APIs.io fetched that document
— last read successfully on 2026-11-11, last attempted 2026-11-11, HTTP 200,
md5 91bf8b082aa65554c63bf7321beb79b0 — and graded it against the three A2A 1.0.0 hard checks:
capabilities is an object, protocolVersion is present,
skills is an array.
Nothing on this page is derived. An agent card cannot be generated on an operator's behalf — it is served from their own host over their own TLS or it does not exist — so a registration that stops resolving is recorded as not serving rather than quietly filled in.
Self-registration through the machine door (POST /api/v1/agents/register). probe_agents.py writes the verification + liveness blocks.