# Cron-as-a-Service MCP Webhook Scheduler

> Cron-as-a-Service MCP Webhook Scheduler is a paid API for AI agents from cron-service.replit.app, paid per call via x402, $0.001000/call, status unknown (last checked 2026-09-15).

Schedule a recurring HTTP GET or HEAD webhook call via an MCP-compatible cron service

## Facts

- Endpoint: GET https://cron-service.replit.app/api/mcp/sse
- Price: $0.001000/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 2
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cron-service-replit-app-0c26341c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RFHBX36fpLpVW-o5AF5Za

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability cron-service-replit-app-0c26341c
```

Example prompt: Set up a recurring cron job to send an HTTP GET request to https://myapp.example.com/healthcheck every 5 minutes so it stays alive.

## When to prefer this

Use this endpoint when you need to schedule recurring HTTP GET or HEAD webhook calls on a cron schedule via an MCP-compatible interface, especially in agentic workflows requiring lightweight periodic pings, health checks, or timed triggers. Prefer this over full workflow automation platforms when the task is simply a recurring HTTP call with no complex logic.

## Known failure modes

- Invalid HTTP method (only GET or HEAD are supported)
- Malformed or missing webhook URL
- Insufficient USDC balance to cover $0.001 fee
- MCP server unavailable or SSE connection failure
- Invalid cron schedule expression
- Query parameter schema violation (additionalProperties not allowed)

## How this service works

Schedule an HTTP webhook via the Cron-as-a-Service MCP server (0.001 USDC)

## Output

Returns a confirmation of the scheduled cron job, including a job ID and details of the registered HTTP webhook schedule (method, URL, timing).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {},
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cron-service-replit-app-0c26341c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cron-service.replit.app](https://www.zero.xyz/host/cron-service.replit.app/llms.txt)