# Aegis Monitor — x402 HTTP Endpoint Watcher

> Aegis Monitor — x402 HTTP Endpoint Watcher is a paid API for AI agents from aegis.borisinc.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-13).

Registers an HTTP endpoint for monitoring and returns a monitor ID with expiry, enabling ongoing trust and availability tracking for x402 agent-payable services.

## Facts

- Endpoint: POST https://aegis.borisinc.com/monitor
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aegis-monitor-x402-http-endpoint-watcher-2beb0739
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Rm1Wd5bzVTLlhdEM0QVQC

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 aegis-monitor-x402-http-endpoint-watcher-2beb0739 -d '<json body>'
```

Example prompt: Set up monitoring on Aegis for my x402 service at https://api.myservice.com/x402 — use a POST method with JSON body, and send callbacks to https://hooks.myservice.com/aegis-alert whenever the status changes.

## When to prefer this

Choose this endpoint when you need to register and continuously monitor an x402 agent-payable HTTP service for uptime, availability, and trust-signal generation within the Aegis ecosystem. Prefer it over generic uptime tools when the target service participates in the x402 payment protocol and you want trust scores and registry presence backed by real purchase history.

## Known failure modes

- Missing required fields (url or callback) returns a 400 validation error
- Invalid callback URI format causes schema rejection before submission
- Non-whitelisted HTTP methods (e.g. GET, DELETE) are rejected by the enum constraint
- Expired or already-registered monitors may return conflict or duplicate errors
- Payment failure (insufficient USDC) results in 402 rejection before monitor is created

## How this service works

Search 2,400+ x402 services ranked by delivery-verified trust. Free discovery, paid trust checks, payment routing with failover. We buy from sellers to prove they deliver.

## Output

Returns a JSON object with the monitored URL, a monitor_id (e.g. 'mon_abc') for future reference, and a Unix timestamp indicating when the monitoring session expires.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "callback": {
   "type": "string",
   "format": "uri"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "url": "https://api.example.com/x402",
  "expires": 1786000000,
  "monitor_id": "mon_abc"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aegis-monitor-x402-http-endpoint-watcher-2beb0739/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aegis.borisinc.com](https://www.zero.xyz/host/aegis.borisinc.com/llms.txt)