How features use credits

this page outlines how different features in make (apps and modules) consume credits, so you understand the credit cost of your activities credits by app apps consume credits differently depending on the type built in ai apps consume credits differently than other app types built in ai apps how a built in ai app uses credits depends on whether it uses make's ai provider docid\ hh nrtakeqakbmg63uuin , a custom ai provider connection (such as via an api key), or an automatic ai provider connection to learn more about connection types, see credit usage for ai features docid\ hh nrtakeqakbmg63uuin make's ai provider is available on all plans , and custom ai provider connections are available on paid plans app make's ai provider (all plans) custom ai provider connection (paid plans) automatic ai provider connection (all plans) make ai toolkit https //apps make com/ai tools dynamic 1 credit per operation + credits based on token usage fixed 1 credit per operation make ai agents https //help make com/make ai agents app dynamic 1 credit per operation/chat + credits based on token usage, including ai tokens ( run an agent and create agent context modules) embedding tokens ( create agent context modules) fixed 1 credit per operation (+ embedding tokens when using create agent context modules) make ai content extractor https //apps make com/make ai extractors fixed (1 credit per operation) or dynamic (credits based on token, file, or page based usage), depending on the module https //apps make com/make ai extractors#j7fs5 make ai web search https //apps make com/make ai web search dynamic 1 credit per operation + credits based on token usage all other apps all other apps consume credits based on a fixed rate of 1 credit per operation exceptions the make code docid\ mkn0za9llnqphyf1mxmz8 app uses 2 credits per second of execution time these modules docid\ lzasgxrjtbcjok6vf0rkr are free to use credits by module most non ai apps at make consume credits based on operations their modules use credits differently based on their place in the scenario and how they process data trigger modules 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 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 action modules (those with "add," "update," "delete," etc) use as many credits as runs needed to process all bundles it uses 1 credit per input bundle processed for example, the google sheets > search row module below returned 10 rows and used 1 credit the following delete rows module must run 10 times to delete each of the 10 rows, using 10 credits the scenario uses 11 credits total aggregator modules 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 iterator modules split an array into multiple bundles iterators use 1 credit to split an array into bundles, and the next modules use 1 credit for each iterated bundle for example, the iterator below received an email with an array of 5 attachments and split the array into 5 separate attachments it used 1 credit to split the attachment array, and the google drive > upload a file module used 5 credits to upload each attachment learn more about bundles and their relationship to operations in operations docid\ zr2rwmilmj 19r85mlawm modules with no credit cost the following modules don't use credits error handler docid 3sxxd1q5e os35cbkdlwk modules rollback , break , resume , commit , ignore router docid\ opqxxzcge19tawxhiaehn modules and filters docid\ toeivu0dbv44bmrjcmlic scenarios docid\ f8fhrvoqwck48nx fjryf modules call a subscenario , start a scenario , return output , and customize run name make functions docid\ v5lrz7uqk1z12zxr6rukq modules