- Which agent is making the request?
- Which funding source and policy apply?
- Is the provider, recipient, asset, protocol, and route allowed?
- Is the request inside its per-call, task, session, or recurring budget?
- May it proceed under policy, must a person approve it, or should it be denied?
- What was purchased, delivered, prepared, submitted, or completed?
What you can use today
Explore the product preview
Explore fixture-driven policy, funding context, audit, and transaction-review surfaces.
Request a read-only simulation
Use the public Please MCP service from a compatible AI client to discover supported actions and preview one structured action.
Authority stays outside the model
AI may interpret a request and explain an outcome. It must not grant itself authority, edit policy, invent arbitrary transaction material, or turn tool output into permission to spend. Deterministic systems own the financial workflow: identity, policy evaluation, budget reservation, typed planning, simulation, approval binding, execution authority, reconciliation, and receipts.Three promises
- Bounded capability. Give an agent the narrow financial action it needs, not general access to a wallet.
- Deterministic authority. Policy explicitly allows, asks, or denies the exact request.
- Readable accountability. Record the agent, purpose, budget, decision, route, settlement, delivery, action, and outcome.
Try the quickstart
Explore the product and run your first read-only preview.
Understand the safety model
Learn what please can—and cannot—do with agent authority, assets, and credentials.