eBay via Scavio

Search eBay's live listings or its SOLD listings, read a single listing in full, and pull a seller's public profile card. All endpoints return structured JSON and cost 1 credit each.

When to trigger

Use this skill when the user asks to:

• Find what something actually SOLD for on eBay (comps, resale pricing, market value)
• Search live eBay listings by keyword, price band, condition or buying format
• Filter to auctions, Buy It Now or Best Offer listings
• Read one eBay listing in full: item specifics, shipping, returns, auction state
• List everything a particular eBay seller has for sale
• Look up an eBay seller's feedback score, items sold and location
• Compare eBay resale prices against retail (pair with scavio-amazon, scavio-walmart or scavio-target)

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

Every request is a POST with a JSON body and:

Authorization: Bearer $SCAVIO_API_KEY

Endpoints

Base URL: https://api.scavio.dev. Every endpoint costs 1 credit.

Workflow

1. Price research: call /ebay/search with query and sold: true. This is the differentiating call. It searches completed listings that actually sold, which is what a comp is.
2. Live listings: call /ebay/search with query and no sold flag.
3. Read a listing: call /ebay/product with item_id (the eBay item number, or a full ebay.com/itm/... URL — tracking parameters are discarded).
4. List a seller's inventory: call /ebay/search with seller set and NO query. That is the paginated route through a seller's catalogue.
5. Seller reputation: call /ebay/seller with the username as it appears in ebay.com/usr/<name>.

/search paginates with page. /product and /seller do not paginate.

Parameters

Search (/search)

query or seller is required. At least one must be present.

Product (/product)

Seller (/seller)

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. What did it actually sell for? (the price-research call)
sold = requests.post(f"{BASE}/api/v1/ebay/search", headers=HEADERS,
    json={"query": "nintendo switch oled", "sold": True, "condition": "used"}).json()

# 2. Live listings, cheapest first, 120 per page
live = requests.post(f"{BASE}/api/v1/ebay/search", headers=HEADERS,
    json={"query": "nintendo switch oled", "sort_by": "price_low", "per_page": 120}).json()

# 3. One listing in full
item = requests.post(f"{BASE}/api/v1/ebay/product", headers=HEADERS,
    json={"item_id": "168591664725"}).json()

# 4. A seller's whole catalogue: /search with seller and no query
catalogue = requests.post(f"{BASE}/api/v1/ebay/search", headers=HEADERS,
    json={"seller": "red-rock-uk", "page": 1}).json()

# 5. That seller's reputation card
profile = requests.post(f"{BASE}/api/v1/ebay/seller", headers=HEADERS,
    json={"seller": "red-rock-uk"}).json()

Response

Every response uses the envelope { data, response_time, credits_used, credits_remaining }.

• search returns the listing rows with price, condition, bids, shipping, seller and feedback, alongside count and total_results.
• product returns price, condition, images, item specifics, shipping, returns, auction state and seller.
• seller returns store name, feedback score and percentage, items sold, followers, location and categories.

total_results is null when sold: true. eBay publishes no headline count on the sold view, so a null there means "eBay did not say", not "zero results". Count the returned rows instead.

Guardrails

• Never fabricate prices, item numbers, sold dates, feedback scores or seller names. Only return data the API returned.
• /seller is a PROFILE endpoint. It cannot enumerate a catalogue. If the user wants a seller's items, use /search with seller set and no keyword.
• per_page accepts only 60, 120 or 240. eBay silently falls back to 60 for any other value, so a request for 100 quietly returns 60 and looks successful.
• category_id must be numeric. An unrecognised category id returns the UNFILTERED result set under a 200, which looks like a successful filter and is not one. Verify the id before relying on it.
• condition: "refurbished" is eBay's parent condition, not one of its three graded refurbished tiers. Do not present it as a specific grade.
• There is no "Distance: nearest first" sort. It ranks against the proxy exit rather than the caller's location, so it is deliberately absent. Never recommend it.
• Sold-listing prices are historical. When quoting them as a market value, say when the sale happened.
• Always include the listing URL so the user can verify.

Failure handling

• 400 means an invalid or missing parameter, most often neither query nor seller being supplied. Fix and retry.
• 401 means the API key is invalid or missing. Check SCAVIO_API_KEY.
• 404 means the item or seller was not found. Check the item number or the ebay.com/usr/<name> spelling.
• 429 means a rate or usage limit was exceeded. Wait before retrying. See https://scavio.dev/docs/rate-limits.
• 502 / 503 mean the upstream is temporarily unavailable. Wait a few seconds before retrying.
• If a sold search returns nothing, widen the keywords before concluding the item never sold. Sold-view matching is stricter than the live view.
• If SCAVIO_API_KEY is not set, prompt the user to export it before continuing.

Docs

• Search: https://scavio.dev/docs/ebay-search
• Product: https://scavio.dev/docs/ebay-product
• Seller: https://scavio.dev/docs/ebay-seller