> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.solvimon.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.solvimon.com/_mcp/server.

# get_metering

**Live server:** available on `mcp.solvimon.com` as well as on the test server.

Read-only access to everything related to measuring usage, plus tools to debug it. Check here for a compatible meter before creating a new one.

**Actions:** `list`, `get`, `csv_template`, `download_url`, `calculate_cost`

**Resource types:** `meters`, `meter_values`, `meter_value_calculations`, `meter_properties`, `meter_property_variables`, `meter_property_variable_values`, `meter_data`, `events`, `event_trace`, `files`, `file_lines`

* **Why is this event (not) billed?** `get` on `event_trace` with an event id or reference shows when it was ingested and processed and what it matched: subscription, product items and invoice (with its number and Desk link). An event without matches says it found no matching subscription.
* **Why did my CSV upload fail?** `list` on `files` shows recent uploads. `list` on `file_lines` with `filter.file_id` shows the failed rows and why.
* **What would this cost?** `calculate_cost` prices an event against the customer's current subscription without storing it.
* `csv_template` on a meter returns the header row its bulk upload must use.
* Listing `meter_data` or `events` must be narrowed with `filter.meter_id` or `filter.reference`.

**`Trace an event`**

```json Trace an event
{"action": "get", "resource_type": "event_trace", "id": "evt-0001"}
```