fix(billing): add line items for wand

[waleedlatif1]

Summary

• add line items for wand, were not updating billing info beforehand

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
docs	Skipped		Dec 23, 2025 6:37am

[greptile-apps]

Greptile Summary

Fixed missing billing line items for wand usage by refactoring updateUserStatsForWand to accept userId directly from the session instead of looking it up via workflowId.

Key changes:

• Function signature changed from accepting workflowId to accepting userId directly
• Removed database query to look up user from workflow (lines 91-104 in old version)
• Removed workspaceId and workflowId parameters from logModelUsage call since wand usage isn't tied to specific workflows
• Now billing works correctly for all wand invocations, not just those with a workflowId

Impact:

• Previously, billing line items were not created when wand was used without a workflowId (which is the common case from the use-wand hook)
• Now billing properly tracks all wand usage since session.user.id is always available

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The change is a straightforward bug fix that removes unnecessary database queries and uses data already available in the session. The logic is cleaner and more reliable since it doesn't depend on the optional workflowId parameter.
• No files require special attention

Important Files Changed

Filename	Overview
apps/sim/app/api/wand/route.ts	Simplifies billing by using session user ID directly instead of looking up via workflowId - fixes missing line items for wand usage

Sequence Diagram

sequenceDiagram
    participant Client as Wand Client
    participant API as /api/wand
    participant Session as getSession()
    participant Stats as userStats (DB)
    participant Log as usageLog (DB)
    participant Billing as checkAndBillOverageThreshold
    
    Client->>API: POST /api/wand<br/>(prompt, stream, history)
    API->>Session: Get authenticated user
    Session-->>API: session.user.id
    
    alt Streaming Mode
        API->>API: Stream OpenAI response
        API->>API: Collect usage data
        Note over API: When [DONE] received
        API->>API: updateUserStatsForWand(session.user.id, usage)
    else Non-Streaming Mode
        API->>API: Call OpenAI completion
        API->>API: updateUserStatsForWand(session.user.id, usage)
    end
    
    Note over API: updateUserStatsForWand flow
    API->>Stats: Update totalTokensUsed,<br/>totalCost, currentPeriodCost
    API->>Log: logModelUsage(userId, source='wand',<br/>model, tokens, cost)
    API->>Billing: checkAndBillOverageThreshold(userId)
    
    API-->>Client: Return generated content

Loading

[greptile-apps]

Additional Comments (1)

1. apps/sim/app/api/wand/route.ts, line 127-134 (link)

   style: removed workspaceId and workflowId from billing attribution - these are still available in scope (from lines 163 and 174-178) and could be useful for tracking usage by workspace/workflow

   was removing workspace/workflow attribution intentional for simplification, or should we preserve this for better usage tracking?

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[waleedlatif1]

@greptile