Scheduled checks on your own API key

If you've connected your own Anthropic API key, scheduled checks keep using it exactly like a manual run does — and the overnight batch discount doesn't apply, because that discount is only available on platform-funded runs.

What you get

• Full control over which key pays for a run, on demand or on a schedule — your key stays your key either way.
• No surprise switch to platform billing just because a check happened to run overnight.
• The same accuracy and coverage on a BYO-key scheduled run as on any other run.

Why BYO runs don't get the overnight discount

The lower overnight cost per research unit comes from batching platform-funded runs together into a shared processing window. A run billed to your own key is never pooled into that window — it's processed directly against your key, the same way a manual run is, whether it happens at 2 PM or 2 AM. That keeps your key's usage predictable and under your control, but it also means BYO scheduled runs don't pick up the overnight rate.

What this means for cost

If lowering your per-unit cost on overnight runs matters to you, that discount is only available on runs billed to your workspace's platform allocation, not to a connected key. A BYO key still gives you full control over your own API spend and rate limits — it just prices scheduled and on-demand runs the same way.

Go further

• Overnight checks finish by morning — how the batch window and its discount work on platform-funded runs.
• Put checks on a schedule — schedules behave the same whether billed to your key or the platform.
• Cost per research unit — how per-unit cost is measured either way.