SoldFetch 推出 eBay 成交刊登 API 与 MCP 服务

eBay sold listings. One simple API call.

Get up to 200 eBay sold listings in one request, with displayed prices, condition, shipping, and seller details when available. Built for resellers, pricing tools, and developers.

3 data operations · supported eBay sites · 100 free units

example response · ready

import requests

response = requests.get(
    'https://soldfetch.com/v1/item/377534750427',
    params={'ebaySite': 'ebay.com'},
    headers={'API-KEY': 'soldfetch_live_YOUR_API_KEY'}
)
data = response.json()

[ .JSON ]

{
  "itemId": "377534750427",
  "title": "Example eBay listing",
  "price": "37.00",
  "currency": "USD",
  "ended": true,
  "endedDate": "2026-10-07T22:10:49Z"
}

Explore the API catalog

Explore SoldFetch’s most-used eBay APIs

Product Search Categories Sold listings Items

The unified eBay data API for developers

Fast, consistent, and ready for agents: three reasons teams use SoldFetch instead of maintaining a pile of marketplace scrapers.

One eBay contract

Sold searches, category searches, and item details use one predictable model.

Explore the APIs

Every interface included

Use REST, MCP tools, or an installable eBay skill with the same account and request allowance.

Read the docs

Freshness you can see

Cache status, fetched-at timestamps, request IDs, stable errors, and usage metadata travel with every response.

See the contract

02 — Use cases

What you can build with eBay data

Price research, inventory tools, category discovery, seller context — all from the same normalized operation catalog.

Price monitoring

Ground resale prices in observed listings

Compare displayed sold prices and conditions, preserving source links and uncertainty.

Example A$89.99Used

Example B$91.20Used

Example C$94.00New

Product research

Move from category discovery to comparable listings

Search categories, narrow by condition and price, then inspect individual eBay listings.

Illustrative price distributionExample data

Inventory research

Research items before you buy

Use structured listing observations to support sourcing and inventory decisions.

Used72%

New21%

Other7%

Seller intelligence

Understand the public seller landscape

Inspect public seller names, feedback, and listing details alongside each comparable.

Example A99.8% feedbackUsed

Example B98.5% feedbackNew

Example C99.2% feedbackUsed

03 — Coverage

3 APIs, one schema

Every SoldFetch eBay endpoint in one catalog. Click any API to inspect its allowlisted request, run the preset, and grab the code.

Click any API tile to open its playground

04 — AI ready

Connect with AI agents

Plug SoldFetch into Claude, Cursor, Codex, or any MCP-compatible client. Or install the Skill so your agent starts with bounded eBay capabilities.

MCPDrop-in for any MCP client

Native tools for every MCP-compatible agent

One JSON block gives your agent the SoldFetch eBay operations as first-class tools. Typed inputs, stable errors, usage metadata, and provider routing stay behind the contract.

Claude Desktop
Cursor
Windsurf
Codex
Claude Code
OpenAI Agents

{
  "mcpServers": {
    "soldfetch": {
      "url": "https://soldfetch.com/api/mcp",
      "headers": { "API-KEY": "soldfetch_live_..." }
    }
  }
}

See the MCP guide

SkillClaude · Codex · Cursor

Install the Skill once

Your agent gets the operation catalog, authentication rules, schemas, and examples as a known capability.

curl -fsSL https://soldfetch.com/skills/ebay-data/SKILL.md \
  -o .agents/skills/ebay-data/SKILL.md

RESTSame contract · same key

Ship the same call in code

Move from an agent tool to a production REST request without changing the underlying eBay operation.

curl 'https://soldfetch.com/v1/scrape?keyword=sony%20wh-1000xm5&count=60' \
  -H 'API-KEY: soldfetch_live_...'

Provider-neutral acquisition

Ask once. Get a normalized answer.

SoldFetch owns source requests, cache policy, marketplace differences, validation, and normalization. Your application receives one stable contract.

One request contract

Every provider and marketplace resolves through the same public operation, validation rules, and response schema.

Browse the APIs

Failures stay explicit

Stable error codes distinguish validation, authentication, quota, provider, and timeout failures without leaking internals.

Inspect error contracts

Freshness travels with data

Cache state, fetched-at time, request ID, schema version, and usage metadata are visible instead of implied.

See live status

Before — you orchestrate

Source A · productSource B · offersCache · freshnessParser · normalizationRetries · failoverLedger · usage

After — SoldFetch does it

GET/v1/item/ITEM_ID

"cached":  true
"schema":  "v1"
"usage":   1

Source requests, cache, normalization, and metering → one request.·One successful result → one unit.

05 — Scale

Built to replace your eBay data stack

3Marketplaces coveredUS · UK · Germany at launch

3API operationsOne schema · one auth

2InterfacesREST · MCP · installable Skill

100Free units on signupNo card · no commitment

06 — Pricing

Pay for useful data. Never for failures.

One successful search page or item lookup uses one request. Replaying a successful idempotency key does not charge again.

Basic

For prototypes and evaluation

100 units

Start free

60 requests / minute
5 concurrent requests
30-day request logs
REST & MCP

Starter

For production eBay workflows

2,000 units

$9/ month

Choose Starter

60 requests / minute
5 concurrent requests
30-day request logs
REST & MCP

Growth

For production eBay workflows

10,000 units

$29/ month

Choose Growth

60 requests / minute
5 concurrent requests
30-day request logs
REST & MCP

Scale

For production eBay workflows

50,000 units

$79/ month

Choose Scale

60 requests / minute
5 concurrent requests
30-day request logs
REST & MCP

Compare plans and estimate usage

Start building

Put live eBay data behind one stable request.

Create an organization key, run a known-good sample, and keep marketplace volatility behind SoldFetch.

product

October 9, 2026 · 10 min read

Moving an eBay Integration to SoldFetch

Plan an eBay API migration with familiar endpoint paths, explicit capability checks, response mapping, quota accounting, and a staged rollout.

Read article

skills

October 9, 2026 · 9 min read

eBay Item API Guide: Look Up a Listing by Item ID

A practical guide to retrieving eBay listing details, preserving price and marketplace context, and handling missing fields, caching, and API errors.

Read article

development

October 9, 2026 · 9 min read

Build an eBay Price Tracking Workflow

Track eBay listing observations with a stable comparison set, explicit price uncertainty, durable history, bounded pagination, and useful change alerts.

Read article

Straight answers

The details that matter before you move a marketplace-data workflow into production.

What eBay data can I query?

SoldFetch provides eBay sold and active search, category search, and item details. Search returns up to 200 records; displayed prices and supplier-reported dates include quality warnings.

Are landing playground responses mocked?

Initial examples are illustrative. Running a preset sends an allowlisted request through a server-side SoldFetch key. Shared cache hits are returned first and do not trigger another upstream request.

How are playground requests protected?

Only cache misses can reach the backend. The server validates every preset and applies daily limits to both the trusted client IP and a persistent browser visitor ID.

Can agents use the same API?

Yes. REST, MCP, and the installable ebay-data Skill resolve through the same operations, authorization rules, and normalized domain model.

Is SoldFetch affiliated with eBay?

No. eBay is a trademark of eBay Inc. SoldFetch is an independent data service and keeps that boundary explicit.