The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 20, 2026 11:34pm

PR Summary

Medium Risk
Medium risk because it changes hosted-key injection/billing behavior and adds new Fal.ai cost-tracking network calls that affect pricing, rate limiting, and tool responses.

Overview
Adds hosted-key support for Fal.ai image/video generation with cost tracking: the image/video proxy routes optionally fetch Fal.ai billing/price estimates and return __falaiCostDollars/__falaiBilling, while the Fal.ai tools apply a markup-based custom pricing model and send useHostedCostTracking when running on hosted keys.

Updates the hosted-key injector to skip injection when a tool’s hosting predicate is false or when the user already supplied an API key, and adds Fal.ai to BYOK provider IDs/UI.

Improves Cmd-K search by introducing commandSearchable subblocks and indexing marked dropdown/combobox options into each block’s searchValue; also hardens the add-block toolbar event typing/validation and refreshes search data when provider models change.

Retires Vision from surfaced UI/docs by removing the vision docs/integration entry and hiding vision_v2 from the toolbar, plus minor Azure DevOps docs output clarifications.

^{Reviewed by Cursor Bugbot for commit 3c7fd57. Configure here.}

Greptile Summary

This PR retires the Vision block (hidden from toolbar), adds Fal.ai hosted-key support for image and video generators with markup-based billing, and enables provider dropdown options to appear as Cmd-K search entries via a new commandSearchable flag on SubBlockConfig.

• Hosted-key billing for Fal.ai: getFalAICostMetadata polls the billing-events API (2 attempts, 500 ms apart) then falls back to a historical-estimate endpoint, and finally to a hard-coded floor — it never throws, so generated content is never lost due to cost-lookup failure. The markup multiplier (1.5×) is applied in each tool's getCost function.
• Dual apiKey subblocks: both image and video generator blocks now carry two apiKey subblocks sharing the same id — one with hideWhenHosted: true scoped to the falai provider, and one for all other providers — so the block UI hides the key field in hosted mode only when Fal.ai is selected.
• commandSearchable search indexing: provider labels and IDs from any subblock marked commandSearchable are folded into the block's searchValue at store-initialization time, letting users find blocks by provider name (e.g., "Fal.ai", "OpenAI") in Cmd-K.

Confidence Score: 5/5

Safe to merge — the cost-tracking chain is robust end-to-end and no generated content can be lost due to pricing-lookup failures.

The three-tier fallback in getFalAICostMetadata (billing events → historical estimate → floor) ensures the billing path never propagates an exception to callers. The hosted-key injection correctly checks the enabled predicate, respects user-provided and BYOK keys, and gates cost tracking via __usingHostedKey. Dual apiKey subblock IDs are an intentional, mutually-exclusive conditional pattern consistent with how other blocks handle provider-scoped fields.

The fallback-floor cost heuristic in falai-pricing.ts and the defensive throws in image/generate.ts and video/falai.ts are worth a second look if Fal.ai adds new endpoint families in the future.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Block as Image/Video Block
    participant Index as tools/index.ts
    participant Route as API Route
    participant FalAI as fal.ai
    participant Pricing as falai-pricing.ts
    participant Billing as Billing System

    Block->>Index: "execute(params, provider=falai)"
    Index->>Index: injectHostedKeyIfNeeded
    Index->>Route: POST api/tools/image or video
    Route->>FalAI: generate(model, prompt)
    FalAI-->>Route: result + requestId
    Route->>Pricing: getFalAICostMetadata
    Pricing->>FalAI: GET billing-events (2 attempts)
    alt billing event found
        FalAI-->>Pricing: cost_estimate_nano_usd
        Pricing-->>Route: "source=billing_events"
    else no event
        Pricing->>FalAI: POST pricing/estimate
        alt estimate ok
            FalAI-->>Pricing: total_cost
            Pricing-->>Route: "source=historical_estimate"
        else estimate fails
            Pricing-->>Route: "source=fallback_floor"
        end
    end
    Route-->>Index: response with costDollars
    Index->>Billing: getCost with 1.5x markup
    Billing-->>Index: billing recorded

_{Reviews (2): Last reviewed commit: "address comments" | Re-trigger Greptile}

@greptile

bugbot run