# Call an endpoint on a schedule

> Call an endpoint on a schedule: 1 companies fully do it, 3 with a limit, 22 carry the tag. Every listing in Event delivery & webhooks with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/webhooks.schedule-call/
- Markdown: https://www.anchorterminal.com/niches/webhooks.schedule-call/index.md (~950 tokens)
- Slim: https://www.anchorterminal.com/niches/webhooks.schedule-call/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/webhooks.schedule-call/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 3 | 22 | 11 | 5 |

## What counts as done

The 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.

Measured, for our own tests: start within 60 seconds of the scheduled minute.

How 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

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **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.

## Does the job, with a limit

It 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.

- **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.
- **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.
- **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.

- not this job: Ably (Ably Realtime Ltd): No scheduler.
- not this job: Centrifugo (Centrifugal Labs LTD): No scheduler.
- not this job: Convoy (Frain Technologies Inc.): No scheduler.
- not this job: Hook0 (FGRibreau SARL): No scheduler.
- not this job: Hookdeck (Hookdeck Technologies Inc.): No cron or scheduled calls; only retries can be scheduled.
- not this job: PubNub (PubNub Inc.): No scheduler.
- not this job: Pusher Channels (MessageBird UK Limited): No scheduler.
- not this job: Svix (Svix Inc.): No scheduler.

## What stops agents finishing

- schedule service needs a person to sign up or add a card
- run skipped while the previous one is still in flight with no notice
- UTC-only cron where the task needs local time

## Around it

Before: infrastructure.deploy-app. After: observability.scheduled-watch.

## Where this comes from

Weight 11 of 100 in Event delivery & webhooks: 5 of 40 accounts; two are agent harness descriptions (acc-12, acc-15) rather than reports of a listing

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
