# User tokens expiring too quick

**URL:** <https://community.pickaxe.co/t/user-tokens-expiring-too-quick/7580>\
**Category:** General\
**Tags:** studio\
**Created:** [November 19, 2025, 2:40am UTC](https://community.pickaxe.co/t/user-tokens-expiring-too-quick/7580 "2025-11-19T02:40:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dougfresh](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/dougfresh/32/1885_2.png) [@dougfresh](https://community.pickaxe.co/u/dougfresh)\
**Post date:** [November 19, 2025, 2:40am UTC](https://community.pickaxe.co/t/user-tokens-expiring-too-quick/7580/1 "2025-11-19T02:40:54Z")

</div>

I have a SaaS with subscribers. One of my users has all of their credits (300) gone just 3 days into his billing cycle. He typically uses about that many in a month. How can I track down this issue?  
I cant see individual usage reports in the users section.

---

<div class="post-metadata">

**Author:** ![abhi](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/abhi/32/5009_2.png) [@abhi](https://community.pickaxe.co/u/abhi)\
**Post date:** [November 19, 2025, 3:40am UTC](https://community.pickaxe.co/t/user-tokens-expiring-too-quick/7580/2 "2025-11-19T03:40:51Z")

</div>

Hi @dougfresh,  
Thanks for the question, and I’m happy to help you sort this out.

One quick clarification that will help me point you in the right direction:  
When you say the user burned through 300 credits, are you referring to **your end user inside your Studio** (where 1 credit equals 1 use), or are you referring to **your own Studio-owner credits** , which are token-based on the backend?

The two systems behave very differently:

• **End-user credits** work on a simple 1 credit = 1 use model.  
• **Studio-owner credits** follow OpenAI/Anthropic/Google token usage, so cost can vary depending on the model and how long the responses are.

If you can confirm which bucket this situation falls into, I can walk you through exactly where to check the logs and what might be causing the spike.

---

<div class="post-metadata">

**Author:** ![dougfresh](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/dougfresh/32/1885_2.png) [@dougfresh](https://community.pickaxe.co/u/dougfresh)\
**Post date:** [November 19, 2025, 1:12pm UTC](https://community.pickaxe.co/t/user-tokens-expiring-too-quick/7580/3 "2025-11-19T13:12:46Z")

</div>

Hi! I am referring to my end user inside my studio.

---

<div class="post-metadata">

**Author:** ![abhi](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/abhi/32/5009_2.png) [@abhi](https://community.pickaxe.co/u/abhi)\
**Post date:** [November 19, 2025, 7:27pm UTC](https://community.pickaxe.co/t/user-tokens-expiring-too-quick/7580/4 "2025-11-19T19:27:50Z")

</div>

> [@dougfresh](#):
>
> Hi! I am referring to my end user inside my studio.

thanks for confirming this is happening inside your Studio. I really want to help you get this sorted.

It could be a combination of things causing the spike, so the best next step is for you to email us at **[info@pickaxeproject.com](mailto:info@pickaxeproject.com)** with your **Studio link** and the **specific user** affected. Once we have that, we can take a deeper look at the setup and pinpoint what’s driving the credit use.

From there, I can also share the best ways to optimize credit usage based on what we find.

Happy to help you get this under control quickly.