Analytics and monitoring decision
SoldComps
A small, single-developer replacement is realistic: the core is a keyword→scrape→parse→JSON pipeline and can be built and hosted in about a week, but the vendor's main advantage is ongoing parser maintenance and operational polish that you'll need to sustain yourself.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off34 h to build
$80/mo4 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Accept a keyword and query eBay search results, fetch up to N result pages, parse each listing into a stable JSON schema, and return up to 240 sold listings in one response with pagination and rate-limiting.
What it still won’t have
- Parser maintenance and uptime guarantees (they monitor eBay and ship same-day fixes)
- Priority support and managed rate-limit/resilience features for high-volume keys
- Polish around edge cases, multi-market quirks, and versioned stable API contract
- Built-in Max Mode server-side pagination and signed CSV/email delivery
What remains hard
- Execution quality
What happens if eBay changes their HTML? That's our problem, not yours. We monitor every site and ship parser updates the same day a change ships — usually within the hour.
First-year cost
No published price
SoldComps does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal SoldComps-compatible REST API in Node.js: use Playwright for fetching eBay search result pages, Express for the API, Redis for simple rate-limits, and Docker for deployment. Implement GET /v1/scrape?keyword=... with parameters (page, count, ebaySite, categoryId, minPrice, maxPrice, itemCondition) that returns up to 240 sold listings per request in JSON matching the documented schema (soldPrice, soldCurrency, endedAt, title, url, sellerFeedbackScore, condition, shippingPrice, hasNextPage). Out of scope: Max Mode server-side pagination delivery channels (email/CSV), RapidAPI channel, and multi-tenant billing. Include retries/backoff, HTML change detection logging, unit tests for parsing, integration tests for the endpoint, and CI that builds and runs tests. Provide deployment instructions for a single small VPS (systemd + Docker) and configuration for 1 container, 2GB RAM, and a cron healthcheck.
How we checked
How the score was reached
- Build verdict base78
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score85
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productSoldComps — eBay Sold Listings API
- official pricingPrice Estate Sale Inventory with eBay Sold Data — SoldComps
- official docsSoldComps API Reference
Integrity checks
What held up, and what did not.
