# 2s Schedule Status

> 2s Schedule Status is a paid API for AI agents from 2s.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Retrieves the current status, fire counts, next scheduled fire time, and recent delivery history for a previously created schedule by its scheduleId.

## Facts

- Endpoint: POST https://2s.io/api/schedule/status
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/2s-schedule-status-ce75616e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Hm1bKirlFacBQO7XeJiVo

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 2s-schedule-status-ce75616e -d '<json body>'
```

Example prompt: Can you check the status of my scheduled job with ID sched_abc123 — I want to know if it's still active, when it's going to fire next, and how many times it's already run?

## When to prefer this

Use this endpoint when you have an existing scheduleId from a prior schedule.create call and need to programmatically inspect its runtime state — particularly useful for agents monitoring job health, debugging delivery failures, or confirming whether a finite-fire schedule has exhausted its quota.

## Known failure modes

- Invalid or unknown scheduleId returns empty items array or an error response
- Missing scheduleId in request body causes a validation error
- Schedule has been deleted or expired and may no longer appear in results
- Network or upstream provider errors result in non-ok responses

## How this service works

The (most) everything API: 575+ pay-per-call endpoints for AI agents — ground-truth data, a full AI gateway, and agent infrastructure (storage, queues, watchers). USDC via x402, no signup, no API keys, and upto billing: pay actual usage, not the quote.

## Output

Returns a JSON object with ok: true and an items array where each item contains the scheduleId, its current status string, the nextFire timestamp (nullable), firesUsed count, maxFires limit, and a recentDeliveries array. Also includes total count and source provenance metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "scheduleId": {
   "type": "string",
   "description": "The scheduleId from schedule.create."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/2s-schedule-status-ce75616e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 2s.io](https://www.zero.xyz/host/2s.io/llms.txt)