> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/plans-and-billing.md). # Plans and billing - [Billing](https://help.felt.com/plans-and-billing/billing.md): Manage your Felt plan, free trial, payments, and invoices. Learn how to upgrade or cancel and what happens when a trial or plan ends. - [Seats and viewers](https://help.felt.com/plans-and-billing/seats-and-viewers.md): Learn who needs a seat and what viewers can do for free. Add or reassign seats in your Felt workspace. - [Plan usage](https://help.felt.com/plans-and-billing/plan-usage.md): Track map views, processing, storage, and Felt AI credits. Learn what counts toward usage limits and what happens when you reach them. - [Free plan](https://help.felt.com/plans-and-billing/free-plan.md): Learn what Felt's Free plan includes and when you need a paid plan. See what happens to your maps and data after a trial ends. - [For classrooms](https://help.felt.com/plans-and-billing/for-classrooms.md): Apply for Felt's free Classroom plan for higher education. Set up a class workspace and invite students to create and share maps. - [For nonprofits](https://help.felt.com/plans-and-billing/for-nonprofits.md): Learn who qualifies for Felt's nonprofit discount, what it covers, and how to apply. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.felt.com/plans-and-billing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.