Find comparable listings
Search with a specific model, category, and condition.
Search → inspecteBay solution · AI agents
For eBay workflows, search sold listings and inspect selected items through REST or MCP.
/v1
GET/v1/scrapeGET/v1/scrape/categoryGET/v1/item/{itemId}Keep the evidence and uncertainty alongside every observation. Search sale dates are supplier-reported and are not independently verified.
Start with a bounded search, then inspect selected listings.
Search with a specific model, category, and condition.
Search → inspectLook up a selected item for its public details.
Item ID → detailsKeep displayed prices and reported dates separate from verified transactions.
Observation → analysisEach data request consumes at most one upstream call.
No date verification or accepted-offer hydration is included.
GET /v1/scrapeUse a keyword and enabled eBay site.
Up to 200 results per request.GET /v1/scrape/categoryChoose a relevant eBay category and condition.
Unsupported filters return an explicit error.GET /v1/item/{itemId}Read item details before deciding whether it belongs in your comparable set.
Item lookup is a separate request.A displayed listing price is an observation, not proof of a transaction amount.
Use explicit limits and quality semantics in your integration.
| Capability | SoldFetch | Typical setup |
|---|---|---|
| Requests | One upstream call per successful request | Request and retry behavior varies |
| Price basis | Displayed listing price; accepted offer unknown | Check the provider’s price semantics |
| Sale dates | Supplier-reported, unverified search dates | Verify before applying time-window analysis |
No. SoldFetch preserves the displayed price and marks the accepted amount as unknown.
One successful request, up to 200 results. Basic includes 100 requests per month; paid plans start at $9.
Yes. The MCP tools use the same authorization, limits, and quality semantics as REST.
Ask AI about this eBay API solution
Create a workspace and use the Basic plan to evaluate the API.
Request
curl -G "https://soldfetch.com/v1/scrape" \
-H "API-KEY: soldfetch_live_YOUR_API_KEY" \
--data-urlencode "keyword=mechanical%20keyboard" \
--data-urlencode "ebaySite=ebay.com" \
--data-urlencode "count=60"curl -G "https://soldfetch.com/v1/item/377534750427" \
-H "API-KEY: soldfetch_live_YOUR_API_KEY" \
--data-urlencode "ebaySite=ebay.com"Both calls use the same key, response envelope, request metadata, and documented failure model.