Per-app credit analytics and integrated credit usage reporting

Per-app credit analytics and integrated credit usage reporting in Base44 isn’t a “nice to have” — it’s essential for anyone running multiple apps and integrations at scale.

Right now, credit consumption feels like a black box. As a power user, that’s genuinely frustrating because when credits spike (or we hit limits), there’s no clear way to answer basic questions without contacting support:

• Which app is consuming the credits?

• Which integration is driving the increase?

• What changed (volume, payload size, retries, errors)?

• What’s the cost per request / per workflow / per endpoint?

• Are we paying for failed calls, loops, or misconfigured automations?

Without this visibility, credit management becomes a free-for-all. It makes budgeting impossible, slows down decision-making, and creates unnecessary support tickets just to diagnose usage.

What we need is straightforward:

• Per-app breakdown of credits used (with trends over time)

• Per-integration breakdown (e.g., Stripe, GA4, email, webhooks, etc.)

• Granular request-level insight (credits per request, endpoint/action, success vs failure)

• Limits & controls (ability to cap, restrict, or disable credit-heavy integrations per app/workspace)

• Alerts for abnormal spikes and approaching thresholds

This would massively improve control, reduce wasted spend from misfires/loops, and remove the constant back-and-forth with support just to understand what’s happening.