Bulk data
Snapshots, recurring drops, and custom slices — outside the per-call ladder.
For buyers who need a Parquet file and an invoice, not a request counter. Three SKUs, three buyer modes, all delivered against the same 449k-restaurant / 44.3M+-item corpus.
Sample query before contract — always
One-time snapshot
$1k–$25k depending on scope. Parquet by default, CSV or JSON on request. Delivered within 5 business days. Methodology PDF + license terms included.
Recurring drops
$500–$10k/month. Weekly or monthly delivery via S3 bucket, SFTP, or secure email. Schema-versioned so your downstream pipeline doesn't break on schema evolution.
Custom slices
$500–$5k per delivery. You specify a filter (“all sushi restaurants in California with 50+ menu items, with chain-affiliation joined”), we deliver. Faster than building it yourself.
Pricing
Three sizes, all priced by scope and delivery cadence.
Snapshot $1k–$25k · Recurring $500–$10k/mo · Custom slice $500–$5k per delivery. Methodology PDF and license PDF included with every delivery.
Common questions
What's in a default snapshot?
Restaurants (id, name, address, geo, cuisines, chain affiliation), items (id, name, price, modifiers, source-tier provenance), and the chain entity layer joined in. Methodology PDF describes the schema in full.
How fresh is the data in a snapshot?
Refreshed daily upstream; the snapshot reflects the most recent crawl as of the delivery date.
Do you handle PII?
No. Restaurant menus and storefronts are public commercial data. We don't collect or distribute consumer PII.
Can the schema change?
Schemas are versioned. Recurring-drop customers get 30 days' notice on any breaking change.
Get a quote