Fireworks AI
Check available Fireworks model usage and connection requirements. Current billed-total compatibility is not yet verified.
Fireworks AI
Direct API billing — API key + Account ID required
The connection requests model token usage and account billing data through separate Fireworks endpoints. Billing totals are not yet verified against the current response format. Validate returned amounts against Fireworks before using them in a cost report; model token-value estimates are separate from billed costs.
What StackSpend tracks
- Account billing coverage that must be validated before relying on a total
- Token usage broken down by model — prompt (input) and completion (output) tokens per day
- Estimated API-equivalent model value from token usage and list rates; not billed model attribution
- Monitoring and forecast workflows depend on validated source coverage
- Initial history requests up to 90 days where the source and response support it
Prerequisites
- A Fireworks AI account with billing
- An API key (starts with
fw_) with billing access, created in the Fireworks console - Your Fireworks Account ID — it scopes every billing request
Setup
Create an API key
Go to fireworks.ai and open Settings → API Keys. Create an API key with billing access and give it a name such as “StackSpend”. Copy it — it starts with fw_.
Find your Account ID
Your Account ID is the account slug shown in your fireworks.ai/account/… URL and on the account settings page. StackSpend needs it because every Fireworks billing endpoint is scoped to a specific account.
Add to StackSpend
Go to Providers → Add provider → Fireworks AI:
Add Fireworks AI provider
An API key with billing access from the Fireworks console
The account slug from your fireworks.ai/account/… URL
Verify sync
Confirm a successful sync and the dates returned. Compare nonempty account amounts with the Fireworks console before relying on billed totals. Reporting delay and response compatibility determine what is available; no same-day detection guarantee is made.
Data summary
| Attribute | Value |
|---|---|
| Data freshness | Provider reporting plus scheduled sync |
| Billed cost | Not yet verified; validate response compatibility |
| Token usage | Per model (input / output) |
| Historical data | Requested where available; validate returned dates |
| Setup time | 3 min |
Frequently asked questions
Are Fireworks per-model costs actual billed dollars?
Model-level dollar values based on token usage and list prices are estimates. Validate the returned account billing response separately before using a billed total; current compatibility and completeness need to be checked.
What credentials are needed?
Use a billing-capable API key and the Fireworks Account ID documented for the connection. Confirm the key can access the required billing data before saving it.
How do I investigate a higher Fireworks bill?
First confirm nonempty amounts and the expected period against Fireworks. Then inspect available model usage and price assumptions. Do not use an empty or unvalidated billing response as evidence of zero spend.