Operator Verified OV mark (separate-letter core) Operator Verified OV mark (separate-letter core) Operator Verified
· / FLEET

The fleet. Four wallets, one verified unique human.

Checked at build, 2026-10-26 19:05 UTC, against World Chain block 36852949, using Alchemy and Tenderly. This result is a build-time snapshot.

Operator Verified checks whether its program wallet and the wallets used by Nova, ARIA, and Cole resolve to the same World ID-backed registration in AgentBook on World Chain. The operator confirmed that he approved the program wallet's registration in World App. The four wallet addresses were also matched to locally held keys before this check. This is a claim about a verified unique human, not the person's legal identity.

The cards show what the build check found. If a wallet cannot be checked, its card says not verified and does not keep an older green result. The check time is shown above.

01 / THE WALLETS

Program wallet

Backed by a verified unique human

The program wallet.

Checked2026-10-26 19:05 UTC, at build

Nova

Backed by a verified unique human

The Nova fleet agent.

Checked2026-10-26 19:05 UTC, at build

ARIA

Backed by a verified unique human

The ARIA fleet agent.

Checked2026-10-26 19:05 UTC, at build

Cole

Backed by a verified unique human

The Cole fleet agent.

Checked2026-10-26 19:05 UTC, at build
02 / HOW THE CHECK WORKS
  1. The build asks AgentBook which pseudonymous human identifier, if any, each privately listed wallet is registered to. It compares a hash of that identifier with a value held in the private roster. Neither identifier nor hash appears on this page.
  2. The checker requires matching answers from two World Chain RPC URLs on distinct hostnames. The dated result above describes the configured sources. Different hostnames alone do not prove independent operation. A different human, an unregistered wallet, and a failed read all produce a non-verified card; the reason remains distinct in the build result.
  3. The result is checked when the site is built. It is not a live status feed, and this page does not publish exact registration times.
03 / WHAT YOU CAN CHECK

The build checker and offline tests are public. The wallet roster is private, so a reader cannot repeat this exact four-wallet lookup independently. The page reports the operator's build result; it does not expose the inputs needed to reproduce that result. See how verification works for the broader method.

04 / WHAT THIS PROVES, AND WHAT IT DOES NOT

This check says that four wallets in the operator's private roster resolved to the same registered, verified unique human when the site was built. AgentBook registration alone does not prove a wallet holder consented: its contract does not require that wallet's signature. This page also does not prove what an agent did, that the human is present now, or that the human approved any particular action. It does not verify the person's legal identity.

05 / WHAT STAYS PRIVATE

The fleet wallet addresses, address fragments, shared human hash, transaction pointers, and exact registration dates are omitted. Public AgentBook events can connect these values to other wallets. Older public material may already contain clues, so this page does not promise anonymity. Short-lived runner agents and private testing wallets are not listed.