HALOWERK Price History New Low Detector

Choose this endpoint when you need to programmatically determine whether a newly observed price for a specific article represents a historical minimum, especially in automated price-monitoring pipelines or deal-detection workflows. It is particularly suited when you already have a structured price history array (up to 60 entries) and a previously known low, and want a definitive computational answer rather than doing the min-detection logic yourself. Prefer it over manual comparison when operating in a multi-agent commerce automation context that already uses x402 micropayment infrastructure.

• Fewer than 3 history items provided — schema requires minItems:3
• History items missing required fields (url, observed_at, value, currency) — validation error
• Currency code not matching ISO 3-letter format — pattern mismatch
• Price value exceeding maximum of 1,000,000,000 — schema rejection
• Duplicate or non-idempotent requests without a valid idempotency_key — potential double-billing
• Payment not received or insufficient USDC balance — x402 payment required response
• Callback URL malformed or unreachable — callback delivery failure