# x402 Demand Changes Monitor

> x402 Demand Changes Monitor is a paid API for AI agents from srv1334799.hstgr.cloud, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Returns incremental changes in x402 demand since a given timestamp, including new/removed resources, price changes, call-volume deltas, and category movers.

## Facts

- Endpoint: GET https://srv1334799.hstgr.cloud/v1/x402/demand/changes
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-demand-changes-monitor-b38c657f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4-d7Q7JRg_3bt5KU51y2k

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 x402-demand-changes-monitor-b38c657f
```

Example prompt: What changed in the x402 Bazaar demand since 2025-06-10T00:00:00Z? Show me new resources, removed listings, price changes, and any categories with a call-volume delta of at least 50, up to 50 results.

## When to prefer this

Use this endpoint when you need incremental, change-only updates to x402 demand rather than a full market snapshot — ideal for recurring polling jobs (every 6–24 hours), change-detection pipelines, or alerting workflows where bandwidth and cost efficiency matter. Prefer this over the full demand radar when you already have a baseline snapshot and only want deltas.

## Known failure modes

- Missing required 'since' parameter returns a 400 error
- Invalid ISO-8601 timestamp format causes a parsing error
- Timestamp too far in the past may exceed retention window and return empty or partial results
- minChange filter set too high may return zero results
- limit exceeding 100 is rejected with a 400 validation error
- Expired or invalid cursor token returns a 400 or 422 error

## How this service works

Recurring agent feed for what changed in x402 demand, why it matters, recommended action, confidence, and evidence between snapshot refreshes.

## Output

An incremental diff of x402 demand activity since the specified timestamp or cursor: lists of newly added resources, removed resources, resources with price changes, call-volume delta rankings per resource, top category movers, and a nextCursor token for the next polling interval.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-demand-changes-monitor-b38c657f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from srv1334799.hstgr.cloud](https://www.zero.xyz/host/srv1334799.hstgr.cloud/llms.txt)