{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidni7oltij4niyrpxt75x7exk3kazqvr2pzpb5jw23klmgib4jpfe",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mk2yrevxsne2"
  },
  "path": "/t/issue-with-omni-editor-free-credits-exceeded-despite-pro-account-and-available-credits/175453#post_4",
  "publishedAt": "2026-04-22T05:59:16.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "Spaces Overview · Hugging Face",
    "Issue with Omni Editor: “Free credits exceeded” despite Pro account and available credits",
    "selfit-camera/Omni-Image-Editor · Discussions",
    "https://huggingface.co/spaces/selfit-camera/Omni-Image-Editor/discussions/35",
    "https://huggingface.co/spaces/selfit-camera/Omni-Image-Editor/discussions/33"
  ],
  "textContent": "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**.\nBelow is by LLM:\n\n* * *\n\nAccording 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.\n\nAlso, 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.\n\nSo 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.\n\nRelevant references:\n\n  * HF Spaces docs (variables and secrets / duplication behavior): Spaces Overview · Hugging Face\n  * This forum thread: Issue with Omni Editor: “Free credits exceeded” despite Pro account and available credits\n  * Space discussions: selfit-camera/Omni-Image-Editor · Discussions\n  * “API KEY Limitations”: https://huggingface.co/spaces/selfit-camera/Omni-Image-Editor/discussions/35\n  * “please login”: https://huggingface.co/spaces/selfit-camera/Omni-Image-Editor/discussions/33\n\n",
  "title": "Issue with Omni Editor: “Free credits exceeded” despite Pro account and available credits"
}