---
title: "Costs and usage"
description: "Explore what your organization's usage cost and how much of each metered resource it used."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Costs and usage

Two console pages chart your organization's metered usage over time: **Cost explorer** shows
what it cost, and **Usage** shows the quantities. Both need the `billing.costs.get` permission.
Times are in UTC. The page URL keeps your range, grouping and filters, so you can share a view.

## Cost explorer

Open **Billing** > **Cost explorer**.

| Control | Options |
| --- | --- |
| Date range | This month, Last month, Last 3 months, Last 7 days, Custom range… (the end date is included) |
| Granularity | Hourly (ranges of up to 14 days), Daily, Monthly |
| Group by | Service, project, meter, SKU or region, then optionally a second key with **Then by** |
| Filters | **Service** and **Project**; each takes one or more values. **Clear filters** removes them |

The page shows the total for the range, a chart per hour, day or month, and a table of each
group's cost and share of the total. When you group by meter or SKU, the table also shows usage.

## Usage

Open **Billing** > **Usage**. Each meter has its own chart, because quantities of different
meters don't add up. Quantities are shown in display units, such as hours and GB-hours.

| Control | Options |
| --- | --- |
| Date range, Granularity | As in Cost explorer |
| Group by | **By meter only**, or by project or region within each meter |
| Filters | **Meter** and **Project** |

Usage appears as soon as it is measured. Its cost appears in Cost explorer once it is priced, so
the most recent hours can differ between the two pages.

## API

The same data is available from `billing.ezghcloud.com` with an API key.

```sh
curl "https://billing.ezghcloud.com/v1/organizations/$ORG_ID/costs?from=2026-09-01&to=2026-10-01&granularity=day&groupBy=service,project" \
  -H "Authorization: Bearer $EZGH_API_KEY"
```

```sh
curl "https://billing.ezghcloud.com/v1/organizations/$ORG_ID/usage?from=2026-09-01&to=2026-10-01&granularity=day&groupBy=project" \
  -H "Authorization: Bearer $EZGH_API_KEY"
```

| Parameter | Description |
| --- | --- |
| `from`, `to` | Required. A date (`2026-09-01`) or a whole UTC hour (`2026-09-01T10:00:00Z`). `to` is excluded |
| `granularity` | `hour`, `day` (default) or `month`. An hourly range is at most 14 days; others at most 13 months |
| `groupBy` | Up to two keys, comma-separated. Costs: `service`, `project`, `meter`, `sku`, `region`. Usage: `project`, `meter`, `region`; usage is always split by meter |
| `filter` | `key:value` pairs, comma-separated, with the same keys. Values of one key match any of them: `filter=project:<id>,project:<id>` |

Each response holds the whole range in one page. Costs (`billedCost`) are decimal strings in
millionths of a US dollar: `"1250000"` is $1.25. `values` lists the values of each key present in
the range, and `labels` gives names for services, meters and SKUs.

Source: https://docs.ezghcloud.com/billing/costs-and-usage/index.mdx