Issue with Omni Editor: “Free credits exceeded” despite Pro account and available credits

Beginners
1

​
​"Hello,
​I am writing to report a persistent issue with the Omni Editor Space.
​Despite having a Pro account and a sufficient balance of credits, I am unable to generate images. The interface keeps displaying an error message stating that I have exceeded my free credits.
​This situation has remained unchanged for more than 24 hours now. Could you please look into this or let me know if there is a known synchronization issue between Pro accounts and this specific Space?
​Thank you for your help.
​Best regards,"

2

For now, which Omni Editor???

3

This: Omni Image Editor - a Hugging Face Space by selfit-camera .

4

Hmm… I took a quick look at the publicly available Space files and related pages, and my impression is that this Space probably is not directly using a user’s personal HF token / monthly included credits path. So whether the account is Free or Pro, or whether HF credits are still available, may simply not be the deciding factor here.
Below is by LLM:

According to Hugging Face’s own docs, duplicated Spaces do not automatically inherit secrets; those need to be re-entered manually. So duplicating the Space and setting only HF_TOKEN does not necessarily prove that the duplicate is exercising the same backend path as the original Space.

Also, the publicly visible signals around this Space point more toward a Space-specific auth / backend flow than a straightforward “my HF Pro credits should work here” situation. The Space’s Discussions include threads like “API KEY Limitations” and “please login”, which is the kind of pattern you would expect from a custom auth or backend path rather than a simple per-user HF Inference billing path.

So my current guess is that the main issue here is probably not whether HF monthly included credits are still available on the account, but whether the Space’s own backend, secret-backed configuration, or quota/auth logic changed. If this Space used to work and now it doesn’t, the most plausible next step is probably for the Space author to investigate their backend/auth/quota path, rather than treating this as a normal HF Pro vs Free credits issue.

Relevant references:

5

Specifically, I don’t think the space will work even if someone other than the person who knows the contents of the OneKey (not HF_TOKEN) secret (such as the author) tries to duplicate it.

6

Thank you.