Credits

the information in this article is subject to change until the credit system and its affected elements are finalized with this guide to make's credit system, you'll understand what credits are, their calculation logic, and your options for tracking and adding credits what are credits? credits are the currency you buy and consume to use features in make your credit usage is based on the number of operations, ai tokens, and other usage based factors only features activated by scenario runs (apps, modules, and some in app features) or the ai agent’s chat feature use credits you can see credits and operations as separate terms in make because they serve different purposes credits help you track how much you’re spending, and operations docid\ zr2rwmilmj 19r85mlawm show you the outcome of your activities on the platform in make, features use credits on a fixed or dynamic basis credits /#fixed credit usage features use a set number of credits per run credits /#dynamic credit usage some ai features and advanced modules use a varying number of credits per run based on actual consumption whether a feature has fixed or dynamic credit usage depends on its processing complexity and if it uses make's ai provider in the product, make always indicates when features use credits dynamically with tags and tooltips fixed credit usage with fixed credit usage, modules consume credits based on a set rate by default, 1 operation uses 1 credit that rate is constant regardless of input or data transfer size most apps in make consume credits on a fixed basis, allowing for predictable costs for example, running the google drive > upload a file module always uses 1 credit per file upload, regardless of the file size some modules with fixed credit usage consume more than 1 credit for an operation due to their processing complexity currently, these include some make ai content extractor modules, which each use a different number of credits per operation you can identify features that use more than the default 1 credit by their tag, which specifies credits per operation you can find detailed examples of fixed credit usage in credits /#credits in modules dynamic credit usage with dynamic credit usage, modules consume a different number of credits based on actual usage rather than a fixed rate mostai features using make's ai provider consume credits dynamically based on token consumption these features have dynamic credit usage because make pays the ai provider (e g , openai or anthropic) directly, eliminating the need to create your own account since these providers charge based on tokens, that variable cost is reflected in your credit usage other features, such as some ai content extractor modules, use a different number of credits per run depending on factors like file size, page number, or run time you can identify features with dynamic credit usage by their tags, which include ai tokens credits based on ai tokens consumed (+ operations in some cases, such as make ai agent and make ai toolkit) file size credits based on file size processed per page credits based on pages processed run time credits based on processing time for a list of all dynamic credit usage features, head to credits /#credits in features credits and tokens when you use ai features in make, you'll also need to understand tokens—the unit that ai providers use to measure and charge for usage you consume tokens to interact with large language models (llms), such as chatgpt or claude token consumption depends on the amount of information processed more interactions, longer prompts, larger files, and longer responses all increase your token usage in english, 1 token equals around 4 characters , and 100 tokens equal about a paragraph when using ai in make, you have two ways to pay for your token usage use make's ai provider, or use your own connection to a provider option 1 you pay make for token usage (use make's ai provider) make handles the connection to an ai provider for you, so you don't need to create an account with openai, anthropic, or other providers you pay for tokens directly with make using credits when you use make's ai provider, you choose a large language model (llm) tier small, medium, or large each tier is a different model that is ideal for a specific purpose llm tier best for small simple text analysis and basic prompts medium more complex tasks and moderate file processing large for tasks requiring advanced reasoning token to credit conversion rates are based on the llm tier for example, 4500 tokens per credit for a small tier, compared to 1000 tokens for a larger tier token to credit conversion rates are currently being finalized and will be included in this article on august 27th with some ai features, you use 1 credit for each operation in addition to the token based credits above when using make's ai provider, you can see the number of tokens used in each run in the white bubble that appears above a relevant module, once you expand an operation you can see both input and output tokens used option 2 you pay your ai provider for token usage (use your own connection) you use your own connection to an existing account with openai, anthropic, or another ai provider you pay for tokens directly with that provider you have two billing components credits make bills you for operations in modules tokens your ai provider bills you for tokens used you pay for tokens directly with your external ai provider, and your token to credit conversion rate depends on your model features offering both options you can choose between make's ai provider and an external ai provider for these features make ai tools docid\ qziwfqxhlmorepv5b4uqw make ai agents docid 0kbnuoduk1emvkqnwmdqc ai prompt calculating credit usage you can anticipate the credit cost of your activities in make with an overview of how different features and modules consume credits the next sections explain how you will consume credits by features and by operations in modules credits in features this chart breaks down make's credit pricing logic for all features, including apps and in app features, depending on whether you use make's ai provider or your own connection to an external provider, if relevant feature uses make's ai provider uses your connection make ai toolkit dynamic 1 credit per operation + credits based on token usage fixed 1 credit per operation make ai agents dynamic 1 credit per operation + credits based on token usage fixed 1 credit per operation ai prompt dynamic credits based on token usage no additional cost make ai content extractor fixed (1 credit per operation) or dynamic (credits based on token, file, or page based usage), depending on the module n/a all other features fixed 1 credit per operation n/a credits in modules most non ai apps at make consume credits on a fixed basis, based on operations completed in modules there are several types of modules docid\ bkdeyubelio6yvvcosrxj at make, each using credits differently based on their place in the scenario and how they process data trigger modules use 1 credit per run, regardless of whether they return data even when a trigger finds no new data, it still uses 1 credit for checking for example, in the google sheets > watch new rows module below, the scenario run retrieved no new data, but used 1 credit for the operation search modules use 1 credit per run, even when they return multiple bundles for example, the google sheets > search row module below runs once to search rows according to the specified criteria it only uses 1 credit for this operation despite returning 10 rows, or bundles action modules (those with "add," "update," "delete," etc) use as many credits as runs needed to process all bundles it uses 1 credit per bundle processed for example, the google sheets > search row module below returned 10 rows the following delete rows module must run 10 times to delete each of the 10 rows, using 10 total credits aggregator modules combine multiple bundles into a single bundle, called an array aggregators use 1 credit for each aggregation for example, the array aggregator below combined 10 contacts, or bundles, from the google sheets > watch new rows module into an array this aggregation used 1 credit iterator modules split an array into multiple bundles iterators use 1 credit to return an array, and the following modules use 1 credit for each iterated bundle for example, the iterator below received an email with 5 attachments and split them into 5 separate attachments, or bundles it used 1 credit to split the attachment array, and the google drive > upload a file module used 5 credits to upload each attachment these module types do not use credits error handlers modules rollback, break, resume, commit, ignore router modules and filtering scenarios docid\ f8fhrvoqwck48nx fjryf overall, the same fixed credit usage logic applies to all modules, except triggers when a module returns multiple bundles, each bundle triggers its own run in each module it passes through this happens because make processes bundles separately each bundle's scenario run is an operation, and each operation uses a predetermined number of credits – usually 1 for example, a trigger module returns 10 new contacts, and the next module runs 10 times, once for each contact, to add them to a table adding 10 contacts results in 10 operations, using 10 credits you can learn more about bundles and their relationship to operations in operations docid\ zr2rwmilmj 19r85mlawm tracking credit usage you can track your credit usage to understand which of your activities consume the most credits and adjust your automations as needed several places in make allow you to view credit usage, each offering a different breakdown of your consumption this chart outlines where you can track credit usage in make and the kind of credit usage information available view how to find it what you see best for dashboard navigate to organization in the left sidebar total credits used overview and trends subscription navigate to organization in the left sidebar in my plan , click subscription total credits + percentage used billing and purchasing scenarios navigate to scenarios in the left sidebar credits per scenario identifying high usage scenarios diagram navigate to scenarios in the left sidebar click a scenario in the scenario list credits for a scenario + run history analyzing scenario level usage scenario builder navigate to scenarios in the left sidebar click on a scenario in the scenario list click anywhere on the canvas credits per module analyzing module level usage + debugging history navigate to scenarios in the left sidebar click on a scenario in the scenario list click on the history tab at the top credits per individual run analyzing run level usage in the next sections, you'll learn more about tracking credit usage at different levels total credits you can view your total credit usage for the current billing period in dashboard and subscription dashboard in credits , you can view total credits used from all credits purchased you can also hover over credits to view any extra credits purchased the blue line in the chart below credits is your credit usage trend subscription in credits , you can view the number of credits you used from the total and the percentage you can also buy extra credits or enable extra credits auto purchasing scenario level credits you can view your credit usage by scenario in scenarios and diagram scenarios the scenarios list provides an overview of each scenario's credit usage the credit icon indicates the number of credits a scenario used inthe current billing period diagram under consumption , you can see the total credits used in the scenario under history , you can find individual scenario runs and their credit usage you can also click on a run to view it in more detail module level credits you can view your credits at the module level, including by scenario run, in the scenario builder and its history tab scenario builder after you run a scenario, you can view each module's credit usage for the scenario run in the white bubble above the modules next to the scenario name, you can toggle the credits view on and off history you can view a scenario's runs and the credits used click on details on the right hand side to view a simple or advanced history log buying extra credits if you run out of credits before the next billing cycle starts, you can upgrade your subscription, buy extra credits, or enable extra credits auto purchasing to learn more about these options, head to extra operations docid 2zcwidbk uamtp2x2 7kj