> For the complete documentation index, see [llms.txt](https://docs.codewords.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codewords.ai/automations/usage.md).

# Usage

Track how you’re spending credits across chats and runs, see your top categories, and drill into a day-by-day breakdown of what each credit was spent on.

### What is Usage?

[Usage](https://codewords.agemo.ai/#settings/usage) lives inside Settings. It’s where you see how credits are being consumed — spend across chats and workflow runs, your wallet balance, your plan, and a day-by-day breakdown of what each credit went to.

Open it from the sidebar account menu (**Usage**), or go straight to [codewords.agemo.ai/#settings/usage](https://codewords.agemo.ai/#settings/usage).

{% hint style="info" %}
Usage is about **credit spend**. For run logs, statuses, and scheduled runs, use the [Activity](https://docs.codewords.ai/automations/activity) page (`/activity`). The Wallet FAQ link labeled **History** also goes to Activity — not this Usage tab.
{% endhint %}

### What you can do there

**1. Cycle Spend**

* Shows the total credits used in the selected billing cycle (e.g. *141.85 credits over 5,818 requests*).
* A bar chart breaks each day’s spend into **Chat** (credits spent while building or chatting with Cody) and **Runs** (credits spent executing workflows).
* Use the calendar dropdown to switch billing cycles.
* Hover **What counts as a request?** for a short explanation of request counting.

**2. Wallet, Plan, and Top Category**

* **Wallet** — your current credit balance available to spend.
* **Plan** — the subscription tier you’re on (Free, Pro, Business).
* **Top Category** — where you’re spending the most this cycle (e.g. *Chat — 137.20 credits · 97%*), so you can see at a glance whether credits are going into building or running.

**3. Day Breakdown**

* Click any bar in the chart to open that day’s breakdown.
* The header shows total credits and request count for the day.
* Each chat or workflow run is listed with its name, whether it was a **Chat** or a **Run**, and the credits it used.
* Click a charge row to jump to that chat or run. Settings closes when you navigate away.

### When to use it

* **Reviewing your spend** — see where credits went this cycle and which automations cost the most.
* **Optimising workflows** — spot any chat or run taking an unexpectedly large share of credits.
* **Planning top-ups or upgrades** — pair cycle spend with your wallet balance to decide when to top up or move to a higher plan. Top-ups live in [Wallet](https://codewords.agemo.ai/#settings/wallet-plans); plan changes live in [Plans](https://codewords.agemo.ai/#settings/plans).
* **Investigating a specific day** — if your balance dropped suddenly, open that day to see which chats or runs were responsible.

For plans, top-ups, and how credits work overall, see [Plans and Pricing](https://docs.codewords.ai/pricing).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.codewords.ai/automations/usage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.