# Cron Job Scheduler for Onchain Trading Intelligence

> Cron Job Scheduler for Onchain Trading Intelligence is a paid API for AI agents from x402-services-production.up.railway.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Schedules recurring cron-based callbacks to a user-supplied URL, enabling periodic automated polling of onchain and trading intelligence tools

## Facts

- Endpoint: POST https://x402-services-production.up.railway.app/api/schedule/cron
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cron-job-scheduler-for-onchain-trading-intelligence-b7e714cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GhFWnZ8PAyAUCO4jIJg4O

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-job-scheduler-for-onchain-trading-intelligence-b7e714cd -d '<json body>'
```

Example prompt: Set up a cron job that hits my callback at https://mybot.example.com/webhook every 5 minutes using POST, with my secret token 'abc123xyz', so I can get fresh pump.fun snipe alerts automatically.

## When to prefer this

Use this endpoint when you need to automate periodic calls to onchain or trading intelligence tools on a fixed schedule — for example, polling token prices, monitoring new launches, or checking risk scores at regular intervals — without maintaining your own cron infrastructure. Prefer this over manual polling when you need reliable, pay-per-call scheduled automation payable in stablecoins without account setup.

## Known failure modes

- Invalid cron expression format causes rejection
- Callback URL unreachable or non-public returns scheduling error
- Missing required fields (url, cron, token) returns 400 validation error
- Payment failure via x402 protocol blocks job creation
- Cron job silently fails if callback URL goes offline after scheduling

## How this service works

Recurring webhook: fire your URL on a cron schedule (repeats). Send { token, url, cron, payload?, method? }.

## Output

A confirmation that the cron job has been registered, including the scheduled expression, the callback URL, and likely a job ID or next-run timestamp. Subsequent executions will POST (or GET) the supplied payload to the callback URL on the defined schedule.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "cron",
  "token",
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "Public callback URL"
  },
  "cron": {
   "type": "string",
   "description": "5-field cron expression (UTC)"
  },
  "token": {
   "type": "string",
   "description": "Your secret token"
  },
  "method": {
   "type": "string",
   "description": "POST or GET"
  },
  "payload": {
   "type": "object",
   "description": "JSON body to POST"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cron-job-scheduler-for-onchain-trading-intelligence-b7e714cd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-services-production.up.railway.app](https://www.zero.xyz/host/x402-services-production.up.railway.app/llms.txt)