Real-time usage and trends
View credits, API calls, and cost per customer by Vera task, team, source, and processing stage.
We use essential cookies so the site works. With your consent, we also use analytics tools (PostHog and Microsoft Clarity) to understand traffic and improve the site. “Accept all” enables analytics; “Necessary only” keeps only essential cookies. See our Privacy Policy for details.
Track usage by task, team, and processing stage; control query, third-party verification, and enrichment budgets separately; alert, downgrade, or pause before costs become abnormal.
View credits, API calls, and cost per customer by Vera task, team, source, and processing stage.
Set separate monthly budgets, per-task caps, and team allowances for query, verification, and enrichment.
Notify, switch to lower-cost paths, or pause new tasks at 70%, 85%, and 100%.
Link every unit of consumption to a task, customer, call source, actor, and final delivery.
VERA BUDGET & USAGE CONTROL
Queries, verification, and enrichment use different data and services, so each can be limited independently. When one stage approaches budget, adjust that stage without stopping the entire Vera workflow.
Vera monthly usage · Global Research Team
July 2026 · Live
Total budget used
64% · 128,420 / 200,000 credits
Company and contact queries
Search, source reads, and candidate discovery
49,600
/ 80,000 credits
Company and channel verification
Entity, email, domain, and channel status
28,800
/ 60,000 credits
Data enrichment
Role, region, size, signals, and evidence
48,600
/ 60,000 credits
Per-task cost cap
Approval is required to expand research beyond 2,000 credits.
Progressive degradation
Preserve company, decision-maker, and channel verification while pausing optional fields.
Budget increase approval
Record requester, business reason, added allowance, and final outcome.
When budget is constrained, Vera narrows scope and reduces optional enrichment instead of sacrificing core verification quality or creating unpredictable overages.