SoldFetch

SoldFetch answers a question resellers ask constantly: what has this actually sold for on eBay? Instead of maintaining your own scrapers, you call one API. A sold-listings search by keyword returns up to 200 results per page with the sold price, currency, end date and condition, and other endpoints cover category searches, active listings and full item details, including public seller names and feedback where available. All of them share one schema across supported eBay sites.

The responses are candid about data quality. Each one carries cache status, a fetched-at time and a request ID, and fields such as priceBasis and saleDateVerified tell you whether a figure is the displayed listing price and whether the sale date was confirmed. The homepage includes a free sold-price search with no account, and example code in Python, TypeScript and cURL.

The same operations are exposed as an MCP server, so Claude Desktop, Claude Code, Cursor, Windsurf, Codex and other MCP clients can call them as tools with one config block. There is also an installable skill that gives an agent the operation catalogue, authentication rules and schemas. The API and MCP share the same account and allowance.

Billing counts successful operations, called units, with failures and internal retries free. You start with 100 free units. Starter is $9 a month for 2,000 units, Growth $29 for 10,000 and Scale $79 for 50,000, all with request-rate limits, 30-day request logs and a hard cap at the included units rather than surprise overage.

SoldFetch turns public eBay item pages and search results into its data, and its about page describes handling the acquisition and caching on customers' behalf. Collecting data this way can conflict with eBay's terms, so it is worth checking how that affects your project. The privacy policy, last updated 22 October 2026, covers account, billing and usage data and says customers decide the purpose of the queries they send.