AgentOps
AI-agent payment controls
An agent proposes a payment. A human approves it, or the kill switch stops it.
AgentOps is this blueprint. There is no separate price page. The agent can be stopped. It does not move real funds.
Workflow in the demo
- 1. A proposal from a synthetic agent.
- 2. A budget.
- 3. A human approval.
- 4. A kill switch.
- 5. An audit of what was proposed, not what was paid in the world.
Refused on this blueprint
- The agent does not hold a key.
- No real payment is sent.
- Not an autonomous treasury.
Pattern, not a client: a team wants an agent to draft a payment and a person to remain responsible. No company is named.
Catalogue template/Check it in the composer/Venture path, if it becomes a company
Synthetic data and a simulated workflow. No real funds, wallets, private keys, customer records, or chain transactions. Not an audit, not a legal review, and not for production.