Provider 디렉토리

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.

Use this operation when search-parking or parking-detail returned a share_seq and the user needs to know which shared parking durations are currently available, including slot prices, before starting payment.

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 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.

Retrieves KMA mid-term temperature forecast for a Korean region, providing daily min/max temperatures with confidence ranges for days 3 through 10. Use when the user asks about weather forecasts for the coming week or beyond 2 days. Do NOT use for current weather or hourly data — use kma:short-forecast instead. Returns an array of daily forecasts with temperature ranges.

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 when authenticated saved-place detail is required, including user memo or private saved metadata in addition to public place fields. Do NOT use for generic public place detail when no Naver session is available. Returns a normalized authenticated place detail object with coordinates, contact fields, tags, memo, review counts, and collection context.

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 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 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 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 authenticated collection exports. Returns normalized review rows with authors, content, ratings, dates, URLs, totals, and source-specific counts.

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 an authenticated user wants to list their own Naver Map saved-place collections after pasting a valid browser cookie. Do NOT use for public place search, unauthenticated access, or modifying saved places. Returns synthetic-safe normalized collection metadata including IDs, names, counts, owner, visibility, and updated timestamps.

Use when an authenticated user wants a bounded read-only export of their Naver Map saved collections and places for backup or migration planning. Do NOT use for continuous crawling, public search, or write operations. Returns collections with nested places and a truncated boolean that signals whether max_collections or max_places_per_collection removed upstream data.

Use when an authenticated user wants the places stored inside one Naver Map collection they own or can view through their session. Do NOT use for listing all collections, public search, or changing collection membership. Returns saved place rows with collection ID, place ID, coordinates, address, memo, tags, and timestamps.

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 this operation when you need Daiso pickup-capable store candidates by keyword or nearby coordinates and want the renewed /mb/mbc/selPkupStrList endpoint response normalized with source payload coverage metadata.

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 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.

Use this operation when you have one Daiso product_id and store_code and need the renewed pickup-stock result from the HAR-observed selStrPkupStck endpoint, including resolved, blocked, no-data, or partial metadata.

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:products first to get the product_id. Returns a list of stores with stock status and quantity.

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:products or daiso:inventory instead. Returns store name, address, phone number, and coordinates for each matching location.

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.

Use this operation when you have one Daiso product_id and store_code and need the renewed in-store floor, zone, or shelf-location rows from selIntPdStDispInfo without also fetching pickup stock.

Searches the Daiso online product catalog by keyword, returning product name, price, ID, image, and category. Use when the user wants to find specific Daiso products, check prices, or browse items by keyword. Do NOT use for checking in-store availability — use daiso:inventory instead. Returns paginated product results with optional total count.

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 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.

Gets grouped Daiso product detail by product ID, faning out to HAR-observed detail, description, notification, thumbnail, attribute, and review-count endpoints. Use after daiso:search_products/products when product_id is known. Optional endpoint failures are surfaced in meta.failed_endpoints instead of being silently dropped.

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 promotion, banner, exhibition, or corner content surfaces observed in the renewed HAR, grouped into a single read-only response with endpoint-level coverage metadata.

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 a user has chosen a Yogiyo shop_id and needs full restaurant details, menu categories, option section ids, option ids, prices, sold-out flags, and sampled reviews before building an order.

Searches the Korean National Law Information Center for laws, precedents, and administrative rules by keyword. Use when the user asks about a specific Korean law, legal case, or regulation by name or topic. Do NOT use for reading full law text — use law:detail instead. Returns a list of matching results with type, ID, name, date, and direct link to law.go.kr.

Retrieves law.go.kr old/new law list, three-way comparison list, or HTML-only legislative history data. Use when the user wants to find comparison/history entries before opening upstream detail links. Do NOT use for reading current law text — use law:detail instead. The response exposes only evidence-backed list envelope fields and preserves target-specific rows as upstream JSON objects because row keys differ by law.go.kr target.

Looks up definitions of Korean legal terms from the National Law Information Center, optionally including references to the laws that define them. Use when the user asks about the meaning of a legal term such as 소멸시효, 선의취득, or 불법행위. Do NOT use for searching laws by name — use law:search instead. Returns matching terms with definitions and source law names.

Retrieves the full text of a Korean law by name, including individual articles with numbers, titles, and content. Use when the user wants to read specific articles or the complete text of a law. Do NOT use for searching laws by keyword — use law:search instead. Returns law name, ID, enforcement date, and an array of articles.

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).

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.

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, warnings, and delivery address before ordering.

Use this operation when the user has verified their phone number, confirmed the delivery address detail, and accepted the cart preview. It submits the Yogiyo order and creates a NaverPay payment URL for handoff.

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.

Use this operation when a user wants to find purchasable Modu Parking tickets near coordinates or a known Korean place label. It queries the map POI endpoint and normalizes parking lots into ticket-level results for follow-up detail, availability, or payment steps.

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.

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 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 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.

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.

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.

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.

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.

Converts a Korean address or place name into geographic coordinates (latitude and longitude) via KakaoMap geocoding. Use when the user provides an address or landmark name and you need coordinates for directions or weather lookup. Do NOT use for searching multiple places by keyword — use kakaomap:search instead. Returns one or more address matches with lat/lng and address type.

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.

Retrieves the current delivery status and 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.

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.

Use this operation when a user is ready to place a Yogiyo order and needs an SMS verification code sent to their phone. It must run on a Yogiyo Connection so the same guest customer session is reused later.

Use this operation when the user provides the Yogiyo SMS code received from verify-phone. It confirms the phone number on the same connected anonymous guest customer before place-order is attempted.

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.

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.

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 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.

Checks available 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 — use catchtable:reserve instead. Returns available date slots (if no date given) or time slots (if date specified) based on party size and table type.

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.

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 at a restaurant after checking availability. Do NOT use without first checking catchtable:availability. Returns a reservation reference ID, status, and confirmed visit details. Requires Catchtable authentication.

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.

Registers the user in a restaurant's waiting queue on Catchtable for a specified table type and party size. Use when the user wants to join the waiting list at a restaurant that supports walk-in waitings. Do NOT use for reservations — use catchtable:reserve instead. Returns a waiting reference ID, queue position, and status. 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.

Retrieves the current waiting queue status at a restaurant on Catchtable, including the number of teams waiting, estimated wait time, and whether the restaurant is open. Use when the user wants to check how busy a restaurant is before joining the queue. Do NOT use for registering — use catchtable:register-waiting instead. Returns waiting count, estimated minutes, and open status.

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 preserves source URL evidence and declares live probing unsupported.

Use when a tenant needs read-only Daangn cars listings for a Korean region and optional keyword without a user login. It resolves the public region id first, requests the Remix _data route, returns normalized listing candidates, and preserves the effective region plus source URL for audit.

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 preserves source URL evidence and declares live probing unsupported.

Use when a tenant needs read-only Daangn jobs listings for a Korean region and optional keyword without a user login. It resolves the public region id first, requests the Remix _data route, returns normalized listing candidates, and preserves the effective region plus source URL for audit.

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 preserves source URL evidence and declares live probing unsupported.

Use when a tenant needs read-only Daangn realty listings for a Korean region and optional keyword without a user login. It resolves the public region id first, requests the Remix _data route, returns normalized listing candidates, and preserves the effective region plus source URL for audit.

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 preserves source URL evidence and declares live probing unsupported.

Use when a tenant needs read-only Daangn used-goods listings for a Korean region and optional keyword without a user login. It resolves the public region id first, requests the Remix _data route, returns normalized listing candidates, and preserves the effective region plus source URL for audit.

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.

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.

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 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 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, production, or card collection. It calls the comments endpoint, can optionally hydrate users, and returns comments, totals, child-inclusive totals, and source URL.

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, next-page state, and the exact source URL.

Use when you need public coupon-display metadata for an Ohouse product or 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 delivery, refund or seller-service metadata for a public Ohouse product before checkout-like analysis. It returns fee, free threshold, service code, exchange/refund fees, and seller contact fields when exposed.

Use when you need stable public product detail metadata for an Ohouse goods 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 goods id. It reads the options endpoint and returns product identity, option group count, sold-out state, and source URL.

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 production id. It reads the reviews endpoint, can call the counts helper, and normalizes ratings, comments, writer labels, and totals.

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

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 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, pagination state, and source URL.

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 when a tenant needs read-only Ohouse Today Deals without login. Fetches the stable public feed API through Chrome TLS/proxy transport, normalizes deal pricing/review/free-delivery signals, and supports API/local filtering.

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