# nodeproxy Agent Timer

> nodeproxy Agent Timer is a paid API for AI agents from nodeproxy-production.up.railway.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Schedule a future HTTP request or payload delivery for an AI agent, firing at a specified time or after a delay without requiring the agent to stay online.

## Facts

- Endpoint: POST https://nodeproxy-production.up.railway.app/agent-timer
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nodeproxy-agent-timer-016ccbae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tQVY4t5GLIHMzn8rcYvV_

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 nodeproxy-agent-timer-016ccbae -d '<json body>'
```

Example prompt: In 10 minutes, fire a POST request to https://api.myservice.com/process with body {"jobId":"abc123"} and hold the response for me to poll — use poll mode.

## When to prefer this

Choose this endpoint when an AI agent needs to defer a web action to a future time without busy-polling or maintaining an active connection. It is ideal for agent pipelines where a step must be triggered after a delay or at a scheduled timestamp, and the agent needs to either retrieve the result later (poll) or have it pushed to a callback. Prefer this over cron services or cloud schedulers when the agent is ephemeral, stateless, or operating in a loop that cannot block.

## Known failure modes

- Invalid fire_at or delay_seconds — returns error if time is in the past or malformed
- callback_url not reachable at fire time — push delivery may fail silently or return delivery error
- HTTP action target URL unreachable — response capture may contain error or timeout
- Missing required fields (mode, action or payload) — returns validation error
- Payment not included or insufficient — returns 402 Payment Required

## How this service works

Schedule a future HTTP action or callback for autonomous agents. At a delay or a set time, either (a) execute an HTTP request you specify (method/url/headers/body) and capture the response for retrieval, or (b) deliver a JSON payload to your HTTPS callback URL (push) / hold it for polling. Lets agent loops defer and fire web actions without staying online or busy-polling.

## Output

Returns a confirmation of the scheduled timer including a unique job ID and fire time. In poll mode, once the scheduled HTTP action fires, the captured response (status, headers, body) is stored and retrievable by the agent. In push mode, the payload or HTTP result is POSTed to the specified callback_url at the fire time.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "arguments": {
   "type": "object",
   "properties": {
    "mode": {
     "enum": [
      "push",
      "poll"
     ],
     "type": "string"
    },
    "action": {
     "type": "object",
     "description": "HTTP request to execute at fire time; response captured for polling."
    },
    "fire_at": {
     "type": "number",
     "description": "Absolute fire time (epoch seconds)."
    },
    "payload": {
     "description": "JSON delivered/held at fire time."
    },
    "callback_url": {
     "type": "string",
     "description": "HTTPS URL to POST the payload/result to (push)."
    },
    "delay_seconds": {
     "type": "number",
     "description": "Seconds from now to fire."
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nodeproxy-agent-timer-016ccbae/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from nodeproxy-production.up.railway.app](https://www.zero.xyz/host/nodeproxy-production.up.railway.app/llms.txt)