Who Pays Credits When I Open an Interactive Artifact?

The person opening the interactive artifact pays the credits, not the person who created it. Each time the artifact loads or refreshes, a Python sandbox runs to fetch your live data, and you're billed roughly 1 credit per 55 seconds of execution (minimum 1 credit per load).

What Counts as an Interactive Artifact?

An interactive artifact is an HTML file your agent generated that pulls live data from your connected integrations every time you open it. Examples: a Slack dashboard, a "today's calendar" tool, a Linear issue tracker that always shows the latest.

This is different from a regular HTML artifact, which is a static snapshot from when the agent ran and doesn't cost credits to view.

Who Pays the Credits

• The viewer always pays. When you open an interactive artifact — whether you created it or someone shared it with you — the credits come out of your credit account.

• The creator is not charged when someone else opens their artifact.

• If a teammate shares a dashboard with five people, each of those five people pays for their own data loads when they open it.

This works the same way as credit billing for shared agents: the person triggering the work pays for it.

How the Charge Is Calculated

Every time the artifact loads (or auto-refreshes), Gumloop runs the data script in a secure sandbox. The cost is based on how long the script ran:

• About 1 credit per 55 seconds of sandbox execution time.

• Minimum 1 credit per execution, even for scripts that finish in under a second.

• Most data scripts finish in a few seconds, so a typical artifact load costs just 1 credit.

You can see the charges in your usage dashboard alongside your other agent credits.

What Triggers a New Charge

A new sandbox execution (and a new credit charge) happens every time the artifact runs its data script:

• You open the artifact for the first time.

• You refresh the page or close and reopen the artifact.

• The artifact has a built-in refresh button or auto-refresh timer that triggers a reload.

• You re-approve the integration consent overlay (per-session).

Each execution runs in a fresh sandbox — no state carries over between refreshes — and has a 5-minute timeout.

What Happens if You Run Out of Credits

If your credit balance hits zero, the artifact's data script won't run. You'll see an error in the artifact and the data sections will be blank or show a "credit limit exceeded" message.

To get going again, top up your credits. See How Do I Get More Credits Without Enabling Overages? or check your usage notifications setup in How Do Credit Usage Notifications Work?

How to Keep Credit Costs Low

• Be specific in your prompts. Ask the agent to only pull the data you actually need (one channel instead of all channels, today's events instead of the whole month). Shorter scripts = lower cost.

• Skip auto-refresh when you don't need it. If you only want to glance at a dashboard once, tell the agent not to add an auto-refresh timer.

• Use a static artifact when live data isn't needed. If the data only needs to reflect "when the agent ran," ask for a regular HTML report instead of an interactive one. Static HTML artifacts are free to view.

Related KB Articles

• Who Gets Charged Credits When Someone Uses a Shared Agent?

• How Do I Get More Credits Without Enabling Overages?

• How Do Credit Usage Notifications Work?

Related Docs

• Interactive Artifacts (Live Data)

• Credits — Overview

Still Need Help?

If you see unexpected credit charges from interactive artifacts, check your usage dashboard for the per-execution log. If something looks wrong, reach out to support@gumloop.com.