Service accounts in Fireworks allow applications, scripts, and automated systems to authenticate and perform actions securely—without relying on human credentials. They are ideal for CI/CD pipelines, backend services, and automated workflows. Service Accounts let you avoid shared credentials and easily distinguish between what automated systems did vs humans in audit logs. Service accounts can take actions using an API key, like creating deployments, running models or creating datasets (see API reference). Service accounts cannot login through the web interface or use OIDC tokens. To manage service accounts via the Fireworks web UI visit app.fireworks.ai/account/users.Documentation Index
Fetch the complete documentation index at: https://docs.fireworks.ai/llms.txt
Use this file to discover all available pages before exploring further.
Creating a Service Account
Using our firectl you can create service accountsCreating an API Key for a Service Account
Using firectl you can create an API key on behalf of a service account:Roles
You can assign a role when creating a service account using the--role flag:
user.
To change the role of an existing service account, use the update command:
Listing Service Accounts
To list all service accounts in your account:Billing
- Service accounts count toward the same account quotas and limits assigned to the account
- Usage is tracked by the account, not individual user vs service account
Auditing
In audit logs users are referenced by their email id’s. Service accounts are referenced bymy-service-account@my-account.sa.fireworks.ai.