# AI agent audit logs: what to record and how to review them

An audit log is the record of everything an AI agent did: what it read, which tools it used, what it sent or spent, and who approved it. What a good log includes, how to review it in 10 minutes a week, and what to do when something looks wrong.

Canonical HTML: https://agentlane.net/guides/ai-agent-audit-logs/

## Steps

1. **Check every send and every payment.** Compare against the sent folder and card statement, not the agent’s summary. See confirm in the source, not chat.
2. **Look for actions you did not ask for.** New recipients, new merchants, deleted files, or changed settings.
3. **Check approvals.** Anything that should have waited for your yes and did not is a setup problem to fix today. See review before place.
4. **Note cost and volume.** A sudden jump in runs or spending is an early warning. See AI agent spending limits.
5. **Act on what you find.** Fix the instruction, remove a tool, or cut access. If something looks wrong, revoke first and investigate second. See revoke before you debug.

## FAQ

### What is an AI agent audit log?

A dated record of what an AI agent did: what it was asked, which tools it used, what it sent, changed, or spent, and who approved it.

### Why not just trust the agent’s summary?

The summary is the agent’s own description and can be wrong or incomplete. The sent folder, card statement, and app history are records the agent cannot rewrite.

### How often should I review agent logs?

Ten minutes a week is enough for most small businesses, plus a check after any new permission or unusual result.

### What should I look for in an AI agent log?

Every send and payment, actions you did not ask for, missing approvals, and sudden jumps in runs or spending.

### How long should I keep AI agent logs?

At least long enough to cover a billing cycle or customer dispute; ask your accountant if the records relate to money or taxes.