Data Credits explained
Data Credits are SALT's unit for paid lookups against external data providers. Each pull costs a configured number of credits. Credits live at the agency level, are bought in packs (100, 500, 2,000, 5,000) with volume discounts, and can be auto-reloaded.
In short: Buy Data Credits in packs; each external data lookup (property data, dec page, MVR) consumes some. Auto-reload prevents running out. Credits are pooled at your agency level.
What Data Credits are for
External data providers (Estated for property data, Fenris for risk data, MeasureOne for declaration page retrieval, Fize as alternative) charge per lookup. Data Credits are how SALT bills those lookups: each pull costs a configured number of credits.
Per-pull costs vary by vendor. Lookups against more expensive providers consume more credits per pull.
Where credits live
Credits accumulate at the agency level. Buying credits, viewing the balance, and configuring auto-reload all happen there.
How credits get used
When a Submission triggers a data lookup:
- SALT debits the credit cost from your agency balance
- The vendor performs the lookup
- The response is stored against the Submission
You see the data on the Submission’s detail; the credit consumption shows up in your usage reports.
If your balance is too low for a pull, your overage policy determines what happens — block, allow with overage charge, or temporary allow.
Buying credits
Credits come in packs with volume discounts:
| Pack | Discount |
|---|---|
| 100 credits | None |
| 500 credits | 5% |
| 2,000 credits | 10% |
| 5,000 credits | 15% |
Buy from your Data Credit settings:
-
1
Open Data Credits on your account.
-
2
Click to add credits.
-
3
Pick a pack size.
-
4
Confirm. The charge runs immediately; credits land in your balance.
Auto-reload
Auto-reload tops up your balance automatically when it dips below a configured threshold:
-
1
Open Data Credits settings.
-
2
Configure the trigger threshold (typically 10% of pack size).
-
3
Pick the reload pack to buy when triggered.
-
4
Save.
When the trigger fires, SALT charges your card and adds credits. You don’t run out, integrations don’t pause, charges are predictable.
Threshold notifications
Even without auto-reload, you’ll get notifications as the balance approaches zero:
- 20% remaining
- 10% remaining
- 5% remaining
Auto-reload usually fires before the lowest tier, so you may not see all of them.
Per-vendor monthly limits
Separate from your overall balance, each vendor integration can have a monthly threshold — a self-imposed cap on how many lookups SALT runs for that vendor per month. When the vendor’s monthly limit is hit, that vendor pauses for the rest of the month even if your overall balance is healthy.
This is useful for cost control on a specific provider. Configure per-vendor limits in the integration settings (the UI label is typically “Manage Monthly Limit”). See Setting per-vendor thresholds.
Common questions
What’s the per-pull cost for each vendor? Per-vendor cost is configured in SALT. Typical range: 0.8 to 2.0 credits per pull. Check your data credit settings for the current cost per vendor.
Do unused credits expire? Standard credits don’t expire while your subscription is active. Check your specific terms — promotional credits may have expiration dates.
Are credits refunded on cancellation? Generally no. Use them while you’re active or accept the loss on cancellation.
Why isn’t my CRM/rater integration consuming credits? CRM, rater, and automation integrations don’t consume credits — only paid data provider lookups do. See Integrations overview for which fall into which category.