# CortexCloud Automation Schedule

> CortexCloud Automation Schedule is a paid API for AI agents from api.cortexcloud.org, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Schedules a recurring or one-time HTTP callback to a specified URL using a cron expression, with configurable retries and delay, settled per-call in USDC on Base via x402.

## Facts

- Endpoint: GET https://api.cortexcloud.org/v1/automation/schedule
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cortexcloud-automation-schedule-2f1fe773
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S4xfWXeu_5YxltEC4-RXs

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 cortexcloud-automation-schedule-2f1fe773
```

Example prompt: Schedule a recurring HTTP GET call to https://myapp.com/sync every day at 2am UTC, retry up to 3 times if it fails, and wait 10 seconds between retries.

## When to prefer this

Choose this endpoint when your agent needs to schedule recurring or delayed HTTP callbacks without managing your own cron infrastructure, especially in agent-native workflows where you want pay-per-call economics settled in USDC on Base via x402 with no API key or signup overhead. It is ideal for agents orchestrating multi-step workflows that include timed triggers or retry-safe automations.

## Known failure modes

- Invalid cron expression returns a 400 error
- Target URL is unreachable or returns non-2xx, triggering retry logic up to max_retries
- Malformed payload or headers may cause downstream failures
- Idempotency key collision may reject duplicate schedule creation
- x402 payment failure prevents the schedule from being registered
- Empty response schema suggests possible undocumented error formats

## How this service works

One pay-per-call API for AI agents: optimization, AI, research, on-chain data, and automation — all settled in USDC on Base via x402. Discover via MCP and Bazaar, estimate free, pay per call. No API keys, no signup.

## Output

Returns a JSON object confirming the schedule was created, likely including a job ID or confirmation token that can be used to track or cancel the scheduled task. The response schema is currently sparse but expected to include job metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "cron": {
   "type": "string"
  },
  "headers": {
   "type": "object"
  },
  "payload": {},
  "max_retries": {
   "type": "integer"
  },
  "delay_seconds": {
   "type": "integer"
  },
  "idempotency_key": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "format": "application/json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cortexcloud-automation-schedule-2f1fe773/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.cortexcloud.org](https://www.zero.xyz/host/api.cortexcloud.org/llms.txt)