Bots St

bots.st/agent-cronjob

agent-cronjob

Scheduled HMAC-signed webhook triggers

2345 ms

answered our call

State
Answered
Protocol
MCP 2025-06-18
Tools listed
15
Answered
3 of the last 3 calls

How to reach it

  • MCP, HTTPhttps://cronjob.agentasy.ai/mcp

What it can do

ToolWhat it says it does
claim_credentialsStep 3. Poll verification state with the setup_token. The first call after the webhook is verified returns hmac_secret (signs triggers) and management_token (manages the job) — SHOWN ONCE, store them now; later calls say credentials: "already_issued". (REST: GET /v1/jobs/{id}/verification)
create_jobStep 1. Register your webhook and schedule (no account, no API key). Returns job_id and a one-time setup_token, and POSTs a url_verification challenge to webhook_url. Your webhook must answer it (echo: reply 2xx {"challenge":"<same>"}) — then call claim_credentials. Or reply 2xx and call…
delete_jobStop the job forever and revoke all its credentials. Cannot be undone. (REST: DELETE /v1/jobs/{id})
get_deliveriesTrigger log, newest first: scheduled_at, first attempt time, delay, attempts, status and last response code of each run. since/until (ISO 8601) filter scheduled_at; page with next_cursor. (REST: GET /v1/jobs/{id}/runs)
get_jobSettings, status, next_run_at, run_count and credential prefixes of one job (webhook path masked). (REST: GET /v1/jobs/{id})
get_runOne run and each delivery attempt: sent_at, response status, duration, error and next retry. (REST: GET /v1/jobs/{id}/runs/{run_id})
get_statsOn-time rate, p50/p95 first-attempt delay and success rate over a window (default 24h). (REST: GET /v1/jobs/{id}/stats)
list_jobsStatus of every job you hold a management token for. There are no accounts, so pass each {job_id, management_token} pair (up to 20); a pair without management_token uses the Authorization header. (REST: GET /v1/jobs/{id} (once per job))
pause_jobStop triggering (idempotent). Schedule points while paused are not made up later. (REST: POST /v1/jobs/{id}/pause)
resume_jobResume a paused or disabled job from its next schedule point; resets consecutive_failures. (REST: POST /v1/jobs/{id}/resume)
retry_challengeRe-send a fresh url_verification challenge to your webhook (at most 5 re-sends (6 challenges in total), at least 60 s apart). The previous challenge stops working. (REST: POST /v1/jobs/{id}/verification/retry)
rotate_secretNew hmac_secret (SHOWN ONCE, store it now). Until previous.expires_at (grace_sec, default 24 h) triggers carry two v1= signatures, new first. (REST: POST /v1/jobs/{id}/rotate-secret)
rotate_tokenNew management_token (SHOWN ONCE, store it now). The old one stops working after grace_sec (default 0 = immediately). (REST: POST /v1/jobs/{id}/rotate-token)
update_jobChange a job in place: signature_in_body (true = triggers also carry cronjob_signature in the JSON body, for platforms that drop the X-Cronjob-* headers; applies from the next attempt sent) and/or max_runs. Raising max_runs on a job completed with max_runs_reached reactivates it (next run = next…
verify_challengeStep 2 (callback mode). Send back the challenge value your webhook received. On success the result holds hmac_secret and management_token — SHOWN ONCE, store them now. (REST: POST /v1/jobs/{id}/verify)

In its maker's words

Scheduled, HMAC-signed, retried webhook triggers for AI agents. No account: self-register via tools.

Website
cronjob.agentasy.ai
Publisher
agentasy.ai
Listed from
the official MCP Registry as ai.agentasy/cronjob
Version
0.0.1, updated 3 Nov 2026
Kinds of work
Browser and automation, AI models and agent tools, Security and trust

The domain it lives on

agentasy.ai
registered 2 Oct 2026 (1 month ago), at Cloudflare, Inc., its name does not resolve now

From our own crawl of domain names: registry records and the home page as our crawler last saw it.

Every call we made

WhenWhat happenedTime
Answered2345 ms
Answered2286 ms
Answered1376 ms

Next door

Is this your bot? Claim its address to add a verified badge and keep the listing current.