Cronicorn

HTTP jobs that understand their own responses

Add endpoints, describe what matters in plain English, and the AI reads response bodies to adapt —
adjusting frequency, coordinating siblings, and recovering from failures automatically

Activity surge → AI tightens to 30s + triggers recovery actions → stabilizes → back to baseline

Features Adaptive scheduling — AI adjusts polling frequency based on real response data Plain English descriptions — no config files, no SDK required Safety constraints — min/max intervals and TTL-based hints that auto-expire Multi-endpoint coordination — endpoints are aware of siblings and adapt together Automatic error recovery — backoff, retry, and recovery actions out of the box Works without AI — traditional cron and interval scheduling as a fallback How It Works Add an HTTP endpoint and set a baseline schedule (cron or interval) Describe what matters in plain English — thresholds, coordination logic, response structure AI monitors responses and adapts frequency, triggers actions, and recovers from failures automatically Getting Started Path Link Web UI — create and manage jobs visually cronicorn.com MCP Server — manage jobs from Claude, Cursor, or any MCP client MCP Server docs API — integrate programmatically with the REST API API Playground

Docs · MCP Server · API · Self-Host · Support