Pay With Locus · USDC wallets on Base
AI Agent Audit Trail
Every transaction your AI agent makes is logged with full context — amount, recipient, reasoning, timestamp, and on-chain proof. Complete transparency for compliance and debugging.
Updated
Why audit trails matter for AI agents
When an AI agent operates autonomously — making API calls, purchasing services, and transferring funds — you need to know exactly what it did and why. Without an audit trail, debugging a misbehaving agent is nearly impossible. You can't tell whether it overspent because of a retry loop, a hallucinated price, or a legitimate but expensive operation. For enterprises, audit trails are also a compliance requirement. Regulators and internal auditors need to verify that automated spending follows approved policies. Locus provides a comprehensive audit trail for every transaction, combining on-chain blockchain records with rich application-level context.
What Locus logs for every transaction
Transaction details
Amount in USDC, recipient address or API endpoint, timestamp, gas fee, and on-chain transaction hash on the Base network. Every payment is verifiable on the blockchain.
Agent context
Which agent initiated the transaction, from which wallet, using which session key. In multi-agent setups, you can trace spending back to the specific sub-agent responsible.
API call metadata
For API payments: the provider called (OpenAI, Anthropic, etc.), the model used, token counts for input and output, latency, and the HTTP status code. Useful for debugging and cost optimization.
Policy enforcement log
Which policies were checked before the transaction executed, whether any limits were close to being hit, and whether any transactions were blocked by policy violations.
On-chain transparency
Because Locus wallets operate on the Base network, every USDC transfer is recorded on the blockchain. This provides an immutable, tamper-proof record that exists independently of Locus's own logs. You can verify any transaction using a block explorer. This dual-layer approach — Locus's rich application logs plus on-chain records — gives you both the detailed context you need for debugging and the cryptographic proof you need for compliance. The blockchain record cannot be altered or deleted, providing a permanent audit trail.
Use cases for audit trails
- •Debugging agent behavior — When an agent produces unexpected results, trace back through its spending to understand which APIs it called, in what order, and at what cost.
- •Cost optimization — Identify which API calls are consuming the most budget and optimize model selection or caching strategies accordingly.
- •Compliance reporting — Generate reports showing all automated spending, policy adherence, and exception handling for internal or regulatory audits.
- •Multi-agent accountability — In swarm architectures, attribute spending to individual agents to understand which parts of the workflow are driving costs.
Related resources
Frequently asked questions
What does Locus record for each agent transaction?
The amount in USDC, the recipient or API endpoint, the timestamp, the gas fee, and the on-chain transaction hash on Base. It also records which agent, wallet, and session key made the payment.
Can I verify an agent payment outside Locus?
Yes. Every USDC transfer from a Locus wallet is recorded on the Base blockchain. You can look up any transaction in a block explorer, independent of Locus's own logs.
How do I find which agent in a swarm spent the money?
Each transaction records the agent, wallet, and session key that initiated it. In multi-agent setups you can trace spending back to the specific sub-agent.
Does the audit trail show blocked transactions?
Yes. The policy enforcement log shows which policies were checked and whether any transaction was blocked by a policy violation.