Point Recuro at any URL. Trigger instantly, delay by minutes or days, or set a recurring cron. We handle execution, retries, logging, and alerts — so you don't have to.
curl -X POST https://app.recurohq.com/api/jobs \ -H "Authorization: Bearer $API_TOKEN" \ -d '{ "queue": "emails", "url": "https://api.yourapp.com/send", "payload": { "to": "[email protected]" } }'
How it works
Instant, delayed, or recurring. All fully logged, retried, and alerted.
Fire and forget
Trigger any HTTP endpoint right now from your code. Fire and forget — we queue it, run it, retry on failure.
Run later, on your terms
Schedule a job to run in 5 minutes, 3 hours, or 7 days. Perfect for trial expiry emails, follow-ups, and time-sensitive workflows.
Recurring, on a schedule
Recurring jobs on any schedule. Every hour, every Monday, first day of the month — standard cron expressions, fully logged.
Observability
Failed jobs, live alerts, and response time stats — all in one place.
Failed jobs
POST /api/send-email
2 min ago
GET /api/sync-users
14 min ago
POST /api/notify
1 hr ago
Each failure links to the full response body, headers, and retry history.
Alerts
"onboarding" queue failed 3 times in a row. Job: POST /api/welcome
Today at 09:14
"onboarding" queue is healthy again. Last run succeeded.
Today at 09:31
Set a failure threshold per queue. Get alerted, then notified when it recovers.
Response times
Per-queue and per-job stats. Spot slow endpoints before they become problems.
Dashboard
All your crons and jobs — statuses, queues, last run time — at a glance.
Total runs
1,240
last 24h
Successful
1,198
96.6%
Failed
42
view all
Avg response
312ms
p99 890ms
Teams
Separate your projects into teams — each with their own crons, queues, dashboards, and members. Keep production isolated from staging. Let clients see only their own jobs.
Features
Everything you need to run HTTP jobs reliably, from day one.
Use any standard cron expression to run recurring HTTP calls. Every execution is logged -- timing, status, and response body.
POST to /api/jobs from your code to trigger any URL immediately or with a delay. Webhooks, callbacks, background work -- all covered.
Configure retry count and delay per queue. Failed calls are retried automatically -- transient errors never become permanent data loss.
Set a consecutive failure threshold. Get alerted when it trips, and notified again when things recover.
Every run logged: status code, response, latency, retry count. Full audit trail so you always know what happened and when.
Invite teammates with admin or member roles. Shared crons, queues, and dashboards -- no friction.
Add Recuro as an MCP server and your agent can create crons, queue jobs, and check executions — no custom code needed.
{
"mcpServers": {
"recuro": {
"command": "npx",
"args": ["-y", "recuro-mcp"],
"env": {
"RECURO_API_TOKEN": "your_token_here"
}
}
}
}9 tools available
list_crons
List and filter crons
create_cron
Create a scheduled cron
get_cron
Get cron details
update_cron
Update cron config
delete_cron
Delete a cron
list_jobs
List and filter jobs
create_job
Queue a one-off job
get_job
Get job details
delete_job
Delete a job
Pricing
Pay for outgoing requests. No seat limits, no queue limits, no feature gates.
Pro
10,000 requests / mo
For production apps and small teams.
Team
100,000 requests / mo
For growing teams with serious workloads.
Enterprise
1,000,000 requests / mo
For high-volume workloads at scale.
Need a custom volume? Get in touch →
FAQ
Recuro is a cloud-hosted HTTP job scheduler built for developers. It lets you run recurring cron jobs and on-demand HTTP requests without managing your own scheduler infrastructure. You define the URL, method, headers, and schedule -- Recuro handles execution, retries, logging, and alerting so you can focus on your application logic.
A traditional cron server requires you to provision, maintain, and monitor a dedicated machine. If it goes down, your jobs stop silently. Recuro runs your schedules in a managed cloud environment with built-in retry logic, failure alerts, and a full execution history -- so you never have to SSH into a box to check if your jobs actually ran.
No. Recuro calls any publicly reachable HTTP endpoint you provide. If your app already has a route that does the work -- sending emails, syncing data, generating reports -- just point Recuro at that URL. There is nothing to install and no SDK required.
Recuro automatically retries failed jobs based on the retry count and delay you configure per queue. If a job keeps failing and hits your consecutive-failure threshold, you receive an alert. When it recovers, you get a recovery notification too. Every attempt is logged with the status code, response body, and latency so you can diagnose issues quickly.
Yes. Send a POST request to the Recuro API with the target URL, method, headers, and payload. The job is queued and executed immediately or after an optional delay. This is useful for webhooks, background processing, and event-driven workflows where a fixed cron schedule does not apply.
Every plan includes 1,000 free credits to start -- no credit card required. Use them to test everything before your billing begins. Sign up to get started.