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

# Projects

Projects in FastRouter.ai provide a structure for specifying access and limits for keys used.

### Projects Overview

Projects in FastRouter.ai provide a structure for organizing activity within your organization. Each project is independently configurable and managed, giving teams control over resources, permissions, and integrations.

{% embed url="<https://youtu.be/NWsP3Zgwoq0>" %}

You can manage the following aspects under **Projects** in FastRouter.ai:

***

### 1. Basic Settings

<figure><img src="https://2466471311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzZfZz8wlCHOmP1FU2BsK%2Fuploads%2FD2aAcNy9VZiJz6C0euzp%2FBasic%20Settings.png?alt=media&amp;token=d67b4cb6-212e-4573-bcba-5b082854d369" alt=""><figcaption></figcaption></figure>

Configure fundamental parameters for your project, such as rate limits, budget controls, and accessible models.

**Fields include:**

* **Project Name**: Identify your project.
* **Models**: Select accessible model families.
* **Tokens Per Minute / Requests Per Minute**: Specify global usage limits for the project.
* **Budget Limit**: (Optional) Toggle to enforce a spending cap for the project.
* **Maximum Budget & Reset Duration**: Set and reset spending limits as desired.

Click **Save** once your configurations are complete.

***

### 2. Members

<figure><img src="https://2466471311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzZfZz8wlCHOmP1FU2BsK%2Fuploads%2FWNvcopMLxuHk1yejv7l6%2FMembers.png?alt=media&amp;token=b53fdb89-15a9-4ba9-b133-7de8d53c8c09" alt=""><figcaption></figcaption></figure>

The **Members** tab lets you manage who can access your project and assign specific roles:

**Roles available:**

* **Project Admin**
  * Manage project settings, members, and API keys.
  * Full control over the project configuration including inviting other members.
* **Project Member**
  * Can create personal API keys based on permissions.

**Note:**\
Organization Owners are automatically **Project Admins** for all projects. Additional admins or members can be added from here as needed.

**To invite members:**

1. Click **Invite Member**.
2. Select the organization member and assign the appropriate role.
3. Click **Invite**.

***

### 3. Keys

<figure><img src="https://2466471311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzZfZz8wlCHOmP1FU2BsK%2Fuploads%2Fq35N5hg1g1ElG0NXZiLX%2FProject%20Keys.png?alt=media&amp;token=2accef1f-b237-4291-901d-f9696d8a1d40" alt=""><figcaption></figcaption></figure>

API keys in FastRouter.ai allow secure access to model endpoints within a project.

* **Create User Key**: Generate API keys owned by a user to access all models routed by FastRouter.
* **Create Provisioning Key**: Generate provisioning keys that can in turn be used to create manage service account keys programatically.
* **Manage Existing Keys**: Edit or revoke as needed.

***

### Important:

* When a project is made **inactive**, all user keys associated with that project will be **disabled**.
* When a project member is **removed**, any user keys they have created for the project will also be **disabled**.


---

# 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://docs.fastrouter.ai/explore-features/projects.md?ask=<question>&goal=<user_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.
