ActorStack.dev

Invaluable auction results: what the data holds, and what the terms say

Prices realized, estimates and live bids from Invaluable, with the coverage measured on 2,040 lots — and the Terms of Use and robots.txt that prohibit automated access, stated plainly.

By Oswaldo Carabano9 min read

Short answer

Invaluable auction results can be exported as rows holding the price realized next to the low and high estimate, the house, category, date and currency of each lot. Measured on Apify on 1 October 2026 over 1,020 sold and 1,020 upcoming lots from 138 auction houses in 12 countries, price realized was filled on 100% of sold lots, the estimate on 91.7%, and the artist on 10.9% overall and 43.4% in Fine Art. The data comes from Invaluable's public search index without a login. Invaluable's Terms of Use, version 3.11, prohibit robots and any form of data extraction without written permission, and its robots.txt opens with the same prohibition — a fact to weigh before running any Invaluable scraper.

Key points

  • Price realized was filled on 100% of 1,020 sold Invaluable lots measured on 1 October 2026, and the estimate on 91.7% of the same sample.
  • Invaluable estimate coverage varied from 70.8% of the 1,000 most recent sold lots to 91.7% of a 16-keyword stratified sample of 1,020, so coverage follows the search.
  • Invaluable's Terms of Use, version 3.11, state that a user will not use any robot or spider to monitor or copy its pages without prior written permission.
  • The invaluable.com robots.txt sets `Crawl-delay: 10` for all agents and disallows `/search?keyword=`, under a header that prohibits automated access other than for search engines.
  • Invaluable sells subscription access to its database of past auction sale results, which is the same kind of data a scraper of sold lots produces.
On this page6 sections

Invaluable is one of the few public places where an auction's result sits next to the auctioneer's estimate, across thousands of houses. It is also a site whose terms prohibit automated access outright. Both facts belong on the same page.

Two datasets: sold and upcoming

searchMode: past returns sold lots with the price realized, newest first. upcoming returns lots open for bidding, with the current bid, bid count, bidders, watchers and favorites. A third and fourth row type, set with outputType, export the directory of about 6,900 auction houses and the artists Invaluable attributes lots to.

Both lot modes are read from Invaluable's search index, which answers without a login, 1,000 lots per request. On Apify, 1,000 lots took between 2.1 and 3.6 seconds. Searches larger than 20,000 lots are split by date, so maxItems — up to 100,000 — is the number of rows you actually receive.

input.json — sold Tiffany lamps, most relevant first
{
  "searchMode": "past",
  "keyword": "tiffany lamp",
  "sortBy": "relevance",
  "maxItems": 200
}

What is filled, measured

The sample: 16 keyword searches in each mode — painting, ring, chair, coin, vase, print, silver, sculpture, rug, clock, porcelain, bronze, book, watch, lamp, poster — giving 1,020 sold and 1,020 upcoming lots from 138 auction houses in 12 countries, run on Apify on 1 October 2026.

FieldSold (1,020)Upcoming (1,020)
Price realized100%—
Low / high estimate91.7%77.5% / 76.9%
Extra catalogue text44.4%63.8%
End time (timed sales)16.1%33.1%
Artist10.9%24.4%
Artist, Fine Art only43.4%66.4%
Reserve price—4.1%

Title, description, lot number, date, currency, house, category, location, country and image are on every row in both modes. Two conventions matter more than any rate: the currency belongs to the lot and is never converted, and a 0 in the source — Invaluable's way of storing “no estimate” or “no result” — is delivered as null. Why both matter for a comparables set is in asking price versus price realized.

Estimate coverage follows the search

The estimate was measured three times on sold lots and gave three answers: 91.7% on the 16-keyword sample of 1,020, 85.2% on 480 lots spread across 8 categories on 23 September, and 70.8% on the 1,000 most recent sold lots. Per category the spread is wider still — on the September sample, sold Firearms lots carried no estimate at all and sold Jewelry lots always did.

None of those numbers is wrong; each describes its sample. The consequence is practical: if your analysis depends on the estimate, measure its coverage on your own query before trusting it, which is the general rule set out in measured fill rates, not promises.

Lot pages: optional, slow and separately priced

scrapeDetails opens each lot's own page. Over 120 lot pages it added every photo (4.7 per lot against one from search), buyer's premium and its tiers, bid increments, payment and shipping terms, and the house's street address on essentially every page; a condition report on 50.0%, dimensions on 15.0%, medium on 8.3% and provenance on 3.3%.

Those pages sit behind a web application firewall, weigh about 71 times a search result and take about 1.5 seconds each through a residential proxy. Across 97 platform runs, 577 lot-page requests met one challenge — answered by changing IP, never by solving it — and no blocks. Hence off by default and a separate $0.003 event charged only when the page is read.

What Invaluable's terms and robots.txt say

Invaluable's Terms of Use, version 3.11, last revised effective 5 November 2019 and governed by Massachusetts law, say in §5.2 that a user will not “use any robot, spider, other automatic device, or manual process to monitor or copy our web pages or the content contained herein without our prior expressed written permission.” §4.2 limits the licence to “personal non-commercial use” and rules out “any form of data extraction or data-mining whatsoever.”

The robots.txt opens with a comment prohibiting automated access other than for search engines, then sets Crawl-delay: 10 for all agents and disallows paths including /login, /bidNow and /search?keyword=. The Actor's searches go to the index host rather than to that path; its optional lot pages are requested at about 1.5 seconds per page per session, which does not honour the 10-second delay. That is stated here rather than left to be discovered, and it is the opposite of robots.txt-compliant scraping.

Two more facts complete the picture. Invaluable's Subscription Agreement sells access to a database of past auction sale results. And when the developer checked on 1 October 2026, a sold lot page showed an anonymous visitor “Sold: Log in to view” in place of the price, while the same value was present in the search index and the page state served without a session. Anyone running the Actor should weigh those facts and make their own decision.

Bidders stay out of the data

Every seller on Invaluable is an auction house — 0 of 960 lots sampled had any other kind — so house names, addresses and logos are business data and ship. Bidders are people. The index carries the identifiers of watchers, bidders and winners and each bidder's maximum bid; the output carries watcher_count, bidder_count and a has_winner flag instead. Every row of 110 platform runs was checked by script, and no bidder identifier appeared in any of them. The full field list and prices are on the Invaluable Auctions Scraper page.

Frequently asked questions

Does Invaluable allow scraping?
Invaluable's Terms of Use prohibit robots, spiders and any form of data extraction without its prior written permission, and the robots.txt header repeats it. This describes the documents as read on 10 October 2026 and is not legal advice.
How many sold lots does Invaluable hold?
Invaluable's counters are approximate. Two queries on 23 September 2026 put sold lots with a price at 8.74 and 10.10 million, and the Actor's README gives about 9.6 million as of 1 October 2026.
Can I get the full description and every photo?
The description is in every search row. Every photo — 4.7 per lot on average over 120 lot pages, against one from search — needs the optional lot page, which costs a separate $0.003 event.

Sources

Every URL below was requested and returned a page on the date shown.

  1. Operator claimchecked 10 Oct 2026
    Invaluable Auctions Scraper — Actor README and input schemaActorStack / Apify Store
  2. Operator claimchecked 10 Oct 2026
    Invaluable Terms of Use, version 3.11Invaluable
  3. Site declarationchecked 10 Oct 2026
    invaluable.com/robots.txtInvaluable
  4. Operator claimchecked 10 Oct 2026
    Invaluable Subscription AgreementInvaluable
  5. Platform docschecked 18 Aug 2026
    Actor pricing modelsApify
A laptop screen showing a plain text-mode terminal with a command prompt.
DealsGuide

Asking price vs price realized

Two marketplaces, two kinds of price. Empire Flippers publishes what sellers asked, Invaluable publishes what auctions realized — and a comparables dataset that mixes the two up measures the wrong thing.

7 min
A laptop screen showing a plain text-mode terminal with a command prompt.
DealsGuide

Scrape Empire Flippers

The whole Empire Flippers catalogue — For Sale, Pending Sold and Sold — in fifteen requests, which filters actually narrow the result, and how much of each row is filled depending on its status.

8 min
A white shuttered window on a peach-coloured building with a for-sale notice beside it.
DomainsGuide

Bulk availability without WHOIS

Screening a naming shortlist against zone files instead of querying WHOIS per name: what it costs, what the verdicts mean, and where the method stops being enough.

7 min