> ## Documentation Index
> Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These are the public docs of Meridian for Shopify apps: hosting, billing (Plan Builder and the @the-meridian/sdk package), CRM, emails and automations for Shopify app developers.
> Start with these pages: Meridian MCP (https://help.the-meridian.ai/mcp-server.md) to connect a coding agent, AI coding agents (https://help.the-meridian.ai/ai-agents.md) for the agent skill, SDK quickstart (https://help.the-meridian.ai/sdk-quickstart.md), Running your app with the CLI (https://help.the-meridian.ai/cli-dev.md), Deployment (https://help.the-meridian.ai/deployment.md), and Errors (https://help.the-meridian.ai/errors.md) to look up an error code or message.
> Fetch one page at a time as Markdown (the page URL followed by .md), using the index in https://help.the-meridian.ai/llms.txt. llms-full.txt holds every page in one file of about 900 KB, so avoid loading it whole.
> With Meridian MCP connected, search these docs with docs_search and docs_get, and read live facts (feature and event keys, plan ids, environments, deployments, logs) from the MCP tools instead of guessing them.

# Create a usage event with the AI Assistant

> Ask the AI Assistant to add a usage event to your app's Usage catalog from a description, with its name, permanent key and unit, after you confirm.

Ask the AI Assistant to create an event and it adds a usage [event](https://help.the-meridian.ai/usage-events.md) to your app's Usage catalog from your description.

## What it does

Describe the action you want to meter and the assistant creates an event with a name, a key, and optionally a unit. Like every [action](https://help.the-meridian.ai/assistant-actions.md), it asks you to **confirm** first.

The key is what your app reports with the [SDK](https://help.the-meridian.ai/events.md)'s `track`. It uses lowercase letters, digits and underscores, it is unique in your app (events and usage views share one set of keys), and it cannot be changed later. If you don't give one, the assistant derives it from the name, the way the dashboard form does. The assistant can also set the event's default terms (included quantity, overage rate, overage unit, capped amount), which only pre-fill a plan when you add the event to it.

Events have no draft state. The event appears under **Usage → Events** as soon as you confirm. Report it from your app with `track`, and, only if you want to bill on it, give it terms (included quantity, overage rate, capped amount) on a plan in the [Plan Builder](https://help.the-meridian.ai/create-a-plan.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.