TokenFront Help

Appearance

Connecting Fireworks AI ​

What you need ​

Two things from your Fireworks account: an API Key, and your Account ID. Fireworks doesn't offer a separate read-only key type — like Vercel AI Gateway, this key can both read usage data and make real, billable inference calls. Create a key specifically for TokenFront rather than reusing one already wired into a production app, so it's easy to revoke independently.

The key must belong to an Admin of the Fireworks account. Fireworks only shows account-wide costs to Admins, so a key created by a User, Contributor or Inference User is rejected. If you'd rather not tie the key to a person, an Admin can create a service account with the Admin role and a key for it using firectl:

bash
firectl user create --user-id tokenfront --service-account --role=admin
firectl api-key create --service-account=tokenfront --key-name=TokenFront

Step 1: Create an API key in Fireworks ​

  1. Go to Fireworks → API Keys.
  2. Click Create API key.
  3. Give it a name you'll recognize later — "TokenFront" works.
  4. Copy the key.
  5. Find your Account ID in the account switcher at the top of the dashboard. It looks like yourname-44ace8 — a short name followed by a random suffix, not a plain username.

Step 2: Add both to TokenFront ​

  1. Open Connect Fireworks AI in TokenFront.
  2. Paste the key into the API key field, and your Account ID into the Account ID field.
  3. Save.

Both fields are required — Fireworks' usage API is scoped to a specific account, not just to whichever key is calling it, so TokenFront can't look anything up without the Account ID.

How much history comes in ​

About 100 days on the first sync, not your plan's full history window like other platforms. That's a limit on Fireworks' side, not something TokenFront can pull further back on. Once connected, TokenFront keeps what it has collected, so your history grows from there.

If the connection shows "Key rejected" ​

Double-check both the key and the Account ID under Edit — a valid key paired with the wrong Account ID will fail the same way an invalid key does. Also check that the key's owner is an Admin on that Fireworks account: a key from any other role is rejected even when both values are right.

More about Fireworks AI in TokenFront ​

What TokenFront shows for Fireworks AI, and how it fits with your other providers: Fireworks AI on tokenfront.io.