A policy and evidence prototype for agent spend
Noesia is exploring how a platform or enterprise could express rules for software-initiated spending and inspect the resulting policy decision. The current documented artifact is an internal prototype, not a deployed financial product.
Internal prototype direction. No production payment, customer deployment, or public integration is announced.
The problem being tested
AI agents can complete tasks across digital services, while the authority and context behind a purchase may be difficult for an operator to review. The research question is whether a specific buyer needs a workflow that connects an agent request to a bounded policy decision and evidence. This remains a buyer hypothesis, not validated demand.
What the internal prototype demonstrates
The fundroom deck describes internal test identities, sample merchant/category/limit rules and a policy test that can return pass or deny against illustrative fixtures. The example is not a payment authorization. Production identity, customer authorization, settlement, dispute handling and payment integrations are not claimed.
What is not established
No customer deployment or signed design partner is reported in the reviewed deck. The deck also treats pricing, financing, production integrations and market demand as unvalidated. Feature states require product, engineering and counsel approval before being presented as commitments.
Explore the research
Read about agentic payments, agent wallets and enterprise agent controls, or browse the use-case questions.