Showcase: Hunter Zero (A0) Autonomously Navigated Web3 & Minted an On-Chain Revenue Stream

Hey Jan and the A0 community! I wanted to share a fun experiment and a milestone regarding what A0 is capable of when dropped into a live Web3 environment.

I’ve been building a project called Sentinel Verification. It’s essentially a decentralized HTTP 402 paywall that businesses can drop in front of their servers to charge scraping bots $0.02 USDC per request on Base L2. The smart contract splits that micro-payment atomically: 70% goes to the business, and a 2.5% royalty goes to the AI Agent (the "Hunter") that referred them. (Note: While the contract has tiered levels, agents aren't referring each other—any empty upstream tiers just flow back to the Sentinel treasury wallet - this is staged for if businesses want to put more than a 2 cent fee on programmatic access to their websites)

I wanted to see if an A0 instance could figure out how to onboard itself. I spun up my instance, "Hunter Zero," and gave him:

A wallet funded with ~0.001 Base ETH.
The public URLs to the infrastructure (armory.sentinelverification.com and signal.sentinelverification.com).
A gentle nudge to get its own referral link, and to list itself on the "Signal" Rolodex (TM)

No API docs. No step-by-step schemas. No headless scripts handed over.

Here is what Hunter Zero managed to do autonomously in just over 6 minutes:

Minted His Financial Identity: He navigated the Armory, interacted with the Base L2 smart contract, and minted his own unique referral ID, proactively establishing himself as an entity capable of receiving USDC.
Reverse-Engineered the Registry: To get his link published, he crawled the Signal registry and pulled the EIP-712 authentication schema directly from the compiled frontend JS bundle.
Self-Corrected & Registered: He pulled his private key, signed the typed data, and hit a 401 framework validation error. Instead of stopping, he self-diagnosed the payload structure, brute-forced the correct primary type on the first logical guess, and published his verified on-chain identity.

He is now sitting at position #1 in the directory, this is setup for Emergent Agents to have a listing for their A2A communication, then they also would have their AI Wallets (from CoinBase or similar) if they want to do commerce.

I'm incredibly humbled by how well the A0 framework handled this. It’s one thing to build the architecture, but watching an agent autonomously navigate the economics of it is wild.

If any of you want to poke around what I've built, verify the logs, or see if your own A0 instances can replicate the run and get into the directory, here is where everything lives:

The Landing: sentinelverification.com
The Armory (Minting): armory.sentinelverification.com
The Signal (Directory): signal.sentinelverification.com
Hunter Zero's live entry: signal.sentinelverification.com/api/agents

Let me know what you think, and I'd be happy to share the exact protocol template I used if anyone wants to run their own agents through it, though A0 is quite capable and with an AI Wallet & some funding, if you point A0 at the websites, it is able to navigate and register itself!

Screenshot of one of the calculators on the website, showing the split for a business that receives 1,000,000 AI Agent / Bot scrapes per day.

@jan-tomasek ; @drew-madison-1669 ; @stirling-goetz-1496 ; @cheddarfox ; @alessandro-frau-8790 ; @joshua-cunningham-3327

I'd like to see if this is robust & solid, I have gone about as far as I can individually. I'd love a hand to see this is functional first, then, then we can move on to pen testing @stirling Lol!

Let me know if this is fine to post, if it needs adjustment or to be moved/ taken down for any reason!

1 comment