Skip to main content
A service account is a non-human user with its own API keys. Use one for an LLM gateway, a CI pipeline, or a backend service, so the key keeps working when people leave and audit logs show which calls were automated.
  • Any member can create a service account and its keys. You don’t need to be an admin.
  • Service accounts cannot sign in to nexus.fireworks.ai.
Service accounts are managed under API Keys in Nexus settings, not on the Members page. The app.fireworks.ai/account/users path in the Platform docs does not exist in Nexus.

​
Create a service account and its key

Open API Keys

Go to Settings → API Keys and click Create API key.

Add a service account

Under Service Account API Keys, click + to add a service account, and give it a name, such as prod-litellm.

Create the key

Select the new service account and create its key. Copy the fw_... key right away and store it in your secret manager. The API Keys page doesn’t list service account keys, so you can’t find or copy it there later.
To add another key later, for example to rotate one, repeat these steps and pick the existing service account in step 2.

​
Set a role or script it with firectl

Use firectl to choose a role when you create the account, change a role, or list service accounts:
If you leave out --role, the role is user. See User roles for each role’s permissions.

​
Billing and audit logs

  • Service account usage counts toward your account’s quotas and bill, like a member’s usage.
  • Spend limits apply to service accounts the same way they apply to members. Check the limit before a gateway or pipeline depends on the key.
  • Audit logs show a service account as <user-id>@<account-id>.sa.fireworks.ai.