Local models
Lot manifests
Turn a seller's photos and listing into an itemised manifest that a buyer can price, with every gap listed for the seller to fill.
Why a manifest
Buyers of liquidation and IT lots pay less for a lot without an itemised list, and many sellers post photos and a paragraph instead. bonfyre manifest reads what the seller already gave and writes the manifest, leaving blank anything the seller did not state.
Start the local model
The three commands on these pages ask a model that runs on your own computer. Start it once and leave it running; it loads a model only when a question arrives, and only if there is memory for it.
bonfyre-moe serve --port 7000
bonfyre model local
bonfyre model local lists the models in ~/BonfyreModels, how much memory each needs and which one would answer now. Left to itself, the server loads the largest model that fits. To ask for a particular one, add --model with its file name or part of it, such as --model qwen2.5-3b-instruct. While a command runs it holds the model, so the server does not swap or unload it partway through. The hold ends when the command finishes, or ten minutes after a command stops without saying so. A command that settles every line without the model never loads one. Every answer records the exact model file that gave it.
Read a lot
bonfyre manifest --lot houston-35 \
--photo houston-35-1.jpg --photo houston-35-2.jpg \
--listing listing.html --out houston-35.tsv --itad houston-35-itad.tsv
Every photo is read on this computer. Photos named alike, such as houston-35-1.jpg and houston-35-2.jpg, are read together. The brand, the model family, part numbers, the count and the listing's own condition and make fields are copied exactly as written. The local model then says what kind of equipment each unit is, whether it holds data that must be wiped before resale, and what the text says about its condition.
What is decided by the text alone
Some answers come from the words themselves and the model is not asked:
| The text says | The manifest records |
|---|---|
| Toner, ink, drum units, cable managers or rack kits, with no equipment named beside them | A consumable that holds no data |
| A desktop, laptop, server or phone | Data to wipe, unless the text says it has no drive |
| No condition words at all | Condition unknown |
| Only a brand name | No kind, and a note asking the seller what the items are |
| Nothing readable | A note asking for the listing or a photo of the label |
A 42U rack listed with servers and drives is not a consumable, so the model is asked about it. A model number is never read as a count: "OptiPlex 7050 desktops" states no count.
--itad writes the three columns the ITAD Exchange desk imports: model, quantity and grade. The desk prices by quantity, so a unit whose count the seller did not state, or that could not be read, is left out of that file. It is listed with the reason in a second file whose name ends in .held.tsv.
What it read from real lots
On seven lots from the October 2026 wholesale pipeline (marketplace photos and two saved listings) it read an HP EliteDesk desktop from a label cut off at ELITEDES, a Vertiv vertical cable manager by part number VRA1016, a 121-unit Lexmark, Epson and Fujifilm ink and toner lot with condition new, and a computer store's mixed stock of Dell, HP and Apple machines. One photo had no readable text and one showed only the word Canon; both were returned to the seller to confirm. A photo of Dell toner boxes was wrongly read as a desktop.
Only the toner lot states its count, so the ITAD file now holds that one lot and the held file lists the other six. The first version wrote five of them into the ITAD file as one unit each. The kinds of equipment above were read by that first version and have not been read again.
Limits
Marketplace photos are small and rarely show a label, so most lots need the listing text or close photos of labels. A manifest says what the seller showed and wrote. It does not count, test or take ownership of anything.