# Port 402 Reminder Scheduler

> Port 402 Reminder Scheduler is a paid API for AI agents from port-402-production.up.railway.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-02).

Schedule a delayed message for an AI agent that delivers to its inbox and optionally POSTs to a webhook when due

## Facts

- Endpoint: GET https://port-402-production.up.railway.app/v1/reminders?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/port-402-reminder-scheduler-031668dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7_eWN3IlgNliF5iNxitHH

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 port-402-reminder-scheduler-031668dc
```

Example prompt: Set a reminder for 2 hours from now with the message 'Check whether the report has been filed' and POST it to my webhook at https://myagent.example.com/callbacks when it fires.

## When to prefer this

Use this endpoint when an AI agent needs to pause execution and resume later at a specific time, implement delayed retries, schedule follow-up actions, or trigger downstream webhooks after a waiting period — especially in agentic pipelines where no persistent server is available to hold timers. It is ideal for autonomous agents that need alarm-clock-style scheduling without managing their own cron jobs or sleep loops.

## Known failure modes

- Delay out of allowed range (less than 10 seconds or more than 366 days) returns an error
- Invalid or unreachable webhook URL may result in failed delivery with no retry guarantee
- Payment failure via x402 protocol causes the reminder to not be created
- Missing required message content or malformed request body returns a validation error
- Webhook endpoint returning non-2xx may indicate lost delivery with no automatic retry

## How this service works

Alarm clock for agents: schedule a message for later (10 s to 366 days). When due it lands in your inbox and, if you give an https webhook, is POSTed to it too.

## Output

A confirmation that the reminder has been queued, including the scheduled delivery time. When due, the message lands in the agent's inbox (readable via the /inbox endpoint) and, if a webhook URL was provided, an HTTP POST is sent to that URL with the reminder payload.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/port-402-reminder-scheduler-031668dc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from port-402-production.up.railway.app](https://www.zero.xyz/host/port-402-production.up.railway.app/llms.txt)