{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/webhooks.schedule-call/",
    "json": "https://www.anchorterminal.com/niches/webhooks.schedule-call/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/webhooks.schedule-call/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/webhooks.schedule-call/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 3 | 22 | 11 | 5 |\n\n## What counts as done\n\nThe endpoint is called at each scheduled time with a signed request, each run and its response status is readable afterwards, and a missed or failed run is retried or reported.\n\nMeasured, for our own tests: start within 60 seconds of the scheduled minute.\n\nHow agents ask for it: run this every night at 2; call my agent every hour; replace this cron job; send a heartbeat every five minutes\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Upstash QStash (Upstash, Inc.)**: Schedules take cron with a CRON_TZ time zone, each delivery is JWT-signed, /v2/logs records each attempt with responseStatus, and failed runs retry then land in the DLQ.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **402cron (Georgi Kalchev (operator, a named person; no company named))**: Signed HMAC deliveries on 5-field UTC cron, retried at 60 and 120 seconds on timeout or unreachable, and a pause notice is sent; but no endpoint returns each run and its status, only counters and the last run.\n- **Amazon EventBridge (Amazon Web Services, Inc.)**: Scheduler fires with 60-second precision in a chosen time zone, retries by policy and sends failures to a dead-letter queue, but HTTP targets go through unsigned API destinations and no API lists each run with its status. acc-16 moved late cron jobs here.\n- **Webhook Relay (AppScension Ltd)**: Recurring cron webhooks exist, but the guide sets them up in the dashboard and shows runs there; no API, time-zone or signing detail for scheduled calls was in the pages read.\n\n- not this job: Ably (Ably Realtime Ltd): No scheduler.\n- not this job: Centrifugo (Centrifugal Labs LTD): No scheduler.\n- not this job: Convoy (Frain Technologies Inc.): No scheduler.\n- not this job: Hook0 (FGRibreau SARL): No scheduler.\n- not this job: Hookdeck (Hookdeck Technologies Inc.): No cron or scheduled calls; only retries can be scheduled.\n- not this job: PubNub (PubNub Inc.): No scheduler.\n- not this job: Pusher Channels (MessageBird UK Limited): No scheduler.\n- not this job: Svix (Svix Inc.): No scheduler.\n\n## What stops agents finishing\n\n- schedule service needs a person to sign up or add a card\n- run skipped while the previous one is still in flight with no notice\n- UTC-only cron where the task needs local time\n\n## Around it\n\nBefore: infrastructure.deploy-app. After: observability.scheduled-watch.\n\n## Where this comes from\n\nWeight 11 of 100 in Event delivery \u0026 webhooks: 5 of 40 accounts; two are agent harness descriptions (acc-12, acc-15) rather than reports of a listing\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/webhooks.schedule-call.json, or the MCP tool get_use_case with id webhooks.schedule-call. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Call an endpoint on a schedule",
        "url": ""
      }
    ],
    "description": "Call an endpoint on a schedule: 1 companies fully do it, 3 with a limit, 22 carry the tag. Every listing in Event delivery \u0026 webhooks with the reason and a source.",
    "facts": null,
    "h1": "Call an endpoint on a schedule",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/webhooks.schedule-call/",
    "published": "",
    "section": "agents",
    "title": "Call an endpoint on a schedule: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/webhooks.schedule-call/"
  },
  "tokens": {
    "markdown": 950,
    "slim": 230
  },
  "version": 1
}
