# Legacy pricing

We’ve [updated our pricing model](https://www.gitbook.com/blog/new-site-sections#new-pricing-for-new-users) recently, to accommodate for many of the new features we’ve been releasing for published sites. Because of this, there is a chance you may still be on our old pricing model.

Some of the new features we are releasing are only available on our updated pricing plans. Please [contact support](https://gitbook.com/docs/help-center/support/how-do-i-contact-support) if you would like to learn more and upgrade your pricing.

You can [view our current plans](https://gitbook.com/docs/account-management/plans) here.

### Updated pricing

We've made some changes to our plans to simplify publishing and better align features with site plans. Here's a summary:

* **Pro Plan**: No longer includes a monthly platform fee. You can purchase and publish sites without restrictions, even on the Free plan.
* **Organization Plan**: Now focused exclusively on collaboration.

**Features Now Tied to Site Plans**

| **Feature**             | **Plan Required**   |
| ----------------------- | ------------------- |
| AI Search               | Ultimate            |
| PDF Export              | Premium or Ultimate |
| Search Insights         | Premium or Ultimate |
| Custom Domains          | Premium or Ultimate |
| Page Ratings/Feedback   | Premium or Ultimate |
| Advanced Customizations | Premium or Ultimate |
| Unlisted Visibility     | Premium or Ultimate |
| Shared Links            | Premium or Ultimate |
| Authenticated Access    | Ultimate            |
| Site Redirects          | Premium or Ultimate |
| Site Sections           | Ultimate            |


---

# Agent Instructions: 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:

```
GET https://gitbook.com/docs/account-management/plans/legacy-plans.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.