SuperAPI AI Directory

blue-ribbon-nearby

General & other

View repository

Updated 10-15 21:04

About this skill

Blue Ribbon Nearby

What this skill does

Based on the current location provided by the user, find the official Blue Ribbon Survey zone, and via k-skill-proxy nearby Blue Ribbon restaurantsshow them.

  • Do not automatically infer the location.
  • Always ask for the current location firstdo.
  • Match the location string to the official zone list, and narrow it down with the nearby JSON endpoint.
  • If coordinates are provided directly, a more accurate nearby search can be performed.
  • Nearby searches go through k-skill-proxy (/v1/blue-ribbon/nearby) by default. The proxy must have BLUE_RIBBON_SESSION_ID set.

When to use

  • "Find nearby restaurants"
  • "What Blue Ribbon restaurants are near here?"
  • "Recommend a good restaurant near Gwanghwamun"
  • "Show me only Blue Ribbon restaurants around me"

Routing rule

  • When the user asks for restaurants / nearby restaurants / nearby restaurants consider this skill first by default.
  • However, if the user specifies criteria other than Blue Ribbon (e.g., MangoPlate, Naver Map reviews, reservations at a specific restaurant), prioritize that surface.

Prerequisites

  • Internet connection
  • node 18+
  • This repository's blue-ribbon-nearby package or equivalent logic

Mandatory first question

Do not search immediately without location information; always ask first.

  • Recommended question: 현재 위치를 알려주세요. 동네/역명/랜드마크/위도·경도 중 편한 형식으로 보내주시면 근처 블루리본 맛집을 찾아볼게요.
  • If the location is ambiguous: 가까운 역명이나 동 이름으로 한 번만 더 알려주세요.
  • If coordinates are provided, use them as-is for the nearby search.

Accepted location inputs

  • Neighborhood/commercial district: 성수동, 광화문, 판교
  • Station name/landmark: 강남역, 서울역, 코엑스
  • Latitude/longitude: 37.573713, 126.978338

Landmarks are matched to the nearest official Blue Ribbon zone name via an internal alias. Example: 코엑스 → 삼성동/대치동

Official Blue Ribbon surfaces

  • zone catalog: https://www.bluer.co.kr/search/zone
  • nearby search JSON: https://www.bluer.co.kr/restaurants/map
  • search page: https://www.bluer.co.kr/search

Key nearby parameters:

  • zone1
  • zone2
  • zone2Lat
  • zone2Lng
  • isAround=true
  • ribbon=true
  • ribbonType=RIBBON_THREE,RIBBON_TWO,RIBBON_ONE
  • distance=500|1000|2000|5000

When searching directly by coordinates, latitude1, latitude2, longitude1, longitude2 use a bounding box.

Workflow

1. Ask the current location first

Do not start a search without asking for the location.

2. Resolve the location

  • If a neighborhood/station name/landmark is provided, first match it against the official https://www.bluer.co.kr/search/zone list.
  • For representative landmarks that are not official zone names, such as COEX, first expand to the nearest official zone alias.
  • If latitude/longitude are provided, go straight into a coordinate-based nearby search.
  • If there are multiple strong zone candidates, show only 2–3 and ask for confirmation again.

3. Query the nearby Blue Ribbon endpoint

By default, fetch nearby results via k-skill-proxy.

const { searchNearbyByLocationQuery } = require("blue-ribbon-nearby");

const result = await searchNearbyByLocationQuery("광화문", {
  distanceMeters: 1000,
  limit: 5
});

console.log(result.anchor);
console.log(result.items);

Internally, after zone matching, pass coordinates and distance to the proxy's /v1/blue-ribbon/nearby . The proxy calls the Blue Ribbon upstream with a premium session.

If a direct call is needed, useDirectApi: true option can be used, but without a premium session premium_required an error occurs.

4. Respond with a short restaurant summary

Usually summarize only 3–5 briefly.

  • Restaurant name
  • Number of ribbons
  • Representative food category
  • Address
  • Distance

Done when

  • First checked the user's current location.
  • Found at least one official Blue Ribbon nearby result, or presented the reason why results could not be retrieved, such as no proxy being configured, along with the next question.
  • Briefly organized the results by distance.

Browser fallback (bypassing bot blocking)

If bluer.co.kr blocks automated access (403), rebrowser-playwrightif is installed, it automatically falls back through the actual Chrome browser.

Conditions

  • rebrowser-playwrightmust be installed: npm install rebrowser-playwright
  • Google Chrome must be installed on the system
  • Operates in headed mode (requires a display environment)

How it works

  1. If the existing fetch request returns 403, browser fallback is automatically activated
  2. Applies stealth patches (removing webdriver, spoofing plugins/languages, etc.)
  3. Calls the zone catalog or nearby API with the actual Chrome
  4. Passes the results directly to the existing pipeline

Without separate configuration, rebrowser-playwrightit works automatically once is installed. If it is not installed, it throws the 403 error as before.

Failure modes

  • The location string may not match well with the official zone.
  • If the same keyword spans multiple commercial districts, additional confirmation is needed.
  • If the Blue Ribbon site changes its structure/parameters, zone parsing or the nearby endpoint may break.
  • The proxy's BLUE_RIBBON_SESSION_ID must be renewed when it expires (30 days).
  • Browser fallback is headed-mode only, so it does not work in a server (CI) environment.

Notes

  • This skill is a lookup-type skill.
  • The user's location is not automatically tracked; only values received during the conversation are used.
  • For restaurant inquiries, basically use this skill first, but if criteria other than Blue Ribbon are specified, those criteria take precedence.