> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/product-catalog/add-ons.md).

# Add-ons

Bunny supports two types of add-ons:

* **Plan add-ons** – These are basically separate products, such as VIP support
* **Feature add-ons** – Think of these as micro upsells on a plan, such as custom fields, higher API rate limits etc.

Plan adds are basically plans that can be added to an existing subscription if certain plans are already being subscribed to. And they can be just as complex as regular plans, with multiple charges, one-time, recurring and usage-based.

### Plan add-ons

Plan add-ons are depending on another plan being subscribed to and cannot be subscribed to alone.

To make a plan an add-on, select the **Add on** toggle on the form and then select that plans it can be an add-on for via the **Compatible plans** drop-down.

<figure><img src="/files/kmNEx7ophcZHLOBdmaJy" alt=""><figcaption></figcaption></figure>

### Feature add-ons

Feature add-ons are basically optional charges that exist along with regular charges on a plan. View them as micro upsells that are easy for both customers and salespeople to enable on a plan.

In the price list charge for, use the **Feature add-on** toggle to make a charge optional.

<figure><img src="/files/1jGm6S7yQv6uTsSpnGaR" alt="" width="563"><figcaption></figcaption></figure>

In the customer portal, they will appear as little toggles that the customer can use to turn on.

<figure><img src="/files/9J6O1K5cTJMmJbDa49P0" alt="" width="375"><figcaption></figcaption></figure>

On a quote, they will look like regular line items with a toggle.


---

# 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.bunny.com/guide/tour/product-catalog/add-ons.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.