A RichAPI workspace is a team account. The workspace holds the API keys, the usage history, and the members. The credit balance belongs to the organization, and every team in the organization spends from it. Your personal account holds your profile only, and it holds no credits and no API keys. Create a workspace and move between workspaces from the account switcher at the top of the dashboard sidebar.

Every RichAPI user has one personal account. A personal account is your sign-in identity. A workspace is a separate container for API work, and one user belongs to any number of workspaces.

The personal account has one sidebar entry: Home. Every API Platform page lives inside a workspace.

The address https://app.richapi.ai/home is not a page that you stay on. If you belong to one or more workspaces, RichAPI sends you to the first workspace in alphabetical order by name. If you belong to no workspace, RichAPI shows the message You don't have any teams yet. with a Create a Team button.

The workspace holds the API keys. The organization holds the credit balance, and every workspace in it spends from that balance. The personal account holds neither.

CAUTION: Confirm the workspace name in the sidebar before you create an API key. A key created in the wrong workspace spends from the organization balance and counts toward the spend limit and usage history of that workspace. RichAPI cannot move a key or its usage between workspaces.

The button shows Creating Team... while the request runs. RichAPI shows the message Team created successfully and opens the new workspace at /home/<workspace-url>.

If you belong to no workspace, RichAPI opens the Create Team dialog for you on the home page. The field holds a suggested name in the form <your name>'s Team. RichAPI does not open the dialog for you after a single sign-on sign-in. The dialog holds one field.

You become the Owner of the workspace that you create. For the role table, read Managing Workspace Members and Permissions.

The name must contain no special character from this set:

The form rejects a reserved name with the message This name is reserved. Please choose a different one. The form rejects a blocked character with the message This name cannot contain special characters. Please choose a different one.

CAUTION: Use English letters in the workspace name. The create dialog rejects a name with Chinese, Japanese, Korean, Cyrillic, Arabic, Hebrew, or Thai characters. The dialog shows no message for that rejection. For a workspace name in one of those scripts, write to [email protected].

RichAPI grants 100 free trial credits on workspace creation. The grant applies once per user, not once per workspace. The first workspace that you create receives the 100 credits. A later workspace that you create gets no new grant: it joins your organization and spends from the same balance.

A trial credit spends the same way as a purchased credit. One credit costs $0.02, so 100 credits carry a value of $2.00. An organization owner adds credits to the organization balance on the Plans & Billing page, at /home/<workspace-url>/credits.

The workspace name is the label that the dashboard shows. The workspace URL is the address fragment that identifies the workspace. RichAPI builds the URL from the name at creation, and RichAPI builds it again after every rename.

RichAPI applies three steps to the name to build the URL.

If the result already belongs to another workspace, RichAPI adds a number. Two workspaces named Acme receive the URLs acme and acme-1. A third receives acme-2.

Not directly. RichAPI generates the workspace URL from the workspace name, and the URL follows the name. To change the URL, rename the workspace. A rename changes the name and the URL together.

CAUTION: After a rename, open the workspace from the account switcher and save the new link. A rename changes the workspace URL, and a saved link to the old URL stops working. RichAPI sends a request for an unknown workspace URL back to your first workspace.

The dashboard holds no control that sets a workspace URL on its own. When the workspace name holds non-English characters, the workspace settings page shows a Team URL field. That field validates your entry, but the update request does not send it. No entry in that field changes the URL.

These are the rules that RichAPI applies to a workspace URL.

RichAPI applies the same three steps to the new name after a rename. If the new URL already belongs to another workspace, RichAPI adds a number to it.

The account switcher sits at the top of the sidebar, under the RichAPI logo. The control shows the avatar and the name of the current workspace, with an arrow icon at the end. On a small screen, open the menu button first, and the switcher sits at the top of the menu panel. The open panel shows three parts.

A check mark marks the current workspace. A workspace that you left, or a workspace that removed you, does not appear in the list.

The dashboard opens /home/<workspace-url> for that workspace. The sidebar, the API keys, the usage charts, and the member list all change to the new workspace. The credit balance changes only when the new workspace belongs to another organization.

Each row below opens a page of the current workspace. The credit balance and the credit purchase belong to the organization, so they change only when you switch to a workspace in another organization.

A developer belongs to two workspaces in one organization. acme-prod runs production. acme-test runs tests.

The test counts as production usage, because the key belongs to acme-prod. RichAPI cannot move the spend back. Switch to the correct workspace first, and then create the key.

To confirm which workspace a key belongs to, open /home/<workspace-url>/api-keys. The table lists the key name and the first 8 characters of the key.

RichAPI sets no limit. The code that creates a workspace counts no existing workspace and blocks no user. Create as many workspaces as you need.

Two facts apply to every workspace after the first one.

Only the Owner of a workspace can rename it. For every other member, the dashboard disables the field.

A rename changes the label in the account switcher and in the sidebar. A rename also changes the workspace URL, because RichAPI builds the URL from the name. A rename creates no new workspace, and it moves no credit, no key, and no member. For the full settings page, read Workspace Settings, Themes, and Security.

CAUTION: After a rename, open the workspace from the account switcher and save the new link. A saved link to the old URL stops working. The account switcher always holds the current address of every workspace that you belong to.

No. A RichAPI personal account holds your profile, your language, your password, and your multi-factor authentication only. API keys belong to a workspace. Credits belong to the organization.

Select the account switcher at the top of the sidebar, and then select Create a Team. Type a name in the Team Name field, and select Create Team. RichAPI opens the new workspace at once.

RichAPI sets no limit on the number of workspaces that one user creates. Only the first workspace receives the 100 free trial credits. A later workspace gets no new grant and spends from the same organization balance.

Not directly. RichAPI builds the workspace URL from the workspace name, so a rename changes the URL. No field sets the URL on its own, and a saved link to the old URL stops working after a rename.

Yes. Two workspaces in the same organization share one balance. All teams in an organization spend from one balance, and each team can have its own monthly spend limit. Each workspace keeps its own API keys, usage history, and member list.

The address /home sends you to your first workspace in alphabetical order by name. If you belong to no workspace, /home shows You don't have any teams yet. and a Create a Team button.

Read the account switcher at the top of the sidebar. The control shows the name of the current workspace. The address bar shows the same workspace as the fragment after /home/.

Next: Accepting an Invitation to Join a Workspace