# Onchain & Trading Intelligence Scheduled Callback — x402 Pay-Per-Call

> Onchain & Trading Intelligence Scheduled Callback — x402 Pay-Per-Call 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 a future HTTP callback (webhook) to a user-supplied URL at a specified ISO-8601 time, enabling time-delayed delivery of onchain and trading intelligence results without polling.

## Facts

- Endpoint: POST https://x402-services-production.up.railway.app/api/schedule
- 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/onchain-trading-intelligence-scheduled-callback-x402-pay-per-call-91a8de7c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tCPu-Mq66l9tCisYETJC7

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 onchain-trading-intelligence-scheduled-callback-x402-pay-per-call-91a8de7c -d '<json body>'
```

Example prompt: Schedule a POST callback to https://myserver.example.com/hook with token 'abc123secret' to fire at 2025-08-01T15:00:00Z, sending payload [{"alert":"check funding rates now"}].

## When to prefer this

Use this endpoint when you need to trigger a one-shot HTTP callback at a precise future time (up to 30 days out) without maintaining a polling loop — ideal for time-sensitive onchain trading events, scheduled DeFi health checks, earnings catalyst alerts, or any workflow where an AI agent needs to resume processing at a known future moment. Prefer this over cron-based infrastructure when you want pay-per-use scheduling with no account setup.

## Known failure modes

- Invalid or unreachable callback URL — job created but delivery fails silently at fire time
- fireAt timestamp exceeds 30-day maximum — request rejected
- Malformed ISO-8601 timestamp — validation error returned
- Payload exceeds 16KB limit — request rejected
- Invalid or missing required fields (url, token, fireAt) — 400 error
- Callback URL returns non-2xx at fire time — delivery considered failed, no automatic retry guaranteed

## How this service works

Webhook Scheduler: schedule a future HTTP callback. At fireAt, we call your url with the payload. Agents' alarm clock for async work. Send { token, url, fireAt (ISO-8601), payload?, method? }.

## Output

A confirmation that the scheduled callback job has been created, including the job ID and the scheduled fire time. At the specified ISO-8601 time (up to 30 days out), the service will make an HTTP request (POST or GET) to the provided callback URL with the specified payload. The secret token can subsequently be used to read the job's status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "fireAt",
  "token",
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "Public http(s) callback URL"
  },
  "token": {
   "type": "string",
   "description": "Your secret token (gates status reads)"
  },
  "fireAt": {
   "type": "string",
   "description": "ISO-8601 time to fire (max 30 days out)"
  },
  "method": {
   "type": "string",
   "description": "POST (default) or GET"
  },
  "payload": {
   "type": "object",
   "description": "JSON body to POST (16KB max)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onchain-trading-intelligence-scheduled-callback-x402-pay-per-call-91a8de7c/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)