What can an agent do to this wallet?

What this check does not cover

An agent can hold power over a wallet through routes this query does not touch, and a clean result above says nothing about them.

• Unregistered sessions. Granted with register: false, enforced by the account, invisible to every third party including this page.
• Binance's Agentic Wallet. Its authority state is off chain by design. Binance's own documentation says the limits you set constrain the agent “at the API level”, the key is MPC and “never fully reconstructed on any single device or server”, and access is withdrawn by signing out in the app rather than by a transaction. There is no contract and no getter, so no third party can verify those limits — including us. We report that as unreadable rather than implying we checked.
• Plain token approvals. An approve to a spender grants ongoing power to move a token with no session, no expiry and no registry entry.
• The permission set itself. The Keystore exposes getKeys, isValidKey and getPublicKey, and no getter for the allowlist, spend caps or expiry — those are arguments to registerKey, not readable state. So the exact scope of a key granted by someone else is not derivable from the registry alone.

What is verifiable here is whether a key holds authority at this block, and that revoking it is possible and immediate. Both were confirmed on chain, including a real session-key transaction and a revocation that took effect at once.