Agent wallets: identity, authority and spend
“Agent wallet” can describe several different things: a software-held credential, an issuer-controlled virtual card, a ledger or a way to express spending rules. Those designs have different security, operational and legal boundaries.
Category guide only. Noesia does not announce an available wallet, issued card, bank account or payment rail.
Ask what the wallet actually holds
Does the system hold a payment credential, a balance, a token, or only a policy reference? Who issues it, who can fund it, and which party authorizes or settles a transaction? A product label alone does not answer these questions.
Controls to evaluate
Check how the agent is identified, whether limits are enforced at the authorization point, how merchant/category rules work, how credentials are stored, and what happens on revocation, timeouts, duplicate requests and disputes. Distinguish a UI limit from a rule enforced by the payment system.
A crowded and changing landscape
The fundroom competitive research documents activity across card issuers, spend-management platforms, payment networks, agent-wallet providers and checkout protocols. The memo is a dated desk-research snapshot, not an exhaustive or independently verified market map. Avoid claims that any capability is unique or that no competitor offers it.
Noesia status
The current fundroom truth-table is marked working draft and not approved. It reports no production capability as approved; any prototype should be identified as internal and illustrative. See the product overview and security checklist.