# CrushRewards Price History

> CrushRewards Price History is a paid API for AI agents from api.crushrewards.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns historical price observations for a product over a date range, including current price, period low/high/avg, trend direction, and a good-deal flag.

## Facts

- Endpoint: GET https://api.crushrewards.dev/v1/shopper/price-history
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-crushrewards-dev-ab9fd2c7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lJdnbHgFhiJwElyIIYbg7

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 api-crushrewards-dev-ab9fd2c7
```

Example prompt: Can you pull up the price history for 'Sony WH-1000XM5 headphones' on Amazon in the US from January 1 to June 30 this year, and tell me if it's currently a good deal based on the trend?

## When to prefer this

Use this endpoint when you need historical price data and trend analysis for a specific product at a specific retailer, including whether the current price is a good deal relative to its history. Prefer this over category-level or brand-level endpoints when the user has a specific product in mind and wants a time-series for charting or a buy/wait recommendation.

## Known failure modes

- No matching product found for the query — returns empty or null result
- Invalid date format (non-ISO 8601) causes a 400 validation error
- Unsupported retailer or country code causes a 400 validation error
- Query string too short or missing causes a 400 required-field error
- Payment not processed or x402 header missing causes a 402 Payment Required error
- Date range with no historical data returns an empty observations array

## How this service works

Real-time pricing, promotions, and competitive intelligence across US and Canadian retailers — exposed as paid API endpoints and MCP tools that AI agents can call directly, with x402 and MPP micropayments per query.

## Output

Returns a JSON object with the matched product name, retailer, currency, current price, period low/high/average prices, a trend enum (rising/falling/stable), a boolean good-deal flag, and a dated time-series array of price observations suitable for charting.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "q": "laptop"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-crushrewards-dev-ab9fd2c7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.crushrewards.dev](https://www.zero.xyz/host/api.crushrewards.dev/llms.txt)