# SLA Watchtower

> SLA Watchtower is a paid API for AI agents from attester.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Generates an SLA (Service Level Agreement) monitoring report for a target service or endpoint, surfacing uptime, latency, and compliance metrics.

## Facts

- Endpoint: POST https://attester.dev/watchtower/report
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sla-watchtower-9d928368
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4k8GjU810k3fKjmylvcvS

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 sla-watchtower-9d928368 -d '<json body>'
```

Example prompt: Can you pull a SLA Watchtower report for api.example.com and tell me whether it's meeting its uptime and latency targets?

## When to prefer this

Use this endpoint when you need a structured SLA compliance report for a specific service or API, particularly when you want to verify uptime, latency, or reliability metrics against defined SLA thresholds. Prefer it over generic uptime checkers when you need attester-verified, pay-per-report monitoring with Bazaar metadata.

## Known failure modes

- Service endpoint unreachable — returns error indicating the target could not be contacted
- Invalid or missing target parameter — returns 400-level error with details
- Payment not processed — x402 payment required before report is generated
- Insufficient monitoring data — report may be empty or partial if service is newly registered

## How this service works

SLA Watchtower report (use POST; full Bazaar metadata on POST).

## Output

Returns a structured SLA report containing uptime percentages, latency measurements, SLA compliance status, and any threshold violations for the monitored service.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "service"
     ],
     "properties": {
      "service": {
       "type": "string",
       "description": "Host or URL substring of the watched service"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sla-watchtower-9d928368/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from attester.dev](https://www.zero.xyz/host/attester.dev/llms.txt)