> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/ai/mcp-server/pricing.md).

# Pricing Reference

The MCP server supports five pricing types when creating or updating offers. You don't need to remember the exact format: describe what you want and the assistant configures it. This page covers what's available.

## Quick selection guide

| Scenario                                       | Pricing type       |
| ---------------------------------------------- | ------------------ |
| Monthly or annual subscription                 | Recurring          |
| Fixed-term one-off payment (e.g., annual pass) | One-time termed    |
| Lifetime or perpetual access                   | One-time evergreen |
| Standalone product purchase                    | One-time line item |
| Quantity-based tiered pricing                  | Recurring volume   |
| Pay-per-use metered billing                    | Usage per unit     |

## Recurring

Standard subscription billing with a fixed price on a repeating schedule.

**Example:** "Create a monthly subscription at $15/month"

* Set the price, currency, and billing interval (monthly, yearly, weekly, etc.)
* Optionally set how many times it repeats before stopping

## One-time termed

A single charge with a defined term length. The subscription ends when the term expires.

**Example:** "Create an annual pass at $99 that expires after one year"

* Set the price and the term length
* After the term ends, the subscription does not renew

## One-time evergreen

A single charge with no end date. The customer gets access indefinitely.

**Example:** "Create a lifetime access offer at $299"

* Set the price. No billing interval needed
* Also covers standalone product purchases (line items) with no ongoing access

## Recurring volume

Tiered pricing based on quantity purchased. Each tier can charge per unit or a flat fee.

**Example:** "Create a volume-priced plan: 1-10 seats at $10/seat, 11-50 at $8/seat, 51+ at $6/seat, billed monthly"

* Define quantity tiers with start and end units
* Each tier has its own price and pricing format (per-unit or flat fee)
* Set the billing interval for recurring charges

## Usage per unit

Consumption-based billing where the charge depends on actual usage within a period.

**Example:** "Create a metered API plan at $0.05 per call, billed monthly"

* Set the per-unit price
* Set the billing interval for aggregating usage

## Shared options

All pricing types support these additional settings:

* Currency: GBP, USD, EUR, AUD, CAD, and others
* Charge trigger: when the first charge fires (on order date, subscription start, or after a delay)
* Delayed start: a delay before the first charge, such as a 7-day free trial before billing starts
* Fixed start day: start subscriptions on a specific day of the month


---

# 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.limio.com/ai/mcp-server/pricing.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.