Omnigraph
Graph engine for context assembly. Object-storage native. Agents work with graph data the way engineers work with code: branched, typed, reviewed, merged, audited, and governed.
21,907 listings on the record; 61% have been up at least 90 days. An open, daily record of US businesses listed for sale on brokers' own websites. Free, CC0.
DataGitHub @jeffsosvilleOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Repository information has not been collected yet.
No updates detected yet. GitHub releases will appear here.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗An open, verifiable record of businesses for sale.
There is no MLS for business sales. No standards. No audit trail. No accountability.
Brokers can list fake businesses. Marketplaces can inflate their counts. Listings can disappear and reappear with no record. Prices change with no history. No one knows what's real.
This is the Market for Lemons. When buyers can't distinguish honest sellers from dishonest ones, trust collapses.
DealLedger is a public deed registry for private market activity — a memory layer for markets that are designed to forget.
Every listing is:
If a listing can't be traced to a verifiable source, it doesn't exist in the ledger.
Broker-direct only. DealLedger reads brokers' own websites and does not ingest marketplace aggregators.
broker_sources
(Supabase), moving through 1_needs_discovery → 3_crawlable → 4_producing.agents/discover_backlog.py, daily) finds each broker's
listings page and marks the verified ones crawlable.scrapers/dealledger_scraper_v6.py, 4 parallel shards,
400 brokers/day) reads crawlable and producing brokers, stalest first.scrapers/run_specialized.py) cover the large
franchise networks and WordPress-REST sites daily.listings_direct with first-seen/last-seen dates, are
filtered for junk, and are bridged to the public site. A daily snapshot is
committed to data/snapshots/<date>/.Schedules live in .github/workflows/. How we crawl, and how a broker can opt out, is in SCRAPING_POLICY.md.
git clone https://github.com/jeffsosville/dealledger
cd dealledger
pip install -r requirements.txt
# Test the generic crawler on ONE broker (never writes to production
# unless you pass --write)
python3 scrapers/dealledger_scraper_v6.py --broker https://example-broker.com/listings
# Run the specialized scrapers without writing
python3 scrapers/run_specialized.py --dry-run --brokers transworld
dealledger/
├── scrapers/
│ ├── dealledger_scraper_v6.py # generic broker crawler (nightly, sharded)
│ ├── run_specialized.py # franchise + WordPress-REST scrapers
│ ├── crawl_run_log.py # per-broker crawl_run logging
│ ├── first_seen_monitor.py # first_seen invariant check
│ ├── freshness_monitor.py # staleness alerts
│ └── brokers/ # per-broker scraper template
├── agents/
│ ├── discover_backlog.py # daily broker discovery
│ └── discovery_v2.py # listings-page finder
├── scripts/
│ ├── export_brokers_csv.py # broker list from broker_sources
│ └── merge_snapshot_shards.py # merge nightly shard snapshots
├── sql/ # applied database migrations
├── data/
│ ├── snapshots/ # daily snapshots (CC0)
│ └── wp_rest_brokers.csv # WordPress-REST broker registry
├── pages/ # dealledger.org (Next.js)
├── .github/workflows/ # scheduled jobs
└── docs/
We need help adding brokers. There are hundreds of business brokers with websites — each one is a potential data source.
To add a broker:
scrapers/brokers/_template.py and submit a PRSee CONTRIBUTING.md for full details.
Full dataset (CSV + JSON, CC0), rebuilt daily: every active, published broker-direct listing.
data/public/DATA_DICTIONARY.mdRaw per-crawl snapshots are in data/snapshots/<date>/; they
cover only the generic crawler and include rows that never get published.
REST (read-only) — see METHODOLOGY.md.
You may use, fork, and build upon this work. No attribution required for data.
"We don't take sides. We publish what we observe."