An agent wallet answers where keys and funds live. A financial control plane answers who may use them, for what purpose, within which limits, and with what evidence.
please is designed to keep those decisions outside the language model.
The control plane owns
- tenant, operator, agent, and funding-source identity;
- capability, provider, recipient, asset, protocol, and venue allowlists;
- per-call, task, session, daily, and recurring budgets;
- deterministic
allow, ask, and deny decisions;
- independent approval for exceptions and material actions;
- reservation, idempotency, and replay protection;
- protected execution authority;
- settlement, delivery, submission, finality, and reconciliation state;
- readable receipts and an append-only audit history.
The control panel
The control panel is the human interface to this system. It should make agents, policies, budgets, approvals, activity, receipts, exceptions, funding sources, and emergency controls visible.
What remains underneath
MCP and APIs provide the agent-facing interface. Wallets and payment rails hold or move value. The planning engine validates and simulates typed actions. Protocols and networks provide execution.
These are important components, but none of them replaces the control plane.
The current public service is read-only. The architecture described here is the intended authenticated product boundary, not a claim that public spending or transaction execution is available today.
