Billing & Credits
SIE Data uses a simple credit system. You buy a bucket each month, and every action burns a small, fixed amount. No surprise invoices.
What you'll learn
- How many credits each action costs
- How the monthly cycle works
- What happens if you run out
- How to set hard caps and alerts
- How refunds work for bad data
Credit pricing per action
| Action | Credits | Notes |
|---|---|---|
| Search signals | 0 | Free; results are masked |
| Reveal a signal | 5 | Unlocks company + contact |
| Enrich (firmographics) | 2 | Adds size, revenue band, tech stack |
| Enrich (contact) | 3 | Email + phone where allowed |
| Sequence email | 1 | Per delivered send |
| Sequence SMS | 2 | Per delivered send |
| Voice call | 10 | Per connected call |
Monthly cycle
Your credit bucket refills on the same day each month. Unused credits roll over up to 1x your monthly allotment — anything beyond that expires. Think of it as a single carry-forward month, not a savings account.
Overage rules
If you exceed your bucket, SIE charges a small per-credit overage rate (about 1.3x the in-bucket rate). You can flip Hard cap on in Billing settings to block overages entirely — actions just queue up until the next cycle.
Alerts
Set thresholds at 50%, 80%, and 100% of bucket. Alerts go to email and Slack if you connect it. We always email at 100% even with alerts off.
Refunds
If a revealed contact bounces or a signal turns out to be stale, click Report bad data on the record. Verified bad data is refunded automatically within 24 hours.
What's next?
- Generate an API key to track usage programmatically
- Spend your first credits on a real reveal
- Estimate workflow cost with the dry-run runner