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

# Check Usage

## Overview

This feature lets you view your usage, which is the basis for Hackle's billing.

You can view usage for A/B Test, Feature Flag, Event, and Event (Import) by event type and by period. The billing amount for that usage may vary depending on the contract terms.

## Current Plan

Click the gear icon at the top of the Dashboard to access the 'Workspace Settings' menu, then navigate to the 'Current Plan' menu.

![](/files/Y2c5JBwSTYfiOY82V6ZR)

You can query by selecting the desired period and unit (daily/monthly).

![](/files/ksa803msOszSPGmL7xHz)

By selecting A/B Test, Feature Flag, Event, or Event (Import) from the type filter, you can easily view the usage for each detailed item in the table below.

A/B Test, Feature Flag, and Remote Config distribution events occur when an experiment key, feature key, or remote config key is called and a valid value is returned. Tests that are in Draft or have ended are excluded from billing even when called.

Events include auto-collected events automatically gathered by the Hackle SDK (such as $page\_view, $engagement) as well as custom events sent directly by customers.

CRM campaign events — In-App Message impressions ($in\_app\_impression), clicks ($in\_app\_action), Push Message sends ($push\_send), and clicks ($push\_click) — are also included in events along with auto-collected events. Push Message send events are billed based on the send request, and invalid push tokens are automatically deleted to ensure fair billing.

Event (Import) refers to events collected via the Data Import method.


---

# 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.hackle.io/en/workspace/billing.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.