copy changes - rename API credits to extra credits #409
Conversation
Updates user-facing terminology from "API credits" to "extra credits" to better reflect their purpose as overflow credits that extend usage when plan credits run out.
📝 WalkthroughWalkthroughThis pull request updates user-facing text across six frontend billing and pricing components, systematically replacing "API credits" terminology with "extra credits" in labels, messages, buttons, and FAQ items. No functional logic or control flow changes are introduced. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Greptile OverviewGreptile SummaryThis PR renames "API credits" to "extra credits" throughout the frontend UI to better communicate their purpose and reduce user confusion. Key Changes
AnalysisThe changes are purely cosmetic - only user-facing string literals were modified. No logic, API contracts, or data structures were changed. The underlying backend still uses The PR description provides strong justification for this change: the term "API credits" created a mental model mismatch where users expected these credits to be consumed during API calls, when in reality they serve as overflow credits consumed last (after plan credits) for both chat and API usage. All changes follow a consistent pattern and appear complete across the UI surface area reviewed. Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant User
participant UI as UI Components
participant BillingService
participant Backend
Note over User,Backend: Credit Purchase Flow (Terminology Update)
User->>UI: Views credit balance
UI->>UI: Display "Extra Credit Balance"
User->>UI: Clicks "Buy Extra Credits"
UI->>BillingService: purchaseApiCredits()
BillingService->>Backend: POST /api/credits/purchase
Backend-->>BillingService: checkout_url
BillingService-->>UI: Redirect to checkout
Note over User,Backend: After successful payment
User->>UI: Returns to app
UI->>BillingService: getApiCreditBalance()
BillingService->>Backend: GET /api/credits/balance
Backend-->>BillingService: { balance: updated_amount }
BillingService-->>UI: Updated balance
UI->>UI: Display "+ X extra credits"
Note over User,Backend: Usage Limit Reached
User->>UI: Attempts to chat (plan credits exhausted)
UI->>UI: Show UpgradePromptDialog
UI->>UI: Display "Purchase extra credits to continue"
User->>UI: Clicks "Buy Extra Credits"
UI->>BillingService: Navigate to credit purchase
|
Summary
Renames "API credits" to "extra credits" throughout the UI to better communicate their
purpose.
Problem
The term "API credits" may be confusing, especially for developers who use both the Maple
chat interface and the Maple API:
they're actually consumed last—plan credits are used first for both chat AND API usage
credits that kick in when plan credits run out
"API credits" remain unchanged—the opposite of what the name suggests
Solution
Rename to "extra credits" which more accurately describes their behavior:
This aligns with how Claude handles a similar concept with "Extra usage" in their billing
UI—neutral terminology that communicates "this kicks in when you exceed your plan."
Changes
Summary by CodeRabbit