Billing Tab

The Billing tab is your spending dashboard. Every AI generation is logged with its cost, model, timestamp, and project attribution. Filter by project, export CSV, generate HTML reports, and import external AI costs — all from one panel.

If you work with clients, this is your paper trail. Every generation is tagged to the client and project you choose. Export as HTML report to include in client deliverables or internal cost reviews.

Generation History

The history shows every generation as an individual entry with:

Model name — which model produced the result
Timestamp — when the generation ran
Cost — the amount for that run: the measured figure once fal.ai reports usage modelBridge can price, otherwise modelBridge’s own calculation
Metered cost — provider-reported usage units × modelBridge rate when available. A metered row carries no badge: the bare amount is the measured one, and every less certain figure is badged. A run fal.ai reported usage for in a unit modelBridge cannot price gets a red “Charged, amount unknown” badge with fal.ai’s count; it counts as spend with no amount. A run that was charged but never delivered gets a red badge — “Metered (failed run)” where fal.ai reported usage, “Calculated (failed run)” where it reported only that the run finished
Client / Project — tags if assigned
Deliverable — tag if assigned

Pagination

The initial view shows 4 entries — enough to confirm tracking is working without overwhelming the narrow panel. Click View more to load 10 additional entries. Hide collapses back to the initial 4.

Running Totals

A running total at the top shows your cumulative AI spending. This updates as new generations complete and adjusts when fal.ai reports the billing units for each charge. When some generations have no pricing data at all, the total shows a ≥ sign — the actual amount may be higher.

Client and Project Tagging

Tag generations with a client and project using the combo picker in the Generate tab. The Billing tab uses these tags for filtering:

Project chips — click any project chip to filter the history to that project only
Client grouping — costs are groupable by client for invoicing

Tags are autocompleted from previously used values as you type. This keeps naming consistent across generations.

Deliverable Tagging

Each generation can also be tagged with a deliverable name — “Hero Film”, “Social Cut”, “BTS Reel”. This enables cost-by-deliverable breakdowns in reports.

The Deliverable field appears in the Generate tab as an autocomplete text input. Previously used deliverable names are suggested as you type.

Currency Switching

Switch between USD, EUR, GBP, SEK, NOK, DKK, JPY, CAD, and AUD using the currency dropdown. Exchange rates are updated daily. The selected currency applies to:

Pre-generation cost estimates
Billing tab totals and per-entry costs
HTML reports and CSV exports

SEK values show one decimal place (5.1 kr) for meaningful precision at low amounts.

CSV Export

Click the export button to download your full cost history as a CSV file. The export includes:

Timestamp (start and completion)
Model name and category
estimated_cost and cost (the amount shown)
cost_source (metered / calculated / estimated / charged_unknown / no_price)
provider_units, provider_unit_type and provider_unit_rate — the provider’s reported usage, in the provider’s own word for the unit (seconds, 1000 tokens, compute seconds) and the rate modelBridge holds for it. The unit column is blank when fal.ai did not name a unit for that run
cost_note — a short plain-language basis for the number
Client, project, and deliverable tags
Currency and exchange rate
Generation parameters, prompt, and request ID

The file opens with a # schema_version: line — currently 5 — so a parser can tell which column layout it is reading. Use this for invoicing, expense tracking, or importing into accounting software. Every row includes its cost source, so you can distinguish measured charges from formula figures at a glance.

HTML Report Generator

Generate self-contained HTML reports for client billing and compliance documentation. Each report is a standalone .html file that works in any browser, on any machine, without an internet connection.

What the Report Contains

Four KPIs at the top:

Total AI cost (internal fal.ai generations)
External AI costs (imported from CSV)
Combined total
Number of generations

Charts and breakdowns:

Cost by model (bar chart) — which models drive spending
Cost by deliverable (bar chart) — costs per deliverable tag
Cost over time (line chart) — spending trends across the project
Full generation log table with all entries

Compliance badge — visual indicator confirming the report was generated from tracked data, with commercial license status per model.

Reports are generated with one click from the Billing tab.

External AI Costs

Import costs from other AI tools (Midjourney, RunwayML, ElevenLabs, ChatGPT, etc.) via CSV to get a unified view of total AI spending.

How to Import

Prepare a CSV with columns for date, description, amount, and category
Open the Billing tab and use the import function
External costs appear alongside internal generations

Cost Types

Type	Source	How It Appears
Internal	fal.ai generations tracked automatically	Standard entries with model name and parameters
External	Imported via CSV	Marked as external with source tool name

External costs are included in running totals, reports, and KPI calculations.

Post-Generation Metered Costs

When fal.ai reports usage units after a generation — and modelBridge can price them at fal.ai’s own rate — the Billing row shows the Metered cost: the units fal.ai reported × fal.ai’s rate for them. Otherwise the entry shows Calculated — the same forecast formula, applied to the settings that ran — or Charged, amount unknown where fal.ai reported usage in a unit with no rate modelBridge can apply. The CSV export’s estimated_cost column carries modelBridge’s formula figure for the settings that ran, recomputed at completion — not the number shown before you clicked; the row itself shows one amount. This lets you:

Compare the formula figure with the metered amount, row by row, in the export
Spot discrepancies between estimated and metered costs
Build confidence in the cost estimation system
See exactly how each cost was determined from the label on each row — or its absence, which marks a measured one

After generation, the cost badge settles to a muted Metered label — expand the COST section for the amount, immediate feedback without switching tabs.

Data Persistence

Cost history uses dual persistence — localStorage for fast reads and a disk file for durability. Your cost data survives:

Premiere Pro updates
CEP cache clears
Plugin updates and reinstalls

The Billing tab includes a manual Reset function requiring you to type “DELETE” as confirmation. This is the only way to clear cost history — it never happens accidentally.