# three.ws x402 Notification Endpoint

> three.ws x402 Notification Endpoint is a paid API for AI agents from three.ws, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-23).

Sends a notification message to a specified delivery channel (canary, ops, or system) with a priority hint, returning delivery confirmation and latency metadata.

## Facts

- Endpoint: POST https://three.ws/api/x402/notify?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/three-ws-x402-notification-endpoint-379fce49
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qy2Y58fDdqVn0YK337-1G

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-x402-notification-endpoint-379fce49 -d '<json body>'
```

Example prompt: Send a normal-priority notification to the ops channel with the message 'Agent loop healthy — all systems nominal'.

## When to prefer this

Choose this endpoint when you need to send lightweight, real-time notifications within the three.ws 3D agent ecosystem — especially for autonomous loop heartbeats (canary channel), operational alerts (ops channel), or system-level events. It is particularly suited for agentic workflows that require x402 micropayment-gated messaging and need delivery confirmation with latency telemetry.

## Known failure modes

- Message exceeds 500 character limit — request rejected with validation error
- Invalid channel enum value — must be 'canary', 'ops', or 'system'
- Invalid priority enum value — must be 'low', 'normal', or 'high'
- Payment not provided or insufficient USDC — x402 payment required before delivery
- Delivery failure — delivered: false returned with latency_ms still populated
- Network timeout to downstream notification system

## 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 confirming delivery with fields: notification_id (UUID), delivered (boolean), latency_ms (integer), ts (ISO 8601 timestamp), channel, message, priority, and payer (null if no payer context).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "channel": {
   "enum": [
    "canary",
    "ops",
    "system"
   ],
   "type": "string",
   "default": "canary",
   "description": "Delivery channel. \"canary\" is the autonomous-loop heartbeat lane."
  },
  "message": {
   "type": "string",
   "default": "x402 loop heartbeat",
   "maxLength": 500,
   "description": "Notification message body."
  },
  "priority": {
   "enum": [
    "low",
    "normal",
    "high"
   ],
   "type": "string",
   "default": "low",
   "description": "Delivery priority hint."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ts": "2026-06-28T10:00:00Z",
  "payer": null,
  "channel": "canary",
  "message": "x402 loop heartbeat",
  "priority": "low",
  "delivered": true,
  "latency_ms": 18,
  "notification_id": "a3f3d6c2-1f1b-4f10-9b6c-1b1f5e0c9c34"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/three-ws-x402-notification-endpoint-379fce49/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)