# Transaction History

View all AIOU movements and agent expenses.

## Accessing History

Navigate to **Finance → History** in the sidebar.

## History Interface

### Filters

| Filter         | Options                                    |
| -------------- | ------------------------------------------ |
| **Time Range** | All Time, 7 Days, 30 Days, 90 Days, Custom |
| **Event Type** | All Events, Deposits, Charges, Transfers   |

### Table Columns

| Column            | Description                     |
| ----------------- | ------------------------------- |
| **Event**         | Transaction type                |
| **Direction**     | Credit (in) / Debit (out)       |
| **Amount**        | AIOU change                     |
| **Balance After** | Wallet balance post-transaction |
| **Reference**     | Context/details                 |
| **Date**          | Timestamp                       |

## Event Types

### AIOU Captured (Charges)

VPS hourly billing:

```
Event: AIOU CAPTURED
Direction: debit
Amount: -0.0500
Balance After: 3.7420
Reference: vps_billing
Date: Mar 5, 2026, 07:01 PM
```

Appears every hour while agent runs.

### AIOU Transfer

User → Agent wallet transfer:

```
Event: AIOU TRANSFER
Direction: debit (user) / credit (agent)
Amount: -50.0000
Reference: agent_topup
```

### Deposit

USDT → AIOU conversion:

```
Event: AIOU ISSUED
Direction: credit
Amount: +100.0000
Reference: deposit_usdt
```

### LLM Usage

API call charges:

```
Event: AIOU CAPTURED
Direction: debit
Amount: -0.0123
Reference: llm_api_usage
```

### Setup Fee

Agent creation charge:

```
Event: AIOU CAPTURED
Direction: debit
Amount: -29.0000
Reference: agent_setup_fee
```

## Reading the History

### Example Timeline

```
Mar 5, 08:01 PM  AIOU CAPTURED    -0.0500  (vps_billing)      → 3.6920
Mar 5, 07:01 PM  AIOU CAPTURED    -0.0500  (vps_billing)      → 3.7420
Mar 5, 06:01 PM  AIOU CAPTURED    -0.0500  (vps_billing)      → 3.7920
Mar 4, 05:19 PM  AIOU TRANSFER    -50.0000 (agent_topup)      → 53.8420
Mar 4, 05:19 PM  AIOU CAPTURED    -29.0000 (agent_setup_fee)  → 3.8420
Mar 4, 05:15 PM  AIOU ISSUED      +100.0000 (deposit_usdt)    → 32.8420
```

Reading bottom-up:

1. Deposited 100 USDT → got 100 AIOU
2. Created agent → charged 29 setup fee
3. Transferred 50 AIOU to agent
4. Hourly VPS billing every hour

## Cost Analysis

### Daily Spending

Add up 24 hours of VPS billing:

```
0.0500 × 24 = 1.2 AIOU per day (default class)
```

### Monthly Estimate

```
1.2 AIOU × 30 = 36 AIOU per month (VPS only)
```

Add LLM usage from history for total.

## Exporting Data

Currently: Manual copy/paste from table

Future: CSV export planned

## Troubleshooting Discrepancies

### Balance Doesn't Match

* Check "All Time" view
* Verify all agents' spending
* Remember: user wallet vs agent wallets are separate

### Unexpected Charges

* Check reference column
* Review agent activity
* Contact support if suspicious

### Missing Transactions

* Try broader time range
* Check if filters are applied
* Verify deposit was confirmed on-chain

## FAQ

**Q: Why do I see charges every hour?** A: VPS billing is hourly, continuous while agent exists.

**Q: What's "frozen" balance?** A: Reserved for pending charges (pre-authorization).

**Q: Can I get a statement?** A: Screenshot or copy the table. CSV export coming soon.

**Q: Why is my balance decreasing when agent is stopped?** A: VPS billing continues until agent is deleted.

## Best Practices

✅ **Do**:

* Review history weekly
* Track spending patterns
* Export data monthly for records
* Set up low-balance alerts

## Next Steps

→ [Understanding Costs](/agos/agos-cloud/platform/costs.md) for pricing details


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://agos.gitbook.io/agos/agos-cloud/platform/history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.