EzStat

• Track Metric — Record a metric point your app "produced". Use this whenever the surrounding code emits a counter or gauge — e.g. on a page view, a successful checkout, or a measured latency. Counters are +N (default +1), values are gauges (e.g. 42.5 ms).
• Ask Ezstat — Ask a natural-language question about the account's metrics. This is the agent-read path: send a question like "what spiked yesterday?" or "compare signups vs cancellations last 7 days" and EzStat returns a grounded answer plus the underlying data it used.
• Read Stat — Read a single stat: latest value, recent series, and basic summary (count/min/max/avg/sum). Use this for a structured read of one metric — prefer `ask_ezstat` for free-form questions over many stats.
• List Stats — List the account's metrics — names and types. Call this first when you don't know what stats exist in the account.
• Create Alert — Create an alert on a stat: webhook fires when the condition is met (above/below threshold, % change, heartbeat/missing data, sustained). Deliveries retry with backoff and carry a stable idempotency_key so receivers can dedup. The stat is referenced by NAME; it must already exist.
• List Alerts — List the account's alerts: id, stat, condition, channel, enabled, last trigger time.
• Delete Alert — Delete an alert by id (see list_alerts).

Schemas and invoke metadata: Directory API