> ## 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.

# Define plan features and per-plan limits

> Define plan features (name, permanent key, boolean or number type, description), give each plan its own value, and gate on them in your app.

Features describe what each plan offers. You define a feature once for the app, then include it in as many plans as you like with a value per plan. That's how a plan says "this tier gets advanced reports" or "this tier is capped at 5 seats".

## Defining one

| Field | What it's for |
| - | - |
| **Name** | Shown to merchants in plan cards and the upgrade prompt |
| **Key** | What your app checks at runtime. Auto-filled from the name, lowercase snake\_case, and **fixed after creation** |
| **Type** | **Boolean** unlocks a capability; **Number** sets a limit. Also fixed after creation |
| **Description** | Shown in the merchant-facing plan card, up to 240 characters |

The key and type are immutable because your code already gates on them and values are stored per type. The name and description are yours to rewrite whenever: they're marketing copy, not contracts.

The features list is searchable by **name** or **key**. [Global search](https://help.the-meridian.ai/global-search.md) ranks an exact key match first, which is useful when you are debugging `isEnabled("<key>")`.

## Features and plans

The link is many-to-many with a value per plan: a plan includes many features, and a feature appears in many plans, each with its own value. A boolean feature is simply in or out of a plan; a number feature carries that plan's limit.

Set which features a plan includes, and their values, when you [create the plan](https://help.the-meridian.ai/create-a-plan.md). A feature can be deleted once no store subscribes to a plan that includes it. Plans without subscribers lose it automatically when you delete it. To stop offering it to new stores now, remove it from the current version of each plan.

## Gating in your app

Your app reads features through the [SDK](https://help.the-meridian.ai/features.md): in React, `useMeridian()` gives `isEnabled(key)` for a boolean and `getLimit(key)` for a number. On the server, `gates.can(key)` and `gates.limitOf(key)` do the same. The feature page shows the exact snippet for the feature you're looking at, so the key you gate on is copied, not retyped.

Three things worth knowing about gating:

* A key your app checks that doesn't exist resolves to **not enabled**: a typo silently gates nothing off, which is why the snippet exists.
* Entitlements resolve through one path everywhere, so a gate behaves the same in your app, in the SDK, and in an agent reading Meridian MCP.
* A merchant who upgrades gets the new values immediately; there's nothing to sync on your side.

> [!NOTE]
>
> Features are about **what a plan includes**, not about metering. If the thing you want to charge for is a count that goes up with use, it's an [event](https://help.the-meridian.ai/usage-events.md), not a number feature.


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