Machine access · Identifier resolver

Resolve a product by its identifier

You already hold the join-key — an Amazon ASIN from a catalog, a feed, or a shopping agent's context. Point it at us and it dereferences to our independent, dated record of that exact product. No scraping, no search, no private slug to look up.

1,146 ASINs resolve today — every product for which we cite a retailer page. Each identifier returns three representations of the same sourced, dated price history, so a human, a search engine, and an LLM each get the format they read best:

JSON-LD entity for agents

/id/asin/<ASIN>.jsonld — the Product + Offer node with productID/sku/sameAs set to the ASIN and the agent-decision price signals inline: lowest and highest recorded price, current price vs the lowest on record, and the number of dated observations. The surface a shopping agent consumes to answer "is this a good price right now?".

Markdown fact-sheet for LLMs

/id/asin/<ASIN>.md — the token-efficient sourced facts, resolution line first.

HTML page for people

/id/asin/<ASIN> — price of record, provenance, and a link to the full comparison.

Live example: /id/asin/B0FDQP54X8 (.jsonld · .md).

Why resolve through us

The ASIN is the identifier your side already has; the value we add is the part the retailer keeps to itself — a dated price history, each point sourced and verifiable, published as an open CC-BY dataset (DOI). Every figure carries the URL it was captured from and the date we recorded it, so any number an agent quotes is checkable in one click.

What's next

GTIN/UPC resolution (/id/gtin/<GTIN>) — the retailer-agnostic key that also identifies a product in Google Shopping and Wikidata — is on the roadmap as we enrich the dataset with the barcodes behind each cited page. See the full machine-access index in llms.txt.