> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usealmanac.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This handbook preview targets personal CLI 0.11.1. Check installed command help and the matching backend schema before using examples with another release. Examples with named people and placeholder IDs are fictional.

# Research products and prices

> Preserve the market context and product identity when moving from search to detail.

A product search produces candidate listings. A detail read can answer a question the snippet leaves open, but its price, stock and shipping context may differ by market and time. Compare returned titles, currency and original product URLs; do not fill in missing prices or assume a shipping region the user did not give.

Amazon product search currently requires both country and postal code. This example uses the US/10001 context **only as an explicit sample market**, not as the reader's location:

```sh theme={"theme":{"light":"github-light","dark":"vesper"}}
almanac web search --source amazon --type product 'mechanical keyboard' --country us --postal-code 10001 --output keyboards.json
```

Carry the returned ASIN into a detail read with the **same** country and postal code:

```sh theme={"theme":{"light":"github-light","dark":"vesper"}}
almanac web read --source amazon --type product --asin B09JG7KRC7 --country us --postal-code 10001 --output keyboard-detail.json
```

That ASIN came from a September 2026 study. Its detail read supplied specifications absent from its search snippet, while another studied product's detail contained empty feature/specification fields. A missing detail is not evidence that a product lacks the feature. The reported USD prices were snapshots for the disclosed US/10001 query; delivery, tax, availability and another region were not checked.

`google-shopping`, `walmart`, `etsy`, `shopify`, `appstore` and `googleplay` expose different product or app identities. Use the [source directory](/web/sources) and the chosen operation's `web describe` contract. A returned product URL is an original locator; it does not imply that another source uses the same ID or regional price.