Stablecoin/depeg watch

The problem it solves

Stablecoin risk does not announce itself. A peg can deteriorate quietly while a team watches dashboards that refresh too slowly, and by the time the move is visible in price it is already a market event.

What a result looks like

A typed WATCH v2 result: the subject's current evidence state, the material-change verdict for the window, freshness, evidence roots and the billing metric (CHECK or CHANGE). The exact schema is compiled into /catalog.json and /openapi.json.

Plain price

Checks $0.001 each · material-change delivery $0.01

Check and change prices are the canonical catalog targets; the deterministic quote engine remains authoritative per request.

Freshness and evidence promise

Every check is source-grounded and freshness-stamped; a change delivery carries its evidence roots and remains replay-safe by idempotency id. No unpaid delivery is ever counted as settlement.

Try it with x402 / the API

Machines call the canonical payable endpoints - discovery starts atFor Machines, the live contract at /openapi.json, and the catalog at /catalog. Every inbound route resolves to the canonical x402 Revenue Collection Wallet; the address is advertised by the canonical surface, never copied onto this page.

Schema and docs

The result schema, examples, errors and payment semantics are compiled from the canonical catalog: see /catalog and the operation definitions in /openapi.json.

Related products

• Protocol 360
• Embedded/OEM usage unit

Monitoring and OEM path

This is the recurring face of the capability: subscribe a subject once and receive material changes instead of polling. OEM embedding is available through the embedded/OEM usage unit.