# agent-exec Drift Monitor — API Endpoint Change Detector

> agent-exec Drift Monitor — API Endpoint Change Detector is a paid API for AI agents from agent-exec.45.67.221.128.sslip.io, paid per call via x402, $0.0061/call, status unknown (last checked 2026-09-15).

Fetches a live snapshot of a known API-discovery venue and compares it to a stored baseline, returning both bodies, metadata, and a diff-events list so agents can detect changes.

## Facts

- Endpoint: POST https://agent-exec.45.67.221.128.sslip.io/drift
- Price: $0.0061/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-exec-drift-monitor-api-endpoint-change-detector-cd3abb7f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YwCTGncB-rMDOUt1XwSm-

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 agent-exec-drift-monitor-api-endpoint-change-detector-cd3abb7f -d '<json body>'
```

Example prompt: Check whether the live x402-list venue has drifted from its stored baseline — fetch it now and give me the diff events, both body hashes, and HTTP statuses.

## When to prefer this

Use this endpoint when you need to compare a known API-discovery venue's current live state against a stored baseline without setting up any account or API key — ideal for lightweight agent-driven change detection on a pay-per-use basis. Prefer it over generic web-diffing tools when the target is one of the five supported x402/agent-discovery venues and you want structured diff events plus cryptographic body hashes.

## Known failure modes

- Invalid venue enum value — request rejected with validation error
- Live fetch network timeout — t2 fields may be null
- Target venue returns non-200 status — captured in t2.http_status but body may be null
- Payment failure (HTTP 402) — call not executed if x402 payment is invalid or insufficient
- SHA-256 mismatch with no events — body changed but diff parser found no structured events

## How this service works

Accountless, pay-per-use code execution for software agents: submit source code, get stdout, stderr and exit code back from an isolated, network-less sandbox. No account, no API key -- possession of valid payment is sufficient.

## Output

Returns a JSON object with two snapshots: t1 (archived baseline with URL, HTTP status, content-type, body, byte count, SHA-256, and fetch time) and t2 (live fetch with the same fields plus the final redirect URL), plus a venue label and an events array describing detected differences between the two.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "venue"
 ],
 "properties": {
  "venue": {
   "enum": [
    "agentry",
    "clearedindex",
    "percall",
    "verantis",
    "x402-list"
   ],
   "type": "string",
   "description": "One of the endpoints we already snapshot."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "venue",
  "t1",
  "t2",
  "events"
 ],
 "properties": {
  "t1": {
   "type": "object",
   "required": [
    "fetched_at",
    "url",
    "http_status",
    "content_type",
    "body_bytes",
    "body_sha256",
    "body"
   ],
   "properties": {
    "url": {
     "type": "string",
     "description": "The URL actually read. Always the baseline's recorded URL for t1; the final URL after any redirects for t2 (empty string if the live fetch never reached one)."
    },
    "body": {
     "type": [
      "string",
      "null"
     ],
     "description": "The raw body itself -- verify it yourself rather than trusting `events`. Null on t2 when the live fetch never reached a response."
    },
    "body_bytes": {
     "type": "integer",
     "description": "Bytes of body actually read and hashed."
    },
    "fetched_at": {
     "type": "string",
     "format": "date-time",
     "description": "When this side was observed -- the archived snapshot time for t1, or this request's own fetch time for t2."
    },
    "body_sha256": {
     "type": [
      "string",
      "null"
     ],
     "description": "sha256 of the body, hex-encoded, or null on t2 when the live fetch never reached a response."
    },
    "http_status": {
     "type": [
      "integer",
      "null"
     ],
     "description": "The HTTP status observed, or null on t2 when the live fetch never reached a response at all."
    },
    "content_type": {
     "type": [
      "string",
      "null"
     ],
     "description": "The Content-Type header observed, or null if none/never reached."
    }
   }
  },
  "t2": {
   "allOf": [
    {
     "type": "object",
     "required": [
      "fetched_at",
      "url",
      "http_status",
      "content_type",
      "body_bytes",
      "body_sha256",
      "body"
     ],
     "properties": {
      "url": {
       "type": "string",
       "description": "The URL actually read. Always the baseline's recorded URL for t1; the final URL after any redirects for t2 (empty string if the live fetch never reached one)."
      },
      "body": {
       "type": [
        "string",
        "null"
       ],
       "description": "The raw body itself -- verify it yourself rather than trusting `events`. Null on t2 when the live fetch never reached a response."
      },
      "body_bytes": {
       "type": "integer",
       "description": "Bytes of body actually read and hashed."
      },
      "fetched_at": {
       "type": "string",
       "f
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-exec-drift-monitor-api-endpoint-change-detector-cd3abb7f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-exec.45.67.221.128.sslip.io](https://www.zero.xyz/host/agent-exec.45.67.221.128.sslip.io/llms.txt)