# ManyLives Schedule Status

> ManyLives Schedule Status is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-10).

Retrieves the current status of all scheduled webhook calls registered with the ManyLives agent scheduling service

## Facts

- Endpoint: GET https://api.manylives.me/paid/schedule/status?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/manylives-schedule-status-88aefff5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pkuVM-sCV2_qkO1sQ19s0

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 manylives-schedule-status-88aefff5
```

Example prompt: Can you check the current status of all my ManyLives scheduled jobs — I want to see which ones are active, when they last ran, how long they took, and how many calls are left on each?

## When to prefer this

Use this endpoint when an AI trading agent needs to audit or monitor the health of its recurring scheduled webhook calls on ManyLives — particularly to confirm active schedules, debug failed executions, check remaining call budgets, or determine when the next trigger fires. Prefer this over general monitoring tools when the agent is specifically managing ManyLives-hosted schedules that drive automated trading strategy triggers or backtest pipelines.

## Known failure modes

- No schedules found if none have been created yet — returns empty array
- Authentication failure if API key is invalid or missing — returns 401
- Payment failure if the $0.002 USDC micro-payment via x402 is not processed — returns 402
- Network timeout if the ManyLives API is temporarily unavailable — returns 503
- Rate limiting if too many status checks are made in quick succession — returns 429

## How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

## Output

Returns an array of schedule objects, each containing: schedule ID, target webhook URL, status (active/inactive), timestamp and duration of last execution, timestamp of next scheduled execution, number of calls remaining and made, last error message (if any), and last HTTP response status code.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schedules": [
   {
    "id": "sch_h8g7f6e5d4c3b2a1",
    "url": "https://example.com/hook",
    "status": "active",
    "last_at": "2026-10-09T12:01:02Z",
    "last_ms": 240,
    "next_at": "2026-10-09T13:01:00Z",
    "calls_left": 23,
    "calls_made": 1,
    "last_error": null,
    "last_status": 200
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-schedule-status-88aefff5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.manylives.me](https://www.zero.xyz/host/api.manylives.me/llms.txt)