Walmart via Scavio

Search Walmart, read a product in full, page its customer reviews, list a category, look up the buy-box offer on an item, read a marketplace seller's storefront and catalog, and find Walmart stores near a ZIP or postal code so search and product results can be targeted at one store. All endpoints return structured JSON.

When to trigger

Use this skill when the user asks to:

• Search Walmart for products by keyword, price band or sort order
• Look up a Walmart item by its item id (usItemId)
• Read customer reviews and the rating breakdown for a Walmart product
• List the products inside a Walmart category
• Check who holds the buy box on a Walmart listing and at what price
• Look up a Walmart marketplace seller: rating, review count, Pro Seller badge
• See what a Walmart marketplace seller lists
• Compare Walmart pricing against another retailer (pair with scavio-amazon, scavio-ebay or scavio-target)
• Search the Canadian (walmart.ca) or Mexican (walmart.com.mx) marketplace
• Find the Walmart stores near a US ZIP or Canadian postal code
• See what a specific Walmart store carries, or a product's availability at that store (walmart.com and walmart.ca)

Setup

Get a free API key at scavio.dev (50 free credits to get started, no card required):

export SCAVIO_API_KEY=sk_live_your_key

If you do not have a key yet

An agent running this skill without SCAVIO_API_KEY set will get 401 on every call below. The whole path from nothing to a working key is self-serve:

1. Sign up at dashboard.scavio.dev - email or Google, no card required.
2. A key is created for the account automatically at signup. It is on the dashboard under API Keys, ready to copy.
3. A new account starts with 50 credits. Endpoints in this skill cost 1 credit each unless the table below says otherwise.

When the balance runs out the API answers 402 with a JSON body carrying billing_url. Topping up needs no code change - the same key keeps working. The smallest purchase is 2,500 credits for $25, and monthly plans work out cheaper per credit if the usage is steady rather than one-off.

Every request is a POST with a JSON body and:

Authorization: Bearer $SCAVIO_API_KEY

Endpoints

Base URL: https://api.scavio.dev.

Cost rule

Cost is a function of the request body, not a constant. Two things change it:

• domain: "com" (US, the default) costs 1 credit
• domain: "ca" (Canada) costs 1 credit
• domain: "com.mx" (Mexico) costs 2 credits, on /search and /category
• A store-targeted request (store_id + delivery_zip) on /search or /product costs 2 credits, on walmart.com or walmart.ca

So /search can cost 2 through either rule, /category only through com.mx, and /product only through store targeting. /reviews, /offers, /seller, /seller-products and /stores are always 1 credit. Never quote a flat price for search, category or product without stating the rule.

Workflow

1. Find items: call /walmart/search with query. The item id is id on each row of data.products[] — that is the value the other endpoints take as product_id.
2. Read an item: call /walmart/product with product_id.
3. Reviews: call /walmart/reviews with the same product_id, paging with page (10 reviews per page).
4. Browse a category: call /walmart/category with category_id.
5. Buy box: call /walmart/offers with product_id to see who currently wins the buy box and at what price.
6. Sellers: a product, search or offers response carries seller_catalog_id. Pass that numeric id as seller_id to /walmart/seller for the storefront and to /walmart/seller-products for the catalog.
7. Target a store: call /walmart/stores with zipcode (add "domain": "ca" for a Canadian postal code). Pick a store_id from data.stores[], then send it with delivery_zip (and the same domain) to /walmart/search or /walmart/product. The results reflect that store's assortment and availability, and data.location confirms the store that was used. Store-targeted calls take 10-60 seconds.

search, reviews and category paginate with page (1-based). product, offers, seller, seller-products and stores do not paginate at all — there is no page or cursor parameter on them.

Parameters

Search (/search)

Product (/product)

Reviews (/reviews)

Category (/category)

Offers (/offers)

Seller (/seller) and seller products (/seller-products)

Stores (/stores)

Examples

import requests

BASE = "https://api.scavio.dev"
# Your key from https://scavio.dev. Load it from your environment or secret
# store in real code - keep it out of source control.
API_KEY = "sk_your_key_here"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}

# 1. Search (1 credit on the default com domain)
results = requests.post(f"{BASE}/api/v1/walmart/search", headers=HEADERS,
    json={"query": "wireless headphones", "sort_by": "price_low", "max_price": 100}).json()

product_id = results["data"]["products"][0]["id"]   # search rows carry `id`, not `product_id`

# 2. Full product detail
product = requests.post(f"{BASE}/api/v1/walmart/product", headers=HEADERS,
    json={"product_id": product_id}).json()

# 3. Reviews, page 2 (10 per page)
reviews = requests.post(f"{BASE}/api/v1/walmart/reviews", headers=HEADERS,
    json={"product_id": product_id, "page": 2, "sort": "rating-desc"}).json()

# 4. Buy box for an item
offers = requests.post(f"{BASE}/api/v1/walmart/offers", headers=HEADERS,
    json={"product_id": "2979510112"}).json()

# 5. Seller storefront, then their catalog (numeric seller_catalog_id)
seller = requests.post(f"{BASE}/api/v1/walmart/seller", headers=HEADERS,
    json={"seller_id": "101480084"}).json()
catalog = requests.post(f"{BASE}/api/v1/walmart/seller-products", headers=HEADERS,
    json={"seller_id": "101480084"}).json()

# 6. Mexican marketplace search: this call costs 2 credits, not 1
mx = requests.post(f"{BASE}/api/v1/walmart/search", headers=HEADERS,
    json={"query": "audifonos", "domain": "com.mx"}).json()

# 7. Stores near a ZIP, then one store's search results (2 credits, 10-60s)
stores = requests.post(f"{BASE}/api/v1/walmart/stores", headers=HEADERS,
    json={"zipcode": "50036"}).json()
store_id = stores["data"]["stores"][0]["store_id"]   # nearest first, e.g. "1389"
local = requests.post(f"{BASE}/api/v1/walmart/search", headers=HEADERS, timeout=120,
    json={"query": "whole milk", "delivery_zip": "50036", "store_id": store_id}).json()
print(local["data"]["location"])   # the store the results were served against

# 8. Same on walmart.ca: postal code + domain "ca" on both calls
ca_stores = requests.post(f"{BASE}/api/v1/walmart/stores", headers=HEADERS,
    json={"zipcode": "M5V 2T6", "domain": "ca"}).json()

Response

Every response uses the envelope { data, response_time, credits_used, credits_remaining }, plus an optional warnings[] array of strings when part of the request was ignored (a retired parameter, zipcode sent to search or product, or store parameters sent to an endpoint that does not take them).

• search puts the rows in data.products[] with data.products_count, and reports the Walmart store the results were served against in data.location. category returns the same product shape as search.
• product returns price, rating, images, specifications, availability and seller.
• reviews returns the review bodies with ratings, text, author and date, plus the rating breakdown.
• offers returns price, seller, condition and the buy-box flag.
• seller returns store name, rating, review count, Pro Seller badge and business details.
• seller-products returns the seller's catalog with total_count.
• stores returns data.stores[] nearest first: store_id, name, type, distance_miles, address, latitude, longitude, open_24_hours, hours and pickup_types, plus zipcode, domain and count.

Read credits_used on the response rather than assuming a cost, since search, category and product are body-priced.

Changed in 3.1.0

• New /walmart/stores endpoint: stores near a US ZIP or Canadian postal code.
• delivery_zip and store_id work again on /search and /product, sent together, on walmart.com and walmart.ca. They target one store's assortment and availability and cost 2 credits. /product accepts domain: "ca" with them.
• device is now the only retired parameter.

Changed in 3.0.0

If you have an older version of this skill installed, stop sending these. The API answers device with a warnings[] entry rather than an error, which means a request that looks successful was silently unfiltered:

• device is gone. Desktop, mobile and tablet return identical page data, so the response would not change.
• fulfillment_speed: "2_days" is gone. It leaked items 3-4 days out.
• fulfillment_speed: "anytime" is gone. It was a no-op. To mean "anytime", omit the parameter entirely.

domain is NOT retired. It is live, it can change the price, and it is the only way to reach walmart.ca and walmart.com.mx.

New since 2.x: /reviews, /category, /offers, /seller and /seller-products. sort_by gained rating_high and new. search and product both changed response shape.

Guardrails

• Never fabricate product names, prices, item ids, ratings or availability. Only return data the API returned.
• /offers returns the BUY-BOX SELLER ONLY. It is not the full offer list, and must never be described as one. If the user wants every seller on an item, say that this API cannot enumerate them.
• /seller-products returns roughly the first 40 items, server-rendered. There is no pagination on it. total_count reports the seller's real catalog size, so the two numbers will disagree and that is expected. Do not invent a page parameter.
• seller_id must be the NUMERIC catalog seller id from seller_catalog_id. The GUID form of seller_id returns 404.
• domain is accepted on /search, /category and /stores, and on /product only as "ca" together with a store target. The other id-keyed endpoints are US-only.
• delivery_zip and store_id must be sent together, and only on /search and /product. One alone is a 400. Get store_id from /walmart/stores on the same domain; a store_id that does not exist is a 400. Store targeting works on walmart.com and walmart.ca, not walmart.com.mx.
• store_id decides the store. Always read data.location to confirm which store the results came from, and tell the user.
• A store-targeted product can return 404 when that store does not carry the item, even if it exists elsewhere. Say so rather than retrying.
• Store-targeted calls take 10-60 seconds. Use a client timeout of at least 120 seconds.
• limit on /category trims the response after fetching. It does not reduce the credit cost.
• category_id accepts either the leaf id or the full underscore-joined path.
• sort_by, fulfillment_speed, fulfillment_type and domain are closed enums - a value outside them is a 400. Send only the values listed above; in particular fulfillment_speed no longer accepts 2_days or anytime, and to mean "anytime" you omit the parameter.
• Always include the product URL so the user can verify and complete the purchase.

Failure handling

• 400 means an invalid or missing parameter. Fix and retry. On a store-targeted call it can also mean store_id is not a real store, or only one of delivery_zip / store_id was sent.
• 401 means the API key is invalid or missing. Check SCAVIO_API_KEY.
• 404 on /seller or /seller-products almost always means a GUID was sent instead of the numeric seller_catalog_id. On a store-targeted /product it means the store does not carry the item.
• 429 means a rate or usage limit was exceeded. Wait before retrying. See rate limits.
• 502 / 503 mean the upstream is temporarily unavailable. Transient 502s happen on Walmart; wait a few seconds and retry once before reporting failure.
• If a response carries warnings[], surface it to the user. It means part of their request was ignored.
• If search returns nothing, relax the filters (drop fulfillment_speed, widen min_price/max_price) and retry.
• If SCAVIO_API_KEY is not set, prompt the user to export it before continuing.

Docs

• Walmart search
• Walmart product
• Walmart reviews
• Walmart category
• Walmart offers
• Walmart seller
• Walmart seller products
• Walmart stores