# three.ws Telegram Bot Health Check

> three.ws Telegram Bot Health Check is a paid API for AI agents from three.ws, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Probes whether the three.ws changelog Telegram bot is reachable and returns latency and status information.

## Facts

- Endpoint: POST https://three.ws/api/x402/telegram-health?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/three-ws-telegram-bot-health-check-6a54c93c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_o7iRbq0L-b0F6eCBzdGK_

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 three-ws-telegram-bot-health-check-6a54c93c -d '<json body>'
```

Example prompt: Can you check whether the three.ws changelog Telegram bot is currently reachable and tell me its response latency?

## When to prefer this

Use this endpoint when you need a real-time, paid health-check signal for the three.ws changelog Telegram bot specifically. Prefer it over generic uptime tools when you need bot-specific metadata like bot_id and bot_username alongside reachability. Useful in automated monitoring pipelines that require verified, timestamped proof of bot status.

## Known failure modes

- Bot is unreachable — reachable returns false with a reason string explaining the failure
- Invalid bot enum value — request rejected if anything other than 'changelog' is passed
- Telegram API timeout — latency_ms may be very high or null if the probe itself times out
- Payment failure — x402 micropayment of $0.001 USDC must succeed before the probe is executed

## How this service works

Make a 3D AI agent from a selfie in 60 seconds. Drop one HTML tag to embed it on any website. Agents think on IBM watsonx.ai (Granite); optionally charge per chat with built-in micropayments.

## Output

Returns a JSON object with the bot name ('changelog'), its Telegram bot ID, username, a boolean reachability flag, the latency in milliseconds at time of check, a timestamp of when the check was performed, and a reason string (null if reachable, error description if not).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "bot": {
   "enum": [
    "changelog"
   ],
   "type": "string",
   "description": "Which platform bot to probe."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "bot": "changelog",
  "bot_id": 7234567890,
  "reason": null,
  "reachable": true,
  "checked_at": "2026-06-28T12:00:00.000Z",
  "latency_ms": 142,
  "bot_username": "three_ws_bot"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/three-ws-telegram-bot-health-check-6a54c93c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from three.ws](https://www.zero.xyz/host/three.ws/llms.txt)