Provider 디렉토리

Add a product_id to the connected shopper's amazon.co.jp cart with an optional quantity. Use only with explicit user intent to add the item. Returns the add action, whether the product is now in the cart, and the updated cart.

Retrieves real-time air quality measurements from an AirKorea monitoring station, including PM10, PM2.5, NO2, O3, SO2, CO, and the comprehensive KHAI index. Use when the user asks about current air quality, fine dust levels, or pollution at a specific Korean location. Do NOT use for weather forecasts — use kma:short-forecast instead. Returns pollutant values with grade levels (good/moderate/bad/very_bad).

Return valid party sizes and reservable dates for a restaurant.

Use this operation when a caller intentionally wants to cancel an existing Tabelog reservation, and when the provider must execute the live destructive cancellation flow with the authenticated reservation reference and capture proof of the resulting upstream state.

Cancel an authenticated Hot Pepper Gourmet reservation after explicit confirmation.

Lists all supported Korean delivery carriers with their IDs and names. Use when the user needs to know which carriers are available or wants to look up a carrier ID before tracking. Do NOT use for tracking a specific parcel — use delivery:status or delivery:track instead. Returns an array of carrier objects with carrier_id, name, and country code.

Checks public reservation dates or time slots for a restaurant on Catchtable. Use when the user wants to know when a restaurant has open reservations before booking. Do NOT use for making a reservation or inspecting reservation choices — use catchtable:reservation-options after confirming the desired date and time. Returns available date slots (if no date given) or time slots (if date specified) based on party size and table type.

Cancels an existing restaurant reservation on Catchtable by reservation reference ID with an optional reason. Use when the user wants to cancel a previously made reservation. Do NOT use for cancelling waitings — use catchtable:cancel-waiting instead. Returns the cancelled reservation reference, updated status, and cancellation timestamp. Requires Catchtable authentication.

Cancels an active waiting queue entry on Catchtable by waiting reference ID. Use when the user no longer wants to wait at a restaurant. Do NOT use for cancelling reservations — use catchtable:cancel-reservation instead. Returns the cancelled waiting reference and updated status. Requires Catchtable authentication.

Creates a dining reservation at a restaurant on Catchtable for a specified date, time, and party size. Use when the user wants to book a table after checking catchtable:availability and, when needed, catchtable:reservation-options. When required selections are returned, pass reservation_state plus selected_options from reservation-options. Returns a reservation reference ID, status, and confirmed visit details. Requires Catchtable authentication.

Retrieves the current user's saved (bookmarked) restaurants on Catchtable. Use when the user wants to see the shops they saved, or to obtain a shop_ref for follow-up calls such as catchtable:shop or catchtable:availability. Do NOT use for discovering new restaurants — use catchtable:search instead. Returns the list of bookmarked shops. Requires Catchtable authentication.

Retrieves the current user's active reservations and waiting queue entries on Catchtable. Use when the user wants to see all their upcoming reservations and active waitings in one view. Do NOT use for details of a single reservation — use catchtable:reservation-detail instead. Returns lists of reservations and active waitings with status. Requires Catchtable authentication.

Registers the user for CatchTable remote waiting at a restaurant using a waiting_choice from waiting-info and the desired party size. Do NOT infer remote registration availability from search.waiting_discovery_hint or an on-site queue alone; call catchtable:waiting-info first and proceed only when remote_waiting_available=true and is_open=true. Do NOT use for reservations; use catchtable:reserve instead. Returns a waiting reference ID, queue position, and status. Requires CatchTable authentication.

Retrieves detailed information about a specific reservation on Catchtable by reservation reference ID, including restaurant name, status, visit date/time, and party size. Use when the user wants to check the details of an existing reservation. Do NOT use for listing all reservations — use catchtable:my-status instead. Returns full reservation details. Requires Catchtable authentication.

Inspects authenticated CatchTable reservation requirements for a specific shop, date, time, party size, and table type. Use after catchtable:availability confirms the desired time is available and before catchtable:reserve when table, menu, payment, or app-only guidance may be needed. Returns reservation_state, required selections, payment support, and the next reservation action. Requires Catchtable authentication.

Searches for restaurants on Catchtable by keyword, optionally filtered by proximity to coordinates and sorted by recommendation or rating. Use when the user wants to find restaurants by name, cuisine type, or area. Do NOT use for getting details about a specific restaurant — use catchtable:shop instead. Returns a list of matching restaurants with name, cuisine, address, rating, and review count.

Retrieves detailed information about a specific restaurant on Catchtable by shop reference ID, including name, cuisine, address, phone, description, images, and ratings. Use when the user wants full details about a restaurant found via search. Do NOT use for reviews — use catchtable:reviews instead. Returns restaurant metadata with optional photo URLs.

Fetches paginated reviews for a specific restaurant on Catchtable by shop reference ID, including author, rating, content, and date. Use when the user wants to read reviews or check ratings for a restaurant. Do NOT use for restaurant details — use catchtable:shop instead. Returns a list of reviews with total count for pagination.

Retrieves the live detail of a single Catchtable waiting entry by waiting reference ID, including the realtime queue position, waiting number, status, table name, registration time, and check-in state. Use when the user wants to check how many teams are ahead for an active waiting. Do NOT use for listing all active waitings — use catchtable:my-status instead. waiting_order comes from the realtime delay lookup when it succeeds (waiting_order_source=realtime) and falls back to the order captured on the waiting record otherwise (waiting_order_source=registered). Requires Catchtable authentication.

Fetches order menus that CatchTable requires or offers during waiting registration. Connected calls include menu_choice tokens; anonymous calls return menu data only.

Fetches current waiting queue status and remote waiting registration availability for a CatchTable shop. Connected calls include waiting_choice and person-option choice tokens; anonymous calls return public status only.

Refresh every watched product and compare the new price with the saved snapshot and target_price. Use this on demand or on a schedule to detect price drops. Returns drops with old_price, new_price, drop_percent, and target_hit.

Empty the connected shopper's amazon.co.jp cart. Use only with explicit user intent to remove all cart items. Returns the clear action and the resulting cart.

Internal lifecycle operation that calls Weverse token validation for connected accounts.

Create or update a price watch for a product_id with an optional target_price. Use this to track a product over time. Returns the create action and stored watch entry with last_price, added_at, and last_checked_at.

Use this operation when a caller is ready to create a real Tabelog reservation from a selected plan and slot, and when the provider must drive the live booking flow, capture a proof snapshot, and return the reservation number for later cancellation or status lookup.

Create an authenticated Hot Pepper Gourmet reservation using choices returned by time-slots.

Use when a tenant already has a public Daangn cars listing URL and needs a best-effort normalized detail read without login or mutation. Detail URLs can disappear as listings close, so this operation returns only evidence available from the submitted URL.

Search read-only Daangn cars listings with a region_id from search-regions and an optional keyword. Call search-regions first and pass items[].id as region_id; free-text region names are not accepted.

Use when a tenant already has a public Daangn jobs listing URL and needs a best-effort normalized detail read without login or mutation. Detail URLs can disappear as listings close, so this operation returns only evidence available from the submitted URL.

Search read-only Daangn jobs listings with a region_id from search-regions and an optional keyword. Call search-regions first and pass items[].id as region_id; free-text region names are not accepted.

Use when a tenant already has an APIFuse opaque Daangn realty complex id and needs the public rich complex detail payload. It exposes buildings, schools, images, lived-review summary/tag counts/reviews, area groups, live article counts, and base complex fields without login.

Use when a tenant has an APIFuse opaque Daangn complex id and needs current article/listing cards attached to that complex. Amount fields from article trades are normalized in 만원 units and area fields are exclusive/supply area strings from Daangn.

Read Daangn realty complex price history from an APIFuse opaque complex id returned by complex search.

Use when a tenant already has a public Daangn realty listing URL and needs a best-effort normalized detail read without login or mutation. Detail URLs can disappear as listings close, so this operation returns only evidence available from the submitted URL.

Use when a tenant needs Daangn realty complex discovery for a region id. It returns normalized complex ids, opaque complex ids for follow-up price history calls, building type labels, household counts, recent transaction counts, and representative addresses when exposed.

Search read-only Daangn realty articles with a region_id from search-regions. Call search-regions first and pass items[].id as region_id; free-text region names are not accepted.

Use when a tenant needs to discover Daangn realty region ids from Korean city, district, or dong text. This uses the current public realty searchRegion GraphQL queries and can expand district rows into legal-dong children.

Find Daangn administrative regions before any region-scoped listing search. Call this first, then pass the returned items[].id as region_id to listing and complex search operations.

Use when a tenant already has a public Daangn used-goods listing URL and needs a best-effort normalized detail read without login or mutation. Detail URLs can disappear as listings close, so this operation returns only evidence available from the submitted URL.

Search read-only Daangn used-goods listings with a region_id from search-regions and an optional keyword. Call search-regions first and pass items[].id as region_id; free-text region names are not accepted.

Use this operation when you need Daiso catalog, category, or brand surfaces from the renewed HAR and want related read-only endpoints grouped into one response with per-endpoint summaries and optional sanitized source payloads.

Use this operation when you need Daiso recommendation surfaces around a product detail or search context, including detail-with, good-review-product, BLUX, and together endpoints grouped into one metadata-rich response.

Use this operation when you need Daiso search trend terms or recommended keyword surfaces for a query and want the observed trendSearch and selRcmKeywd endpoints grouped with partial-failure metadata.

Use this operation when you need Daiso site metadata such as common codes, delivery parameters, placeholders, holiday delivery information, or store search keywords from the renewed HAR endpoints.

Use this operation when you need a caller-friendly availability view for one Daiso product_id/store_code pair that combines renewed pickup stock and in-store location endpoints while preserving partial failures in meta.

Fetches Daiso product details, descriptions, notice information, images, and option review counts by product ID.

Use this operation when you need grouped Daiso product reviews by product ID, faning out to HAR-observed review list/content/attribute and AI summary/recommendation/keyword endpoints while surfacing optional failures in meta.

Use this operation when you need renewed Daiso Mall product discovery by keyword through the HAR-observed FindStoreGoods endpoint. It returns product name, price, ID, image, availability flags, metadata, and optional sanitized source payloads.

Use this operation when you already have a Daiso store_code and need the renewed store-detail payload, pickup date window, holiday signal, and source-aware metadata from the HAR-observed /dl/dla-api/selStrInfo endpoint.

Searches for Daiso store locations by keyword, province, district, or neighborhood in South Korea. Use when the user wants to find nearby Daiso stores or locate a specific branch by name or area. Do NOT use for product search or inventory — use daiso:search-products or daiso:inventory instead. Returns store name, address, phone number, and coordinates for each matching location.

Checks real-time inventory availability for a specific Daiso product at nearby stores, using coordinates for proximity ranking. Use when the user wants to know if a product is in stock at a particular Daiso branch or nearby stores. Do NOT use for product search — use daiso:search-products first to get the product_id. Returns a list of stores with stock status and quantity.

Use this operation when you need Daiso stores from the renewed fapi /ms/msg/selStr endpoint and want store_code, pickup flags, distance, hours, facility fields, and source-aware metadata instead of the legacy HTML-backed daiso:stores path.

Use when a tenant wants a compact Danawa price comparison from a keyword in one read-only call. It searches public product candidates, enriches top products with mall offer rows, preserves payment-condition signals, and returns source URLs for diagnosing upstream changes.

Use when a tenant already has a Danawa pcode and needs read-only mall offer rows from the public price-comparison AJAX surface. It extracts seller names, base price, shipping, total price, card price, conditional payment labels, and source evidence without logging in.

Use when a tenant needs read-only Danawa product candidates from public search results for a Korean keyword. It parses visible HTML, extracts product code, title, representative price, image, and product URL when available, and returns the upstream source URL for audit.

Delete a price watch for one product_id. Use this to stop tracking a product. Returns the delete action, removed flag, and product_id.

Retrieves the full delivery tracking history for a parcel identified by carrier ID and tracking number, including all transit events. Use when the user wants to see every step of the delivery journey from pickup to delivery. Do NOT use for a quick status check — use delivery:status instead. Returns carrier info, current status, and a chronological list of events with timestamps, locations, and descriptions.

Fetch genre lists and recommended conditions for a block code.

Get the connected Weverse account information.

Read the connected shopper's amazon.co.jp cart contents and subtotal. Use this before checkout or before cart changes. Returns cart items, subtotal, and item_count. Requires a signed-in cookie session.

Read one amazon.co.jp order by order_id from the connected shopper's history. Use this after list_orders when the user wants one order's details. Returns order_id, placed_at, total, ship_to, delivery, return_eligible, and items.

Read one amazon.co.jp product page by product_id, the public Amazon product identifier value. Use this when the product is already known. Returns normalized product detail including title, url, image_url, price, brand, availability, points, delivery, and features.

Get Weverse web app state.

Search directly usable Rakuten Travel leaf area tokens for hotel-search selectors.

Get artist highlight data for a community.

Use this operation when a caller needs the latest state of an existing Tabelog reservation, and when the provider must read the authenticated reservation detail flow to normalize whether the booking is still confirmed, already cancelled, or otherwise ambiguous upstream.

Use this when list-items or search-items returned an item_id and the user needs richer product details such as images, description, materials, colors, view count, or favorite count.

Get a Weverse comment by comment ID.

Get a Weverse community profile by community ID.

Get tab content for a Weverse community.

Get the connected Weverse user profile.

Get the connected user's Weverse DM profile.

Fetch details for a Rakuten Travel hotel and return normalized access, parking, telephone, review, and location fields.

Retrieve Rakuten Travel hotel rankings and return normalized ranked hotel rows.

Retrieve Rakuten Ichiba item rankings and return normalized ranked item rows.

Get the connected user's Jelly balance.

Fetch a legal resource detail returned by search.

Get live tab content for a community.

Get a Weverse member profile.

Get membership benefits for a community.

Get the connected account's membership profile for a community.

Get a Weverse post by post ID.

Get multiple Weverse posts by ID.

Use this operation when a caller needs a read-only view of a specific Tabelog restaurant page, and when downstream reservation logic depends on normalized booking-calendar endpoints, CSRF state, restaurant identity, or any booking launch links exposed by the detail page.

Get the unseen notification count.

Get the connected user's Weverse settings.

Use this when a user asks for the current Han River water level or flow by bridge, station name, or HRFCO station code. It resolves the public station metadata, fetches the latest 10-minute water-level observation, and returns thresholds for flood context.

Use this operation when a caller needs to inspect a booking-entry URL before creating a reservation, and when the provider must distinguish between an open entry form, a login gate, or a rate-limited anti-bot state without mutating a live reservation.

Fetch item detail and option groups for a shop/menu/item combination.

Use this when a user wants current or historical K-Startup support announcements by keyword, region, field, target, startup age, date range, or recruitment status. It calls the official announcement-information endpoint and returns normalized public announcement records.

Use this when a user asks for K-Startup business program information rather than a specific recruitment announcement. It searches the official business-information endpoint by business year, category code, or support business title.

Converts Korean road-name and land-lot addresses into latitude/longitude coordinates. For place or landmark names, use kakaomap:search and read the matching place lat/lng.

Calculates bicycle directions between two coordinate points via KakaoMap, returning distance and estimated cycling time. Use when the user asks how to cycle between two locations or wants bike route distance and time. Do NOT use for driving, walking, or transit routes — use the corresponding kakaomap direction operations. Returns distance in meters and duration in seconds. Coordinates can be obtained via kakaomap:geocode.

Calculates car driving directions between two coordinate points via KakaoMap, returning distance, estimated duration, and fare. Use when the user asks how to drive between two locations or wants driving time and distance. Do NOT use for walking, cycling, or transit — use the corresponding kakaomap direction operations. Returns distance in meters, duration in seconds, and optional taxi/toll fare in KRW. Coordinates can be obtained via kakaomap:geocode.

Retrieves detailed information for a single place on KakaoMap by its confirm_id, including name, address, coordinates, menus, reviews, and photos. Use when the user wants full details about a specific restaurant, cafe, or shop found via search. Do NOT use for searching places by keyword — use kakaomap:search instead. Returns place metadata, menu list, review counts, and user-generated tags.

Fetches user reviews and blog reviews for a specific KakaoMap place identified by confirm_id. Use when the user wants to read reviews, ratings, or opinions about a restaurant or shop. Do NOT use for place details like menus or hours — use kakaomap:place instead. Returns a list of reviews with author, rating, content, date, and total count.

Searches for places on KakaoMap by keyword, optionally filtered by proximity to given coordinates. Use when the user asks to find restaurants, cafes, shops, or any POI near a location or by name. Do NOT use for getting detailed info about a known place — use kakaomap:place instead. Returns a list of matching places with name, address, coordinates, and confirm_id for further lookup.

Calculates public transit directions between two coordinate points via KakaoMap, returning multiple itinerary options with duration breakdown. Use when the user asks how to get somewhere by bus or subway, or wants transit travel time. Do NOT use for driving, walking, or cycling — use the corresponding kakaomap direction operations. Returns itineraries with total duration, walk time, and transit time in seconds. Coordinates can be obtained via kakaomap:geocode.

Retrieves real-time information about a specific bus stop, bus line, or subway station from KakaoMap. Use when the user asks about bus arrival times at a stop, a bus line route, or subway station details. Do NOT use for route planning between two points — use kakaomap:transit-directions instead. Returns a structured transit branch whose fields vary by info_type (bus_stop, bus_line, or subway).

Calculates walking directions between two coordinate points via KakaoMap, returning distance and estimated walking time. Use when the user asks how to walk between two nearby locations or wants walking distance and time. Do NOT use for driving, cycling, or transit routes — use the corresponding kakaomap direction operations. Returns distance in meters and duration in seconds. Coordinates can be obtained via kakaomap:geocode.

Retrieves KMA current observation and short-term forecast for a Korean address or place name. The operation geocodes the address, converts WGS84 coordinates to KMA grid coordinates, and then calls the same KMA forecast APIs used by short-forecast. Use when callers have an address/place instead of KMA nx/ny grid coordinates.

Computes lifestyle weather indexes for a Korean KMA grid or address using KMA ultra-short current observations. Returns the observation inputs plus apparent temperature, laundry drying grade, and an estimated UV index/grade derived from time, season, and precipitation state.

Normalizes KMA mid-term temperature forecast responses into a day-by-day forecast array.

Retrieves KMA current observation and short-term village forecast for a grid coordinate in South Korea, including tomorrow forecasts when available. Use when the user asks about current weather, today, tomorrow, or hourly weather at a Korean location. Do NOT use for forecasts beyond 2 days — use kma:mid-forecast instead. Returns current observation plus forecast entries in KST timezone; null values indicate data unavailable. Grid coordinates can be obtained via kakaomap:geocode.

Retrieves active KMA weather-alert announcements from the national warning feed. Use for Korean weather warnings, advisories, cancellations, and alert status. Returns normalized alert level/status fields and preserves upstream KMA codes only under documented upstream_codes fields.

Use this when a user asks when, where, or how to dispose of household waste, food waste, or recyclables for a Korean district. It queries official municipal guidance by 시군구명 and returns the upstream guidance rows for local summarization.

Reports the official data.go.kr file dataset that backs the household waste guide while the paired data.go.kr open API endpoint is unavailable.

Use this when a user needs official MFDS e약은요 information for a named medicine. It searches by the APIFuse-standard query field and returns normalized medicine safety fields such as efficacy, usage, warnings, cautions, interactions, side effects, storage, and drug_id.

Use this when a user asks whether a food product or company appears in official MFDS improper-food disclosures. It searches product name, company name, category, and violation reason when checking recall or korea-mfds-food-safety concerns.

Use this when a user wants a school meal menu for a known NEIS school code and date. It calls the official mealServiceDietInfo endpoint and returns breakfast, lunch, or dinner rows for summarizing menu, calories, and nutrition fields.

Use this when a user names a school but does not yet have the NEIS SD_SCHUL_CODE. It searches official NEIS schoolInfo by education-office code and school name, then returns upstream rows that can be used when calling the menu operation.

Retrieves the current delivery status and the most recent tracking event for a parcel identified by carrier ID and tracking number. Use when the user wants a quick status check on a package without the full history. Do NOT use for full event history — use delivery:track instead. Returns carrier info, current status code/text, and the latest event with time, location, and description.

List available Korean legal sources and search presets.

Use this when a user selected an LH notice from the list operation and needs the official detail rows. It requires the detail_reference returned by the list operation and returns the requested notice plus supply-specific upstream rows.

Use this when a user wants official LH 청약 공고 lists for rental housing, 분양주택, 주거복지, 토지, or 상가. It searches by status, region, notice keyword, semantic housing type, and LH subcategory code, and returns a detail_reference for the detail operation.

List recent amazon.co.jp orders for the connected shopper. Use this to show order history or select an order_id for get_order. Returns normalized order summaries with snake_case fields.

List saved payment methods for the connected shopper's amazon.co.jp account. Use this to show available payment choices before checkout. Returns display names and descriptions only; full card numbers are never exposed.

List price watches stored for the connected shopper. Use this to show tracked products and their latest saved snapshots. Returns watch entries with product_id and snake_case price-watch fields.

List media posts in a media category.

Use this when a user wants to browse current Charan secondhand fashion listings by page, category, or brand.

List artist replies under a comment.

List replies under a comment.

List all media posts for a community.

List Weverse DM subscription state.

List fan letter posts for a community.

List feed tab posts for a community.

List Weverse communities grouped for discovery.

List Weverse community discovery groups.

List Rakuten Travel hotel chain codes and names.

List live posts for a community.

List media categories for a community.

List media posts related to a media post.

List comments written by a member.

List posts written by a member.

List artist comments on a post.

List comments on a post.

List showcased Weverse DM rooms.

Find a current Korean law by name and optionally return one article.

Use when a tenant needs the current Market Kurly public result count for a keyword before deciding whether to fetch product rows. It calls the lightweight count endpoint, does not require a user session, and returns a stable numeric count plus the upstream source URL.

Use when a tenant already has a Market Kurly product identifier and needs best-effort public detail-page data without login. It reads SSR page data, normalizes the first matching product row, and reports the source URL so callers can diagnose upstream schema changes.

Use when a tenant needs a read-only Market Kurly keyword search from public web/API surfaces without a user login. It returns normalized product identifiers, names, prices, discount signals, sold-out state, delivery labels, and product URLs while preserving the upstream source URL for audit.

Browse local Hot Pepper Gourmet master data such as areas, genres, features, seat types, smoking filters, and budgets.

Use this operation after a user chooses one Yogiyo menu item and needs its option section ids, option ids, and required/optional option counts for order-preview.

Use this when a user wants public Naver Blog search results for a topic, place, product, or research keyword. It calls the official Naver Search blog API, strips highlight HTML from title and description fields, decodes common HTML entities, and returns blogger metadata plus post dates.

Searches Naver Flight international one-way direct airfare for one adult economy passenger by departure airport, arrival airport, outbound date, and optional airline filters. Use when the user wants Korean-market one-way airfare comparison with exact fare rows from Naver. Do NOT use for round-trip planning that needs a return leg, booking, payment, passenger data collection, domestic-only guarantees, or historical prices. Returns ranked normalized one-way itinerary combinations with outbound segment, general fare, card fare, promotion fare, baggage type, taxes, and curation tags.

Searches Naver Flight international round-trip direct airfare for one adult economy passenger by departure airport, arrival airport, outbound date, return date, and optional airline filters. Use when the user wants Korean-market round-trip airfare comparison with exact fare rows from Naver. Do NOT use for booking, payment, passenger data collection, domestic-only guarantees, or historical prices. Returns ranked normalized itinerary combinations with outbound and inbound segments, general fare, card fare, promotion fare, baggage type, taxes, and curation tags.

Use when you need to convert a Korean place name, landmark, or station phrase into coordinates using the public place search surface. Backed by PlaceList keyword search with Seoul-area proximity bias, so it works best for recognizable names (강남역, 경복궁) and may not surface strict cadastral addresses. Returns the best match (prefers candidates whose roadAddress/address/name contains the query) plus alternates so clients can display ambiguity.

Use when you need bicycle-friendly routing between two coordinates, optionally through waypoints, using Naver bicycle routing. Do NOT use for cars, scooters, pedestrian routing, or official cycling safety guarantees. Returns route candidates with distance, duration, path geometry, legs, and guide text suitable for previewing a route.

Use when you need a Naver automobile route between Seoul-area or Korea-wide coordinates with optional waypoints and vehicle options. Do NOT use for transit, walking, bicycle, or legal toll billing decisions. Returns route candidates with distance, duration, fares, path geometry, road sections, and turn-by-turn guide text.

Use when you already have a Naver place ID and need public details such as categories, business hours, menus, photos, review counts, tags, and links. Do NOT use for user-only saved-place metadata or collection membership. Returns a normalized nullable place detail object for read-only display and enrichment workflows.

Use when you need visitor and blog review snippets for a Naver Map place ID with paging and source filtering. Do NOT use for writing reviews, moderation actions, or saved-place exports. Returns normalized review rows with authors, content, ratings, dates, URLs, totals, and source-specific counts.

Use when you need Naver Map place candidates for Korean keywords such as 강남역, 홍대 맛집, or 경복궁 near an optional bias coordinate. Do NOT use for address-only legal geocoding or private saved places. Returns normalized public place summaries with pagination, coordinates, address, contact, distance, and Naver Map URLs.

Use when you need subway, bus, and walking combinations between two coordinates using Naver public transit routing. Do NOT use for car, bicycle, or pedestrian-only navigation. Returns path candidates with duration, fare, transfer count, transport labels, walking time, and leg-by-leg instructions.

Use when you have a Naver public transit identifier and need bus stop, bus route, or subway station detail selected by info_type. Do NOT use for point-to-point route planning or realtime guarantees beyond upstream availability. Returns one normalized detail branch matching the discriminator with coordinates, stops, routes, schedules, and exits.

Use when you need pedestrian directions between two Korean coordinates with recommendation, wide-road, or flat-route preferences. Do NOT use for vehicle routing, transit schedules, or accessibility certification. Returns walking route candidates with distance, duration, path coordinates, and guide instructions.

Use this when a user wants recent or relevance-ranked Naver News search results for a Korean or English keyword. It calls the official Naver Search news API, strips highlight HTML from title and description fields, decodes common HTML entities, and returns normalized URLs and publication timestamps.

Use this when a user wants public Naver Shopping search candidates for a product keyword. It calls the official Naver Search shopping API, strips highlight HTML from titles, and returns product URLs, images, normalized price range fields, mall names, product IDs, brands, makers, category paths, and summary metadata.

Use when you need to browse a public Ohouse store category like furniture or fabric by category id. It returns normalized product rows, exposed totals, and category path metadata from the observed category API.

Use when you need public card recommendations for an Ohouse card collection id. It reads the collection recommendations endpoint and returns the section title plus normalized cards with images, counters, writer labels, and links.

Use when you need public Ohouse comments for a project, card, product, or card collection. It calls the comments endpoint, can optionally hydrate users, and returns comments, totals, and child-inclusive totals.

Use when you need public coupon-display metadata for an Ohouse deal without performing any coupon download or account mutation. It returns price text, button status, messages, and title fields when exposed.

Use when you need the product rows that belong to a public Ohouse deal bundle. It calls the observed deal list endpoint, normalizes included products, and returns exposed total counts for deal merchandising analysis.

Use when you need product rows from a public Ohouse exhibition or campaign section. It calls the exhibition-section-items endpoint and returns normalized products, exposed totals, and next-page state.

Use when you need the recursive public Ohouse product category tree before browsing or mapping catalog ids. It calls the observed categories API and returns stable id/title/image child nodes without login state.

Use when you need public coupon-display metadata for an Ohouse product without performing any coupon download or account mutation. It returns price text, button status, messages, and title fields when exposed.

Use when you need stable public product detail metadata for an Ohouse product id. It reads the store API and normalizes product identity, cards, buy variants, categories, and review summary signals.

Use when you need the public option and selling-state summary for an Ohouse product. It reads the options endpoint and returns product identity, option groups, and sold-out state.

Use when you need public Q&A rows for an Ohouse product page. It calls the questions endpoint and normalizes question text, answer text when present, writer nickname, buyer marker, timestamps, and totals.

Use when you need public recommendation modules attached to an Ohouse product detail page. It calls the product recommended endpoint and summarizes CMS modules into stable ids, titles, types, and product items.

Use when you need public Ohouse product reviews plus optional star-count distribution for a product id. It reads the reviews endpoint, can call the counts helper, and normalizes ratings, comments, writer labels, and totals.

Use when you need delivery, refund or seller-service metadata for a public Ohouse product before checkout-like analysis. It returns fee, free threshold, service level, exchange/refund fees, and seller contact fields when exposed.

Use when you need public user content cards that use or tag a specific Ohouse product. It calls the used-card endpoint and returns normalized card ids, images, captions, counters, and writers.

Use when you already have one or more Ohouse product ids and need public product summaries in one call. It queries the batch products endpoint and normalizes ids, names, urls, pricing, images, and review signals.

Use when you need public Ohouse contents project detail such as a housewarming article. It reads the contents project API and returns title, content type, writer metadata, residence/style fields, section count, and product cards.

Use when you need public recommended Ohouse projects related to an existing contents project. It calls the project recommendations endpoint and normalizes project ids, titles, writer metadata, content type, and section title.

Use when you need current public Ohouse promotion-card metadata without user state. It calls the observed tRPC promotion endpoint and normalizes ids, titles, image URLs, landing URLs, and a valid empty result when no cards are exposed.

Use when you need public Ohouse search portal trends for autocomplete, discovery, or monitoring. It reads the observed portal endpoint and returns ranked popular keywords plus recommended keyword strings.

Use when you need public Ohouse site navigation or category metadata for discovery. It calls the navigation endpoint and deliberately excludes csrf, cookies, login state, cart count, and other session-specific fields.

Use when a tenant needs read-only Ohouse Today Deals without login. Fetches the stable public feed API through Chrome stealth/proxy transport, normalizes deal pricing/review/free-delivery signals, and supports API/local filtering.

Use this operation when a user has selected Yogiyo menu item ids, category ids, quantities, and options and wants to validate the cart, delivery fee, discounts, total amount, blockers, and delivery address before ordering. Guest remote orders are NaverPay-only and always use safety number; show display before raw price internals.

Use this operation when the user has verified their phone number, confirmed the delivery address detail, accepted order-preview.display, and order-preview.can_place_order is true. It submits the guest Yogiyo order with safety number enabled and creates a NaverPay payment URL for handoff.

Use this operation when a user wants to find purchasable Modu Parking tickets near coordinates or a place label. Place labels are geocoded through Modu Parking's own place search (unresolvable labels fail with LOCATION_RESOLVE_FAILED) and searched_location returns the resolved place name. It queries the map POI endpoint and normalizes parking lots into ticket-level results for follow-up detail, availability, or payment steps.

Use this operation when a user selected a ticket_id from search-parking and needs the detailed parking lot, price, operating-hour, purchase-day, and app URL information before deciding whether to proceed to SMS verification or payment. Monthly/period tickets expose no daily purchase schedule: they return available_days as an empty array with daily_schedule_supported=false and must be handed off via app_url instead of start-payment.

Drive checkout to the final review stage without placing an order. Use this to preview the connected shopper's cart and estimated_total before confirmation. Returns stage, cart, estimated_total, requires_confirmation, and notes.

Remove one product_id from the connected shopper's amazon.co.jp cart. Use only with explicit user intent to remove that item. Returns the remove action, whether the product was removed, and the updated cart.

Use this only after the user explicitly confirms a real Charan closet-cleaning pickup request. This submits recipient, phone, address, bag count, and clothing kind to Charan so staff can arrange pickup.

List current authenticated Hot Pepper Gourmet reservations.

Resolve address candidates and block codes from a Japanese postal code.

Resolve a Weverse community ID and URL path from an artist code.

Fetch normalized restaurant detail and course summaries for a Hot Pepper Gourmet restaurant.

Use this operation when a user needs normalized Yogiyo restaurant reviews for a selected shop_id. It returns comment-bearing reviews with ratings, reviewer names, owner replies, ordered menu names, and photos when Yogiyo exposes them.

Use this operation when a user wants to discover Yogiyo restaurants by keyword, food category, address, or coordinates. It normalizes either discovery search or shop-list responses for restaurant selection before menu detail or order-preview steps.

Search the amazon.co.jp catalog by keyword with optional sort, min_price, and max_price filters. Use this to discover products before calling get_product or adding an item to the cart. Returns keyword, page, total, and product summaries using product_id plus snake_case fields.

Search law appendices and form records.

Use this operation when a caller needs read-only discovery of Tabelog search areas, cities, prefectures, or area-group links from observed Tabelog pages, and when later restaurant-search requests need normalized upstream area selectors rather than copied raw URLs or provider-owned aliases.

Use when you need public Ohouse community/content cards for a keyword rather than commerce products. It calls the cards feed endpoint and returns normalized cards, related keywords, totals, and pagination state.

Use this when a user wants to search Charan products by keyword and optional filters such as category, brand, size, price, color, or material.

Search decisions from Korean public committees and commissions.

Search Weverse communities by keyword.

Search current Korean statutes.

Search Rakuten Travel hotels by area and return normalized hotel summary rows.

Search Rakuten Travel hotels by keyword and return normalized hotel rows.

List Rakuten Ichiba attributes available for a genre.

List Rakuten Ichiba genre children for a genre code.

Search Rakuten Ichiba item listings by keyword, genre, shop, or item code and return normalized item, price, shop, image, review, and pagination fields.

Search Rakuten Item Price Navi product records and return normalized product price ranges and review metadata.

Find old/new or three-way comparison entries for a Korean law.

Search Korean legal interpretation records.

Search by source id or preset and return legal resource summaries.

Search legal-term dictionary entries and definitions.

Search ministry interpretation records across supported agencies.

Search Korean precedent summaries.

Use when you need public Ohouse commerce search results for a keyword without login. It calls the observed APIG commerce body endpoint, normalizes product cards, and preserves pagination tokens for follow-up queries.

Use this operation when a caller needs read-only restaurant discovery for a Tabelog area selector returned by search-areas, a prefecture slug, or a full Tabelog area URL, visit date, and diner count, and when the result must include normalized availability signals, booking plan identifiers, and semantic slot metadata for downstream reservation inspection steps.

Search Hot Pepper Gourmet restaurants with normalized area, keyword, genre, budget, date/time, party-size, amenity, seat, and smoking filters.

Search Demaecan shops by block code and optional genre, sort, wait time, and page.

Search Korean treaty records.

Search Rakuten Travel hotel vacancy for a date range. If dates are omitted, runtime health probes calculate a safe future one-night stay.

Use this operation when a user is ready to place a Yogiyo order and needs an SMS verification code sent to their phone. It creates a short-lived anonymous Yogiyo order session and returns yogiyo_session_id for confirm-phone and place-order.

Use this when a user provides a Seoul latitude and longitude and wants nearby 따릉이 rental station availability. It fetches the official Seoul bikeList real-time station rows, filters by radius using station coordinates, and returns station names, rack totals, available bike counts, sharing ratio, and coordinates.

Use this when a user asks how crowded a supported Seoul hotspot is right now. It calls the official Seoul citydata endpoint for one exact hotspot name and returns the normalized population congestion level, congestion message, estimated population min/max range, and population reference time.

Use this when a user asks when trains are arriving at a Seoul subway station right now. It calls the official Seoul real-time subway arrival endpoint for the station name and returns line IDs, up/down direction, train destination text, arrival seconds, and arrival messages from the upstream rows.

Use this operation when search-parking or parking-detail returned a share_seq and the user needs shared-parking duration and price choices before starting payment. Business rule: this endpoint confirms purchasable duration/price candidates, but shared parking occupancy can change; final full/in-use rejection is only confirmed when start-payment creates the upstream payment URL.

List Weverse Shop artist home banners.

List recent Weverse Shop sales for one artist.

Get Weverse Shop cart item counts.

Fetch shop detail, menu categories, reviews, and rating distribution.

List Weverse Shop home banners.

List Weverse Shop home notices.

Call Weverse Shop logout for the connected session.

List Weverse Shop marketing banners for sales.

Get Weverse Shop pickup banner data.

Get Weverse Shop pickup detail.

List Weverse Shop POD sales blocks.

List recent Weverse Shop sales by artist IDs.

List recommended Weverse Shop sales by artist IDs.

List Weverse Shop recommendations for a sale.

Get Weverse Shop return and exchange information by sale type.

List Weverse Shop sale curation blocks.

Use this operation when a user has chosen a Yogiyo shop_id and needs full restaurant details, menu categories, menu item/category ids, prices, sold-out flags, option counts, and sampled reviews before building an order. Fetch option section ids and option ids for one selected menu item with menu-item-options.

Return time slots, course options, and seat options for a restaurant/date/party-size combination.

Use this operation when the user provides the Yogiyo SMS code received from verify-phone. It confirms the phone number on the same anonymous Yogiyo session identified by yogiyo_session_id before place-order is attempted.

Use this operation when a user is ready to pay for a Modu Parking ticket and needs the upstream SMS authentication code sent to their phone. It returns auth_code_seq for the next start-payment call.

Use this operation when the user has received a Modu Parking SMS code and wants to start payment. It verifies the code, logs in as a guest, and creates either a coupon or shared-parking payment webview URL. Business rule: ticket payments are preflighted before SMS using current ticket price/window data; shared payments are preflighted for duration/price before SMS, but Modu can still reject the final payment URL creation with code NOT_PURCHASABLE when the shared space is full or already in use. Monthly/period tickets expose no available_days and cannot be purchased through start-payment; they are rejected with NOT_PURCHASABLE — hand off via the parking-detail app_url instead.