Runs and schedule
When Onym asks your questions, what a run costs, and how answers are reused.
A run asks every active prompt on every surface that serves its lane, once. Runs are what turn prompts into answers.
Schedule
| Plan | Cadence |
|---|---|
| Free | Weekly |
| Starter, Growth, Agency | Daily |
The scheduler starts at 06:00 UTC every day and runs each domain that's due. A domain is due when its last finished run is older than its plan's cadence. A run usually finishes within an hour.
All dates in Onym are UTC. A run that starts at 06:00 UTC on October 14 has run_date 2026-10-14 everywhere, whatever your time zone.
Credits
Each answer costs credits, set by the surface. Consumer-app answers cost 1 credit; some model APIs cost more because they cost us more. Models we track lists every surface's price.
A prompt asked daily on every surface uses about 240 credits a month. Each plan has a monthly budget, pooled across its domains. When a domain's next run would go over the budget, scheduled runs pause until the budget resets. You're never charged extra. The billing page shows what you've used, and Manage prompts shows what each prompt costs per run.
Run statuses
| Status | Meaning |
|---|---|
running |
Questions are being asked |
done |
Finished; its answers count in every metric |
capped |
Stopped at the spending cap; its answers so far count |
failed |
Something broke; Onym retries after six hours |
Failed and capped runs don't reset the schedule, so a retry happens on the next scheduler pass after six hours.
What happens after a run
When a scheduled run finishes, Onym updates the Changes feed and opportunities, checks your site health, and sends the email digest, Slack message and webhooks.