Question 1

Which site is actually cheapest for this hotel?

Accepted Answer

ask each site twice, or you compare a night against a stay before you compare any two hotel prices, work out the basis of each one by asking each site TWICE, once for one night and once for the full stay, and dividing each site's own two answers. a per-night quote returns the same number both times and a whole-stay quote doubles. do not compare the two sites to each other to find this: the price gap between them contaminates the ratio and hides it what gives it away: asked for one night and then for two, a whole-stay endpoint returned 478 and then 956, exactly 2.000, while a per-night one returned 534 both times, exactly 1.000; each site is compared only against itself, so no price gap can contaminate it why the cross-site ratio does not work: an earlier version of this page told readers to divide one site's number by the other's and look for the night count. On a second city those ratios came out at 1.79 and 1.40, because the sites also differ about 10% on price and the two effects multiply; an agent following that sentence concludes the bases match and ships the error what does not give it away: both payloads report the currency as USD, both report a length of stay of two, and both put the money in a field with the same name the description is wrong: the per-night endpoint's own summary calls that field the total price. It is not a total how wrong you get: it does not just inflate the gap, it inverts the ranking: on a second city one site looked 44% cheaper at face value and was actually 11.7% dearer once both were on the same basis, so the naive read recommends the wrong booking and within one record too: on one provider the final price is the whole stay while the fare beside it is per night, in the same object, so the basis can change between two fields rather than between two sites

Question 2

Which store is cheapest per unit?

Accepted Answer

price per unit, because the cheapest row is half the pack find <product> with litescrape google shopping on monid and open the product page endpoint. read pack size off the OFFER titles rather than the search results, and put any offer whose title carries no size into a third pile rather than dropping it: one merchant's title omits the size entirely, so a strict filter can throw away the cheapest matching pack. check that pile before you name a winner. most search titles carry no size at all, and filtering there throws away the right row and keeps the wrong battery the spread: $4.12 between the cheapest and the dearest shelf, which is 27.7%, on one identical pack in one country on one day what it cost: $0.0003 for fifteen merchant offers with direct store links, which is $0.00002 an offer per unit instead: $0.929 a cell at the bottom against $1.187 at the top, which is the number that actually decides the purchase the two that had no price: one big grocer's own page carried the product markup with its offers field set to null; one big hardware chain does not stock this size at all where not to filter: on the search list 12 of 20 titles carried no pack size at all, the correct top result among them, and one row that survived the filter was a different battery size entirely

Question 3

What does this product sell for on TikTok Shop?

Accepted Answer

what a product costs there against everywhere else get the tiktok shop products for category <id> with tikhub on monid several times, pool the results and de-duplicate, then sort by units sold yourself. there is no bestseller endpoint here and the feed is not just unordered, it is reshuffled per call: two identical requests came back with no products in common there is no ranking: nothing in this aisle returns a sales rank, and in our feed the top seller by units came back last on the page worse than unordered: three calls to the same category, two of them byte-identical requests, returned zero products in common; so pool several calls rather than paging one, because there is no stable sequence to page through two documented things that are not true: the list arrives under productList rather than the documented products, and a page is fifteen rows rather than the documented twenty, so the documented offset of twenty skips five rows every time what a month costs: $0.32 to refresh a whole category's prices and unit counts every day for thirty days, at seven calls a day listed stable, mostly not: the other provider's search endpoint answered 404 twice, and the category endpoint itself answered 400 on seven of eleven attempts while discover marked it stable; every one of those billed $0.0000

MrScraper

Try it with your agents

How-to guides

MrScraper

Try it with your agents

How-to guides

Related categories