Skip to main content
Credits are VeluraHQ’s unit of computation — they’re consumed when you run workflows, execute agent tasks, and track AI search prompts. Every plan includes a monthly credit allocation alongside a separate prompt-answer tracking quota for AI Search Analytics. Understanding how credits are consumed helps you plan capacity, choose the right plan for your team’s workload, and avoid interruptions mid-run during large batch operations.

​
Plan comparison

​
What consumes credits

Credits are drawn from your monthly allocation each time the platform performs a computation on your behalf. The following activities consume credits:
  • Workflow runs — Cost depends on the number of blocks in your workflow, the AI models selected, and the volume of data being processed. More complex pipelines with research, generation, and QA blocks use more credits per run than simple single-block workflows.
  • Agent tasks in Cowork — Each task your agent completes inside the Cowork chat workspace draws from your credit balance.
  • AI Search Analytics prompt executions — Tracking brand mentions and citations across AI engines consumes credits alongside your prompt-answer quota.
  • SuperBlock executions inside Sheets — Running a SuperBlock across rows in a Sheets bulk operation consumes credits proportional to the number of rows processed and the complexity of the block.

​
Checking your usage

Go to Settings > Billing to see your current credit usage, remaining balance, and the date your credits reset for the next billing period. Your prompt-answer tracking quota and workflow credit balance are displayed separately so you can monitor each independently. Enterprise customers can contact their dedicated account manager to discuss custom credit packages if your team’s usage consistently exceeds the included 200,000 credits.

​
Credit efficiency tips

Before running a bulk Sheets operation across thousands of rows, test your workflow on a small selection — 5 to 10 rows — to confirm the outputs meet your quality bar. Catching a misconfigured block early saves the credits that would otherwise be spent on a full run that needs to be re-done.
Use scheduled Pulse runs during off-hours to spread your credit load across the billing period. Concentrating large batch runs in the first few days of the month can exhaust your balance before you’ve processed everything you need.
When testing a new workflow, run it on 1–2 inputs before setting it to execute at scale. A short test run costs a fraction of a full batch and lets you verify that every block — research, drafting, QA, and publishing — is configured correctly before committing to the full dataset.

​
Free tier and sign-up

The Starter plan requires no credit card to start. You can sign up, connect your stack, and begin running workflows immediately at app.velurahq.com. Starter includes 15,000 workflow credits and 8,000 prompt answers tracked per month.

​
Credit expiry

Credits do not roll over between billing periods. Any unused credits expire at the end of each monthly cycle and are not carried forward into the next month. If you find you consistently have unused credits, consider whether a lower plan tier better matches your team’s actual workload — or scale up your operations to take full advantage of your included allocation.