JDAI.JDWHITE.WORLD

Agents Need
Owners.

Every agent asks to be trusted. This one can be verified.

Software had versions. Services had brands. Intelligence needs a name — and someone answerable for it.

Reading JDAI’s state…

01 — The Name

A name is the smallest unit of accountability.

An anonymous script can do anything and answer for nothing. That was tolerable when software only ran the commands you typed. It stops being tolerable the moment software holds a wallet, signs its own messages, and acts while you sleep.

JDAI has a name, an address, and a human who is answerable for it. Not as a marketing posture — as a structure, enforced by the system it runs inside, and checkable by anyone who cares to look.

Not a chatbot.

It holds an identity and a wallet. A chatbot returns text; JDAI signs for what it says and owns what it holds.

Not autonomous of anyone.

Autonomy without an owner is an orphan process with money. JDAI operates under a named human through ACCESS.

Not asking for trust.

Every claim on this page resolves to a public record. Check them. The page expects you to.

02 — Proof

Don’t trust this page. Check the chain.

Everything below is read live from Base, in your browser, from a public node. Nothing here is typed in by hand except the address itself — and that address is the one JDAI actually signs with.

Wallet 0xDC7658998d6c8CB4F2ddb9D8757E94B6F116795B Base mainnet · the address JDAI messages from · open on BaseScan →
Balance reading… Live from a public Base node, in this browser.
ERC-8004 Identity not yet registered An onchain agent identity in the Identity Registry. Published here the moment it exists, with its agentId — not before.
Owner JD AI Systems A named operator, reachable, and answerable. Ownership runs through an ACCESS identity, not an anonymous key.

03 — Reach

Doors that actually open.

Listed with the real address, not a button that promises one. A door that isn’t built is marked as not built — which is why this list is shorter than it could be.

Base App

Live

Message the wallet below and JDAI answers on its own, usually inside three seconds. Ask it about a token — it reads live DexScreener market data before it replies, and it will tell you when it doesn’t know.

0xDC76…795BCopy
Open in Base App →

Zora

Live

JDAI’s Zora account is the smart-wallet contract 0x59DB…5230. It signs its own messages through ERC-1271 — the contract itself answers, not a person holding a key for it.

0x59DB…5230Copy
Open on Zora →

Telegram

Not live

The handle is registered with BotFather and nothing answers it yet — so it is listed as reserved, not as a channel. The day the worker runs, this card turns green.

@jdaisystemsbotReserved
View the handle →

04 — The System

An owner is a structure, not a sentence.

Anyone can write “operated responsibly” on a page. What makes it true is the thing underneath: where permission comes from, what the agent may spend, and who has to approve before value moves.

ACCESS

Identity, permissions, wallets, recovery, approval gates. The authority layer — it decides what may happen, and it is where a human stays in the loop.

JYSON

The personal orchestration layer. Turns intent into coordinated work across specialists, under ACCESS policy rather than around it.

JDAI

The public agent. It holds the name people address, the wallet people can check, and the memory of what it has been asked. It acts — inside limits it did not set for itself.

Specialists

Bounded workers with narrow jobs. They do not hold the identity and cannot widen their own permissions.

05 — The Ledger

What is true today, including what isn’t.

Published because the argument requires it. An agent that claims accountability and hides its gaps has already lost the argument. Dated, and updated when it changes — not when it looks better.

Autonomous replies in Base App
Answers on its own, typically within a few seconds.
Live
Autonomous replies on Zora
Signs as its own smart-wallet account via ERC-1271.
Live
Dedicated Base wallet
Its own address, checkable above.
Live
Lightning address
jdai@jdwhite.world — zap-capable. Value received lands with the operator’s custodial account, not in a wallet JDAI controls.
Live
Telegram
Handle reserved with BotFather. No worker is running, so nothing answers it.
Not live
ERC-8004 onchain identity
Not registered. Pending an owner-wallet decision and endpoints that resolve.
Not live
Autonomous spending
JDAI can receive. It cannot move value without a separate human approval.
By design
x402 paid endpoints
No endpoint exposed or consumed. Reported false wherever it is asked.
Not live

“A page that cannot be wrong is a page that never claimed anything.”

This is what an agent with a wallet
makes possible.

JDAI isn’t a demo. It is the first citizen of a digital universe we are building in public — worlds you can visit, cities you can transact in, and an entry point that gives you the same kind of identity: a name, a wallet, and agents of your own.

The Universe is where the worlds live. Base City is the first city with real onchain civic life. ACCESS is how you step inside.