Credit Consumption
Versable operates on a credit-based pricing model designed to give you flexibility in how you use the platform across modules. Credits can be applied to any module you have access to, allowing you to scale usage based on your actual data workflows rather than being locked into rigid feature limits.
This section covers:
- Available plans and how credits are allocated
- How credits are consumed in real-world workflows
Available Plans
Versable plans are subscription-based and provide a monthly allotment of credits that you can use across supported modules.
Basic Plan
- Starts at $1,000 per month
- Includes 2,000 credits
- Includes access to:
- Data Extraction (text-based only)
- Validation
- Enhancement
Pro Plan
- Starts at $3,000 per month
- Includes 6,000 credits
- Includes access to all modules
Enterprise & Custom Plans
Enterprise plans are available for higher monthly credit needs, where per-credit pricing becomes cheaper than existing plans (<$0.50) at scale. Enterprise plans come with custom features, integration to existing platforms, credit allocation across users.
Custom plans are available if your needs fall between Basic and Pro.
Please contact the Versable team to discuss.
Credit Top-Ups
If you exceed your monthly credit allocation:
- You can purchase one-time top-up credits from the homepage.
- Top-up credits are applied immediately to your current billing cycle.
- Top-up credits are priced slightly higher per credit than subscription pricing.
If you find yourself purchasing top-ups every month, upgrading your plan will result in lower per-credit costs.
Credit Expiration
- Credits do not roll over between billing cycles.
- Unused credits expire at the end of each cycle.
- This allows Versable to:
- Predict usage patterns
- Allocate compute resources efficiently across customers
How Credits Work in Practice
Data Extraction Credit Usage
Website Configuration (One-Time)
- Each new website added for extraction requires 100 credits.
- This is a one-time cost per site.
- Once configured, the site can be reused across files, jobs, and billing cycles.
- You are not charged again for the same site.
Per-Part Extraction
- Text-based extraction costs 1 credit per part, regardless of: - Number of fields selected - Amount of text extracted
- Image scraping (Pro plan and above) costs 1 additional credit per part.
Note: Extracting more fields does not increase credits, but it does increase processing time.
Example: Ash
Ash has a file with 100 parts and wants to enrich his data by scraping competitor and supplier websites. He selects five different websites and asks Versable to extract text-based fields for titles, descriptions, and images.
Because these are new websites that haven't been configured before, Versable first applies a one-time website configuration cost for each site. Once configured, Ash is charged one credit per part to extract all text-based information, and another per part for images.
Credits
- Website configuration: 5 websites × 100 credits = 500 credits (one-time)
- Text extraction: 100 parts × 1 credit = 100 credits
- Image scraping: 100 parts × 1 credit = 100 credits
Total: 700 credits (500 one-time + 200 per run)
Validation Credit Usage
Rule Configuration (One-Time)
- Each new validation rule requires 100 credits to configure.
- Rules are saved to your account permanently.
- Rules can be reused across files, jobs, and billing cycles.
Per-Part Validation
Validation consumes 1 credit per part per rule.
Example: Misty
Misty receives a supplier file with inconsistent formatting and classification. She wants to apply two validation rules: one to map supplier part types to her internal taxonomy, and another to convert fitment data into an ACES-compliant format.
Because these rules don't yet exist on her account, Versable applies a one-time configuration cost for each rule. Misty then runs validation on a file containing 100 parts, and credits are consumed per part for each rule applied.
Credits
- Rule configuration: 2 rules × 100 credits = 200 credits (one-time)
- Validation run: 100 parts × 2 rules × 1 credit = 200 credits
Total: 400 credits (200 one-time + 200 per run)
Enhancement Credit Usage
Enhancement pricing is simple and predictable.
- Enhancement costs 1 credit per unique part per month.
- Number of fields does not affect credit usage.
- Re-running enhancements on the same parts within the same month does not consume additional credits.
Example: Brock
Brock has a file with 500 parts and wants to generate market-ready content for each one. He generates titles, two different descriptions (short and long), and a list of ten features and benefits per part.
Even though he is generating multiple fields and large amounts of content, enhancement pricing remains simple. Versable charges one credit per unique part, regardless of how many fields or variations are generated.
Credits
Enhancement: 500 parts × 1 credit = 500 credits
Total: 500 credits
Image Generation Credit Usage
- Image generation costs 2 credits per successful part.
- Credits are only consumed if an image is successfully generated.
- Failed rows (due to missing reference images) are not charged.
Example: Gary
Gary wants to generate images for 1,000 parts.
Versable searches the web for reference images before generating proprietary images. During processing, the engine determines that 200 of the parts are private-label products with no reliable reference images available. Those rows are skipped automatically.
Images are successfully generated for the remaining 800 parts, and Gary is only charged for those successful generations.
Credits
Image generation: 800 parts × 2 credits/part` = 1,600 credits
Total: 1,600 credits (200 parts not charged due to insufficient reference images)
You now have everything you need to start using Versable effectively, from understanding the platform's capabilities to planning how credits are consumed.
If you have any questions, feature requests, or just want to say hi, please don't hesitate to reach out to our founder (me, the author of this doc!) directly at [email protected]. My favorite part of this job is talking to our customers and learning how you're actually using Versable in the real world. I read every message within 24 hours, and your feedback directly shapes what we build next. We move fast, we listen closely, and we're constantly iterating to make Versable a product you genuinely want to use.