Pricing
Everyone needs a different amount, so I put together a range of options.
We don't just sell data. We sell answers you can trust.
You, whenever a craving hits
No card, right now. Refills every midnight (KST).
You, if Yumi's your daily go-to
7× the free headroom — ask all day and still have room.
The indie dev shipping right now
Just right for your first hookup into a live service.
- Up to 1,000 results per search
- 10,000 distinct venues / 30 days
- Priority 30 rpm
A service with real traffic coming in
Everything in Starter + room as you grow.
- Up to 5,000 results per search
- 40,000 distinct venues / 30 days
- Priority 60 rpm
Teams at scale · companies that need the data
Whole regions or the dataset — sized to you.
- Unlimited extraction
- Bulk export · data license
- SLA · dedicated support
What do the three developer limits mean?
These three limits apply only to the developer (API) plans you build into a product. Separate from tokens (depth/usage), they set how wide, how fast, and across how many venues your live queries go — guardrails, not nickel-and-diming. (The personal Free/Plus plans have none of these; they run on a daily token budget only.)
Up to N per search · result window
How many results a single search can page through — Starter 1,000 · Pro 5,000. Pulling a whole region at once is Bulk Export territory.
N distinct venues / 30 days · extraction cap
How many distinct venues you actually touch over a rolling 30 days — Starter 10,000 · Pro 40,000. Serving the same popular spot to many users, again and again, still counts as one — so real recommendation apps rarely hit it; only harvesting the dataset wholesale does (then it's Bulk / a data license).
Priority N rpm · requests per minute
How many requests per minute you can send. Higher means your calls go through first — no waiting or 429s under load — Starter 30 · Pro 60.
How tokens are spent
Tiers aren't plans. They only set how many tokens a single call spends — and every plan can call every tier. Basic data spends 1, rich data spends 4, and owner-uploaded photos (images, the richest data) spend 8. page_size (how many you get per call) has no effect on cost.
| Tier | tokens / call | Fields included |
|---|---|---|
| core | 1 | id, name, category, location, address, regionCode, confidence, sourceCount, lastSeenAt |
| contact_hours | 2 | phone, homepage, bookingUrl, snsLinks, businessHours, is24h |
| quality | 2 | rating, reviewCount, latestReviewDate, freshnessScore, dataQuality, price, menuSummary, openNow, photoCount, nearestStation |
| edge | 4 | accessHints, recommendedFor, atmosphere, cautions, menu, serviceAttributes, dietary, atmosphereScores, aiSummary, reputation |
| media | 8 | photos · video (owner-uploaded venue & menu photo & video URLs — video soon) |
Why the live limits — and why bulk is separate
The live API is for answering queries in the moment. So storing, copying, or redistributing responses in bulk is off-limits — the same as map APIs — to stop data we worked to verify from being resold as-is. When you need to load data into a product or own a dataset, we offer it properly through Bulk Export and a data license: rights already cleared, none of the terms-and-copyright risk that comes with scraping someone else's map. That legal path simply doesn't exist on map APIs.
Talk to us · Bulk & data licensing →