We gate our own blog. Scored 17 October 2026 with the same engine you get, glossary rules, balanced strictness.
A scheduled re-scan is the existing deterministic /scan/url endpoint run on a timer. When the score drops below your threshold or by more than 10 points, fire an alert to your configured channel.
Cadences
Daily, weekly, or monthly. The cron is internal; the durable job queue survives restarts.
API
All schedule operations live under /api/v1/schedules. Manage them via curl or the UI at /account/schedules.
curl -X POST https://api.dokeo.co/api/v1/schedules \
-H "X-API-Key: $DOKEO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/blog/post",
"cadence": "weekly",
"score_threshold": 70,
"alert_channels": ["webhook"],
"title": "My post",
"content_type": "blog"
}'curl -X POST https://api.dokeo.co/api/v1/schedules/{id}/run \
-H "X-API-Key: $DOKEO_API_KEY"
# Response includes:
# - score (int)
# - prev_score (int | null)
# - verdict (pass | flag | fail)
# - decay_detected (bool)
# - alert (string | null) - description if threshold was crossed
# - checks (per-check status)Decay alerts
When the new score is below score_threshold OR has dropped more than 10 points since the last run, fire the content.decay_detected event to your configured integrations (Slack, Discord, generic webhook).
Costs
Each schedule run consumes one automated (CI) scan credit. They never touch the interactive allowance. On Growth, that is 12,500 / month - enough for a weekly re-scan of dozens of URLs.