swiggy-search
Discovery is read-only and safe to call as often as needed. Pick the server from intent; never search all three "just in case" — each call spends the user's per-server rate budget (70/min).
Route by intent
| The user wants |
Command |
| restaurants that deliver (name or cuisine) |
swiggy food search -q "<one term>" |
| a specific dish across restaurants |
swiggy food search-menu -q "<dish>" (--veg for veg-only; there is no non-veg-only filter) |
| everything one restaurant sells |
swiggy food menu --restaurant-id <id> |
| groceries / household / FMCG |
swiggy instamart search -q "<product>" |
| "my usual" groceries |
swiggy instamart go-to-items — one call replaces 3–5 searches |
| a place to eat out / book a table |
swiggy dineout search -q "<one term>" --address-id <id> (or --lat --lng for a named city) |
Always append --json --no-interactive.
Rules
- Send one term, not the user's sentence. Swiggy's search resolves what the term means; "best rooftop places in Koramangala" becomes
-q rooftop plus the location. Sentences return noise.
- Food/Instamart need
--address-id (or a profile default). Results depend on serviceability at that address, so a search without it is meaningless upstream and the CLI refuses it in machine mode.
- Dineout needs a location:
--address-id from swiggy dineout locations for "near me/home/office"; --lat --lng for a named area (Bangalore 12.9716,77.5946 · Koramangala 12.9352,77.6245 · Mumbai 19.0760,72.8777 · Delhi 28.6139,77.2090). Do not guess coordinates for a city you do not know — ask.
- Map intent to a Food collection only when it is unambiguous: healthy/high-protein →
--collection EATRIGHT, "fastest possible" → BOLT, "under ₹100" → STORE_99. Otherwise omit.
- Paginate with the response's
nextOffset (--offset <n>); never invent offsets.
- Present, then stop. Show name, rating, id (Food/Dineout) or displayName, price,
spinId (Instamart variations). Do not auto-continue into cart or booking; those need the user's choice.
Reading results
- Food
search: data.restaurants[] → id, name, availabilityStatus. Only recommend OPEN restaurants.
- Food
search-menu: data.items[] → menu_item_id (needed for the cart), restaurant_id, price, hasVariants, hasAddons.
- Instamart
search: data.products[] → each has variations[] with spinId, skuId, price.offerPrice, isInStockAndAvailable. Carts take variation ids, never productId.
- Dineout
search: data.restaurants[] → id, name, cuisine, costForTwo, availableDeals; data.latitude/longitude are remembered by the CLI for the next details/slots/book.
Example
swiggy food search-menu -q "paneer tikka" --veg --json --no-interactive \
| jq '.data.items[:5] | map({name, price, id: .menu_item_id, restaurant: .restaurant_name})'
1---2name: swiggy-search3description: Find restaurants, dishes, grocery products or dine-in venues on Swiggy with swiggy-cli. Use when the user says "find", "search", "what's available", "show me options", "is X on Swiggy" — before any cart, order or booking step.4license: MIT5---67# swiggy-search89Discovery is read-only and safe to call as often as needed. Pick the server from intent; never search all three "just in case" — each call spends the user's per-server rate budget (70/min).1011## Route by intent1213| The user wants | Command |14| --- | --- |15| restaurants that deliver (name or cuisine) | `swiggy food search -q "<one term>"` |16| a specific dish across restaurants | `swiggy food search-menu -q "<dish>"` (`--veg` for veg-only; there is no non-veg-only filter) |17| everything one restaurant sells | `swiggy food menu --restaurant-id <id>` |18| groceries / household / FMCG | `swiggy instamart search -q "<product>"` |19| "my usual" groceries | `swiggy instamart go-to-items` — one call replaces 3–5 searches |20| a place to eat out / book a table | `swiggy dineout search -q "<one term>" --address-id <id>` (or `--lat --lng` for a named city) |2122Always append `--json --no-interactive`.2324## Rules25261. **Send one term, not the user's sentence.** Swiggy's search resolves what the term means; "best rooftop places in Koramangala" becomes `-q rooftop` plus the location. Sentences return noise.272. **Food/Instamart need `--address-id`** (or a profile default). Results depend on serviceability at that address, so a search without it is meaningless upstream and the CLI refuses it in machine mode.283. **Dineout needs a location:** `--address-id` from `swiggy dineout locations` for "near me/home/office"; `--lat --lng` for a named area (Bangalore 12.9716,77.5946 · Koramangala 12.9352,77.6245 · Mumbai 19.0760,72.8777 · Delhi 28.6139,77.2090). Do not guess coordinates for a city you do not know — ask.294. **Map intent to a Food collection only when it is unambiguous:** healthy/high-protein → `--collection EATRIGHT`, "fastest possible" → `BOLT`, "under ₹100" → `STORE_99`. Otherwise omit.305. **Paginate with the response's `nextOffset`** (`--offset <n>`); never invent offsets.316. **Present, then stop.** Show name, rating, id (Food/Dineout) or displayName, price, `spinId` (Instamart variations). Do not auto-continue into cart or booking; those need the user's choice.3233## Reading results3435- Food `search`: `data.restaurants[]` → `id`, `name`, `availabilityStatus`. Only recommend `OPEN` restaurants.36- Food `search-menu`: `data.items[]` → `menu_item_id` (needed for the cart), `restaurant_id`, `price`, `hasVariants`, `hasAddons`.37- Instamart `search`: `data.products[]` → each has `variations[]` with `spinId`, `skuId`, `price.offerPrice`, `isInStockAndAvailable`. Carts take variation ids, never `productId`.38- Dineout `search`: `data.restaurants[]` → `id`, `name`, `cuisine`, `costForTwo`, `availableDeals`; `data.latitude/longitude` are remembered by the CLI for the next `details`/`slots`/`book`.3940## Example4142```bash43swiggy food search-menu -q "paneer tikka" --veg --json --no-interactive \44 | jq '.data.items[:5] | map({name, price, id: .menu_item_id, restaurant: .restaurant_name})'45```
HKTITAN