Who Gets Charged Credits When Someone Uses a Shared Agent?
Last updated: May 14, 2026
Credits are pulled from your organization's shared credit pool — no matter who in your org chats with the agent. The agent owner is not specifically charged. The only exception is when you share an agent with someone outside your org — in that case, their messages are billed to their own account.
Inside Your Organization
Every Gumloop org has one shared credit pool. Whenever anyone in your org uses a shared agent — via web chat, Slack, or API — credits are deducted from that pool. It doesn't matter who created or shared the agent.
Per-user credit caps (set by org admins in permission groups) limit how much any single person can spend, but the credits themselves still come from the org pool.
External Users
If you share an agent with someone outside your organization, their usage is billed to their own account (or their org's pool) — not yours. See How Do I Share an Agent or Workflow With Someone Outside My Organization? for setup details.
Slack Workflow Trigger Exception
This article covers agents. If you're running a workflow with a Slack trigger (not an agent deployed via Add to Slack), credits go to the trigger owner, not the person who sent the Slack message.
Still Need Help?
If this didn't resolve your issue, reach out to support at support@gumloop.com.
Related Docs
Credits — How credits are calculated and charged
Share Permissions — Sharing roles and General Access settings