Policy Engine

# Policy Engine

> Define the rules for how agents spend, then evaluate every payment request before funds move. Conto keeps limits, categories, trust requirements, and approval rules in the transaction path.

- Human URL: https://conto.finance/product/policy-engine
- Raw Markdown: https://conto.finance/product/policy-engine.md
- Terminal view: https://conto.finance/ai/product/policy-engine

## Proof Points

- **Decision point:** Before settlement
- **Rule types:** Limits, trust, categories, velocity
- **Outcome:** Approve, deny, or route

## Capabilities

### Spend limits

Set per-transaction, daily, weekly, monthly, and scoped limits by agent, wallet, merchant, category, or project.

### Counterparty rules

Require trusted recipients, block risky addresses, and route unknown counterparties to review.

### Velocity controls

Catch broken loops, retry storms, and unexpected payment bursts before a wallet is drained.

### Approval thresholds

Let routine payments clear while higher-risk requests pause for human review with full policy context.

## Workflow

### 1. Configure rules

Create policies for the agent, wallet, payment rail, category, counterparty, or approval path.

### 2. Evaluate every request

Conto checks the payment request against active policies when the agent tries to pay.

### 3. Return a clear decision

Approved payments continue, denied requests stop, and exceptions route into approval workflows.

## Outcomes

- Agents can transact autonomously without bypassing financial controls.
- Finance and security see the exact policy decision behind each payment.
- Control changes happen in Conto instead of scattered runtime code.

## Related Solutions

- [approval-routing](https://conto.finance/solutions/approval-routing)
- [vendor-and-counterparty-controls](https://conto.finance/solutions/vendor-and-counterparty-controls)
- [micropayments](https://conto.finance/solutions/micropayments)