eBay API Price per Record in 2026: Search Pages Are Not Listings
An eBay API price per record cannot be read from a search price alone. A search-priced service charges for one page request; a record-priced service charges for each delivered product. I normalized current published rates, then built an explicit listing-yield model so you can plug in your own measured output. The calculations below are original arithmetic from provider rate cards checked October 6, 2026, not a performance test.
We sell a separate eBay API, but this independent pricing table compares the other named products. They were researched from their own sites, not tested with live calls. No row implies a measured response time, success rate or data quality.
Short answer: compare cost per useful unique listing with the fields you need. AnyAPI advertises eBay search and basic item requests from $0.50 per 1,000, but search is capped at 25 requested rows and required fields can raise its quote; full item starts at $1.80 per 1,000. SearchApi Developer is $4 and SerpApi Starter $25 per 1,000 searches at full plan use. Bright Data quotes $1.50 per 1,000 delivered records. These are different denominators. Without actual listings per billed search, no fair cross-unit cheapest ranking exists.
Method: normalize eBay API price per record honestly
I transcribed prices from the vendors’ own live pages, selected their entry or clearly named plan, and divided monthly price by included units only where the plan gives an exact count. I kept a separate column for the unit the vendor bills. Every search-plan “per 1,000” figure assumes the entire monthly allowance is used. An underused plan costs more per actual search.
I included AnyAPI, SerpApi, SearchApi, Bright Data and one specific Apify community Actor in the arithmetic because their public pages state usable numbers. I discuss Oxylabs separately: its table has target-dependent rates, and the eBay mapping must be confirmed before quoting a final eBay unit cost. The provider buyer’s guide compares field surfaces and production access. No one in this study was benchmarked.
The published eBay API price table, with its real unit
| Product and plan | Published allowance or event | Calculated or quoted rate | Billed unit | Minimum / qualifier |
|---|---|---|---|---|
| SerpApi Starter | $25/month; 1,000 searches | $25.00 / 1,000 | Search | $25 monthly; full use assumed |
| SerpApi Developer | $75/month; 5,000 searches | $15.00 / 1,000 | Search | $75 monthly; full use assumed |
| SerpApi Production | $150/month; 15,000 searches | $10.00 / 1,000 | Search | $150 monthly; full use assumed |
| SearchApi Developer | $40/month; 10,000 searches | $4.00 / 1,000 | Search | $40 monthly; full use assumed |
| SearchApi Production | $100/month; 35,000 searches | $2.86 / 1,000 | Search | Vendor rounds headline to $3 |
| AnyAPI eBay Search | From $0.50 / 1,000 requests | From $0.50 / 1,000 | Search request | Up to 25 requested rows; required fields can raise quote |
| AnyAPI basic item | $0.50 / 1,000 requests | $0.50 / 1,000 | One item request | Offer fields; no seller description or full specifics promised |
| AnyAPI full item | $1.80 / 1,000 requests | $1.80 / 1,000 | One item request | Description and item-specifics table documented |
| Bright Data PAYG | $1.50 / 1,000 records | $1.50 / 1,000 | Delivered record | 5,000 free records/month advertised |
| Bright Data Scale | $499/month; 384,000 records | $1.30 / 1,000 | Delivered record | $499 monthly; full use assumed |
| Apify automation-lab Actor, free tier | $0.00345/product + $0.001/run start | $3.45 / 1,000 + starts | Product record | Specific community Actor, not all Apify |
Source pages: SerpApi eBay Search and pricing; SearchApi eBay Search and pricing; AnyAPI search, basic item and full item; Bright Data eBay product and pricing; the named Apify Actor. Read 2026-10-06. Provider rates can change.
Search-priced plans: commitments and row caps change the math
SerpApi: monthly search allowances
SerpApi’s Starter, Developer and Production plans list $25 for 1,000 searches, $75 for 5,000, and $150 for 15,000 per month. At full plan use, those work out to $25, $15 and $10 per 1,000 searches. These are whole-plan costs, not eBay-only surcharges.
SearchApi: monthly search allowances
SearchApi’s Developer plan is $40 for 10,000 searches, or $4 per 1,000. Its Production plan says $100 for 35,000 searches, which is $2.857 per 1,000 by division; the vendor’s displayed headline rounds that to $3. These are whole-plan costs, not eBay-only surcharges.
AnyAPI: search requests and a 25-row cap
AnyAPI eBay Search has no advertised monthly minimum and starts at $0.50 per 1,000 requests. One paid request asks for at most 25 listings, so even a perfectly full response cannot represent 50 or 100 unique listings in the same call. The page says requests that require certain seller or listing fields can carry a higher quote; its FAQ also says some failed funded requests incur processing charges. Its free response example is restricted to three rows; do not use that preview as the paid-page size. At the published starting rate, a hypothetical 25 useful rows every call would cost $0.50 / 25 = $0.02 per 1,000 useful rows. That is a theoretical ceiling-yield case, not a tested rate per delivered listing.
Worked example: buy SerpApi Starter at $25/month and use only 200 of the 1,000 included searches. Your realized spend is $25 / 200 × 1,000 = $125 per 1,000 actual searches. At all 1,000, it is $25. The same caveat applies to every monthly allowance.
One eBay search can show several listings, but your application may reject duplicates, sponsored items, missing prices, wrong countries or rows without an item ID. A requested SerpApi page size of 25, 50, 100 or 200 is not a delivered-row guarantee. Counting raw cards as usable records would overstate value. If you monitor prices across marketplaces, compare the item-matching method in our product-data API guide and ecommerce price-intelligence overview.
Record-priced products: one output row is the unit
Bright Data: delivered records
Bright Data’s eBay product page lists keyword and product scrapers and points to record-based pricing. Its pay-as-you-go card says $1.50 per 1,000 records; the $499 Scale plan includes 384,000 records, equivalent to $1.2995 per 1,000 at full use, aligning with its quoted $1.30 additional-record rate. It also lists 5,000 free records per month. Check the exact scraper’s output before treating every row as the item record your job needs.
Apify automation-lab Actor: products and run starts
The automation-lab eBay Actor quotes $0.00345 for each product on its free-plan tier plus a $0.001 Actor-start charge. That is 1,000 × $0.00345 + $0.001 = $3.451 for 1,000 products in one run. Split the same 1,000 products across 100 runs, and the event total becomes $3.45 + 100 × $0.001 = $3.55. These are calculations from its published event table, not measured invoices. Other Actors have other prices and may carry platform charges.
AnyAPI: basic and full item requests
AnyAPI’s basic product request is an item lookup, not an added search row, and the published base rate is $0.50 per 1,000 requests. Its full product request adds the seller’s description and item specifics at $1.80 per 1,000 requests. If a search really yields 25 useful unique items and you then make one basic lookup for each, the hypothetical total is $0.02 + $0.50 = $0.52 per 1,000 enriched items. Full lookups instead make it $0.02 + $1.80 = $1.82. Both calculations assume the $0.50 starting search quote applies and every item lookup returns the needed fields; neither is a measured bill.
Oxylabs: confirm the eBay target quote
Oxylabs’ rate card needs extra care. Its “from $0.50 per 1,000” entry price is for Amazon without JavaScript. The same page lists “Other” targets at $1.15 per 1,000 without JavaScript on Micro, and explains that 2xx and 4xx responses count as successful billing responses. Its e-commerce target catalog includes eBay search and product sources, but confirm the eBay target’s exact rate and parsed output in a quote. A charged 4xx is not a useful product record.
Convert a search price to a usable-listing scenario
This is a sensitivity table, not observed eBay output. Let R be your measured average number of useful unique listings per paid search after your field and country rules. Then cost per 1,000 useful listings = cost per 1,000 searches / R. The table below deliberately uses three assumed yields to show why a search can look cheap or expensive depending on the actual response.
| Search plan | 25 useful listings | 50 useful listings | 100 useful listings |
|---|---|---|---|
| AnyAPI starting quote: $0.50 / 1,000 requests | 0.02 | Not possible in one request (25 cap) | Not possible in one request (25 cap) |
| SerpApi Starter: $25 / 1,000 searches | 1.00 | 0.50 | 0.25 |
| SearchApi Developer: $4 / 1,000 searches | 0.16 | 0.08 | 0.04 |
The calculation shows a possible unit conversion, not a claim that any vendor returns those counts. AnyAPI’s 50- and 100-row cells are unavailable by its documented per-request cap; SerpApi permits a 100-result request and SearchApi permits 120 or 240 requested items, but useful output remains unmeasured. Extra item-detail calls raise cost. Seller feedback, description or shipping fields can also force a different endpoint or rate. Match the output contract before comparing. Our eBay provider buyer’s guide maps which products document search, item and seller surfaces.
Five checks before you budget an eBay data job
- Record the unit: search, HTTP response, delivered product row or Actor event. Never divide one provider’s page count by another’s row count.
- Use a representative sample: for each country and category, record billed calls, unique item IDs, nonempty required fields and duplicates. The price-alert guide shows why stable IDs matter.
- Include enrichment: if you need item descriptions, reviews or seller detail, add the extra calls or records to your model. Search-only rates are a lower bound for a richer workflow.
- Include the commitment: monthly minimums and unused allowance can dominate the rate for irregular jobs. Compare the published Serpent eBay pricing on the same unit and sample as every other row.
- Recheck the rate card: prices and product access change. Save a dated quote and ask the provider to confirm your exact eBay target and country before a large job. The API documentation should be checked at the same time as any rate.
FAQ
How do I calculate eBay API price per usable listing?
For a search-priced API, divide cost per 1,000 searches by measured useful unique listings per billed search. For a record-priced product, add run fees and any plan commitment to the per-record price. Use your own output count, not the requested page size.
Is AnyAPI eBay Search always $0.50 per 1,000 requests?
No. Its search page publishes $0.50 as the starting rate and says required output fields can raise the quoted price. One search can request at most 25 listings, and the full item endpoint has a separate $1.80-per-1,000-request rate.
Is Bright Data’s $1.50 per 1,000 cheaper than SerpApi’s $25 per 1,000?
Those numbers describe different units: Bright Data quotes delivered records while SerpApi quotes searches. You need actual useful listings per search, the same output fields and the plan commitment to compare total spend.
Does the cheapest headline rate apply to eBay?
Not automatically. Oxylabs’ $0.50-per-1,000 headline is for Amazon in the rate table. Apify has many independently priced eBay Actors. Check the exact eBay product and plan rather than using a platform-wide headline.
Were these prices measured from invoices?
No. They are provider-published prices checked October 6, 2026, with arithmetic shown. The listing-yield table is explicitly hypothetical. No competitor traffic or billing invoice was collected.
Use the provider buyer’s guide to choose a data surface, then inspect the Serpent eBay API page and documentation for the output contract you would need to test.
