Clone Support
GuideTeam Studio · Studio Max

How credits work in Clone Studio

What draws on credits in Clone Team Studio and Clone Studio Max, from chat and skill calls to scheduled tasks, research and video, plus where to check usage and what to do when you run low.

Scott BogdanUpdated Nov 15, 20266 min read
Illustration of credits flowing into Clone Studio skills such as chat, scheduled tasks, research and video, with a usage meter showing how much each draws

Clone Studio is usage-based: the work your clones do draws on credits. This guide explains how that works. It covers what uses credits, why some jobs use far more than others, where to check your usage, and what to do when you run low. For a practical list of habits that save credits, see the companion guide, Credits and good habits.

The basics

A clone does its work by running skills: sending email, reading a calendar, searching the web, writing a research report, making a video, building software. Every skill run uses credits. The number depends on two things:

  1. What it uses. Different skills call different systems and models.
  2. How much work it does. Reading 20 emails is a small job. Reading thousands of emails and pulling their attachments is a big one.

Your plan includes a credit allowance for each billing cycle. Your clones draw on it as they work, whether you asked in Chat, a schedule kicked off the work, or another system triggered it.

Team Studio and Studio Max

Clone Team Studio (clone.org) and Clone Studio Max (clone.me) run on the same platform and have the same capabilities (see Clone Studio: the complete guide). Credits work the same way in both: the same kinds of work are light or heavy. Only the screens differ, so billing and usage pages may look different depending on which edition you use.

What draws on credits

Kind of workTypical credit useWhy
Normal chat with your cloneLightShort back-and-forth with little data to read
Searching a knowledge baseLightDocuments are already indexed, so the clone just looks things up
Short, focused scheduled tasksLight per runA narrow job, such as "emails from the last 24 hours"
Skill calls that touch your accounts (email, calendar, CRM)Depends on scopeA few records is small; thousands of records is large
Searching a very large inbox and pulling attachmentsHeavyLots of data to read on every run
Long, complex reports against years of historyHeavyThe clone has to read and reason over a lot
Research reportsHeavyMany searches and sources, plus a designed report
Large coding buildsHeavyBigger builds use more; cost isn't fixed
Video generationHeavy, especially long videosScript, scenes, images, voice, music and an edit

Skill calls

Each time your clone runs a skill, it uses credits. One request in Chat can run several skills. For example, "find every customer who hasn't replied in two weeks and draft a check-in for each" searches email, may check the CRM, then writes drafts. The Execution Log lists every skill that ran, so you can see what a request actually did.

Scheduled tasks

A scheduled task is the same prompt you'd type in Chat, run on a timer. That means it uses credits on every run. An hourly task runs 24 times a day, so whatever one run costs, the day costs about 24 times that.

The biggest driver is scope. "Check my inbox" makes your clone reread your whole inbox every run. "Check emails from the last 24 hours" keeps each run small. See Put your clone on a schedule.

Events

When another system wakes a clone through an Event (for example, a new form submission), the clone runs its handler instruction with its own skills. Those skill runs use credits like any others, so a busy event source means more runs.

Research, coding and media

Research reports, coding builds and video are the heaviest skills. That's why some guided setups, such as the First-Week Setup Concierge, tell you before starting a coding, video or research skill and ask for a "yes" first. Building a site with Website in Minutes has no fixed cost: larger builds use more credits. For video, the Automated Video review pages let you approve the script and storyboard before anything is rendered. That's a good point to make sure you only render what you want.

Where to see your usage

  • Billing shows your overall credit usage.
  • Per skill call: you can see how many credits each skill call used, so you can tell what's driving your usage.
  • The Execution Log shows which skills ran for each chat or scheduled run. Open a run in Chats and tasks to check it. This is the quickest way to spot a routine that's doing more work than it needs to.
  • Some use cases report their own usage. For example, Lead Enrichment Autopilot adds a Run Summary with the credits and time each run used.

When you run low

You're always in control. If you're running low, you can:

  • Buy more credits, or
  • Pause until your next cycle.

Before starting a heavy job, such as a research report, a coding build or a video, it's worth checking your usage in billing so the job isn't cut short.

Planning heavy jobs

For big jobs, get an estimate before committing:

  1. Run a small test first. Try a new routine or a big job on a small scope. For example, Lead Enrichment Autopilot runs 10-25 rows and shows the credits they used before touching the whole list.
  2. Ask for an estimate. From the test, your clone can project the credits and time for the full job.
  3. Set a budget. Tell your clone to stop at a credit limit. Lead Enrichment Autopilot, for example, stops cleanly when it reaches the budget you set and tells you what's left.
  4. Run in batches with a progress check after each one, so a mistake is caught early.

Habits that stretch your credits

In short:

  • Keep reports and routines to short windows ("last 7 days", "only unread").
  • Put documents in a SharePoint or OneDrive folder, or in Knowledge, instead of asking your clone to dig them out of an inbox.
  • Start small, then scale up.
  • Review scheduled tasks monthly and turn off anything nobody reads.
  • Check the Execution Log for unnecessary work.

Each of these is explained, with examples, in Credits and good habits.

Common questions

Does chatting with my clone use credits? Chat is among the lightest things your clone does. The heavy use comes from research, coding, video and jobs that read large amounts of data.

Why did one scheduled task use so many credits? It probably reads more than it needs to on every run, for example the whole inbox instead of the last 24 hours. Narrow the time window and the amount of data it reads, and check its Execution Log.

Do credits work differently in Studio Max and Team Studio? No. Both editions run on the same platform with the same capabilities. The billing and usage screens may look different.

Can I see exactly what a single request cost? Yes. You can see how many credits each skill call used, and the Execution Log shows which skills ran.

What happens when I run out? You can buy more credits or pause until the next cycle.

Was this helpful?

Related