EDGE Pipeline Scraper

Title card for the AutoSmartCode EDGE Pipeline scraper — automated EDGE Pipeline data extraction

The independent auctions you actually buy at, read together, in one list, ranked by margin.

What EDGE Pipeline is, and why the data matters

EDGE Pipeline is the platform a large share of North America's independent auto auctions run their pre-sale listings and simulcast bidding on. Each auction keeps its own identity, its own sale calendar and its own consignors, but the underlying run lists, condition notes and lane data are published through a common system — which is why one build can cover a dozen independent houses that would otherwise each need their own.

Not every dealer buys at Manheim. Plenty of the best margin sits at regional independents, where the competition is thinner and the cars are local. The catch is that following six independent auctions means six logins, six sale calendars and six run lists in six different formats every week. Reading them through one pipeline collapses that into a single ranked list, and makes the small auction as easy to work as the national one.

What the EDGE Pipeline scraper extracts

Getting past EDGE Pipeline's defences

Each auction house configures its own EDGE instance, so field names, optional columns and sale-calendar structure vary between houses even though the platform is shared. Sessions are authenticated per auction and expire quickly. The build handles one session per auction account you hold, maps each house's local field naming into a single normalised schema, and reconciles the same VIN appearing at two houses so a car is not counted twice in your shortlist.

What people do with it

How you receive the data

Excel, CSV, JSON, a Google Sheet that refreshes on a schedule, a direct write into MySQL or Postgres, or a REST endpoint your own tools can query.

Frequently asked questions

Does this work for my local auction specifically?

If your auction publishes run lists through EDGE Pipeline or Simulcast, yes. If it runs its own in-house site instead, it is still almost always doable — the pattern is identical, only the login and page structure change. Send me the auction and I will tell you straight away.

Can it cover several auction houses at once?

That is the usual reason people ask. One build, one session per auction account you hold, and one normalised output where the auction house is just a column. Same VIN appearing at two houses gets reconciled rather than duplicated.

Do I need an account at each auction?

Yes. The automation drives licensed sessions you already hold at each house — it does not create access you do not have, and I do not share credentials between clients.

Can it score independent auction lots against MMR?

Yes, and it is the point of the exercise. Regional run lists joined against Manheim MMR on VIN gives you the spread per lot directly, which is what tells you whether the drive to a smaller sale is worth making.

What does this cost?

One auction house with run-list extraction and scoring typically runs $600 to $1,200. Each additional house on the same platform is a fraction of that, because the parser is already built. Recurring systems are a build fee plus a small monthly amount for hosting and fixes.

Other sites I scrape