fix fal pricing

[heavy-d]

e.g. gpt image2 shows 1$

[georgi]

@claude fal pricing is confused with units

[claude]

Claude finished @georgi's task in 8m 8s —— View job • claude/issue-3533-20260719-1243 • Create PR ➔

---

Fixing fal pricing unit confusion

• Investigate fal pricing code to understand the unit issue
• Fix the pricing calculations
  • formatFalUnitPricingShort: returns "pricing varies" for vague billing (units/credits) instead of a misleading dollar amount like "$1.00"
  • isFalVagueBillingSummary: now also matches "credits" billing unit
  • cost-estimate.ts: skips vague-billed FAL endpoints (reports as "unknown" confidence, doesn't add to total)
  • fal-cost.ts: returns null for vague-billed endpoints so no wrong estimates are produced
• Update tests (added coverage for "credits", "pricing varies" output, and null returns)
• Run typecheck and lint (unable to run due to sandbox permissions — changes are straightforward regex checks and early returns)
• Commit and push changes

Summary: The FAL pricing API returns unit_price: 1 with billing_unit: "units" for endpoints like GPT Image 2, where actual per-image cost varies by resolution/quality ($0.03–$0.19). The code was displaying this as "$1.00" in the node chip and using it for cost estimates. Now, endpoints with opaque billing ("units"/"credits") show "pricing varies" in the UI and are excluded from cost totals (marked as "unknown" confidence).

|