Understanding Lookup Column Enrichment Credits in Sculptor

Joe H. · 2025-12-16T04:36:02.685Z

I used Sculptor to create a Lookup column enrichment, and it's quoting me 2 credits per lookup. Is this strictly because I used Sculptor, or is this a universal credit charge for Lookup function?

Understanding Lookup Column Enrichment Credits in Sculptor | Clay

10 comments

· Sorted by Oldest

Clay Support
APP
·
·
The 2 credits per lookup isn't specific to Sculptor—it's the standard cost for data enrichment actions in Clay. [1] Most actions cost 1-2 credits regardless of how you create them. [2]
Your lookup will only charge credits when matches are found, so if there's no match, you pay 0 credits.
Clay Support
APP
·
·
Is that what you were looking for?
Joe H.
·
·
but there's no enrichment happening, it's just looking up existing data
Clay Support
APP
·
·
You're right—lookup columns are specifically designed to avoid enrichment costs. The sources recommend using lookup columns to "integrate existing data rather than repeating enrichments" and to "pull that existing data, saving credits by avoiding duplicate enrichments." [1]
The 2 credits you're seeing might be a display issue or related to how Sculptor is interpreting the action. Lookups of existing data shouldn't consume credits since no external data providers are being called.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help understanding the credit charges for your lookup column, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or clarify?
Taimoor A.
·
·
Why didn’t you use Lookup enrichment instead of Sculptor
Clay Support
APP
·
·
Sculptor and Lookup enrichments serve different purposes. Sculptor is designed for building new tables, generating workflows, and creating enrichments from scratch through natural language. [1]
Lookup enrichments are for pulling existing data between tables without external API calls. If you already have the data in another Clay table, a standard Lookup column would be the right choice and shouldn't consume credits.
Sculptor may have suggested a different approach or interpreted your request as needing new enrichment rather than a simple lookup.
Clay Support
APP
·
·
Does this clarify things?
Clay Support
APP
·
·
If you still have questions about credit charges or how to best use Sculptor versus Lookup enrichments, I’m happy to help clarify. Would you like to share more about what you’re trying to achieve so I can assist further?

Clay Support
APP
·
·
The 2 credits per lookup isn't specific to Sculptor—it's the standard cost for data enrichment actions in Clay. [1] Most actions cost 1-2 credits regardless of how you create them. [2]
Your lookup will only charge credits when matches are found, so if there's no match, you pay 0 credits.
Clay Support
APP
·
·
Is that what you were looking for?
Joe H.
·
·
but there's no enrichment happening, it's just looking up existing data
Clay Support
APP
·
·
You're right—lookup columns are specifically designed to avoid enrichment costs. The sources recommend using lookup columns to "integrate existing data rather than repeating enrichments" and to "pull that existing data, saving credits by avoiding duplicate enrichments." [1]
The 2 credits you're seeing might be a display issue or related to how Sculptor is interpreting the action. Lookups of existing data shouldn't consume credits since no external data providers are being called.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help understanding the credit charges for your lookup column, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or clarify?
Taimoor A.
·
·
Why didn’t you use Lookup enrichment instead of Sculptor
Clay Support
APP
·
·
Sculptor and Lookup enrichments serve different purposes. Sculptor is designed for building new tables, generating workflows, and creating enrichments from scratch through natural language. [1]
Lookup enrichments are for pulling existing data between tables without external API calls. If you already have the data in another Clay table, a standard Lookup column would be the right choice and shouldn't consume credits.
Sculptor may have suggested a different approach or interpreted your request as needing new enrichment rather than a simple lookup.
Clay Support
APP
·
·
Does this clarify things?
Clay Support
APP
·
·
If you still have questions about credit charges or how to best use Sculptor versus Lookup enrichments, I’m happy to help clarify. Would you like to share more about what you’re trying to achieve so I can assist further?