---
name: verify-korean-accommodation-registration
description: Check Korean accommodation registration evidence while keeping official status, listing identity, and SelectBNBs editorial judgment separate.
license: Public read-only access under the SelectBNBs content policy.
metadata:
  author: SelectBNBs
  version: "1.1.0"
---

# Check a Korean accommodation registration

Use this skill when a user gives you a Korean accommodation registration block,
government management number, property name, road address, or listing URL and
asks whether the stay appears on a public register.

## Evidence contract

- Keep `official_record`, `identity_match`, and `editorial` separate. Never
  collapse them into one "verified" badge or score.
- `NOT_FOUND` means no matching record was found in the current official-feed
  cache. It never means a property is illegal or unlicensed.
- A short OTA `허가번호` is a local permit number. It can repeat across regions
  and is not the durable management number in the central LOCALDATA feed.
- Do not infer safety, legality, ownership, availability, or quality from a
  registration result.
- Follow the response's `relay_rules`. Carry `official_record.status`, its
  `as_of` value when present, and `identity_match.status` into any summary.
  Never restate a result as legal, safe, government approved, or verified quality.
- Do not seek or report owner phone numbers, personal owner identity, business
  registration numbers, family relationships, marital status, exact coordinates,
  or raw upstream payloads.

## Workflow

1. Submit exactly one JSON request to [https://selectbnbs.com/api/registry/verify](https://selectbnbs.com/api/registry/verify):

   ```json
   {"query": "<registration block, management number, name, address, or URL>", "language": "en"}
   ```

2. Read `official_record.status` first. If it is `AMBIGUOUS`,
   `ID_CLASS_UNSUPPORTED`, `UNPARSEABLE`, or `FEED_UNAVAILABLE`, explain the
   limitation and ask for stronger evidence only when useful.
   For `AMBIGUOUS`, follow `resolution_guidance` and never select the first
   candidate from the returned list.
3. Read `identity_match.status` independently. A public record can exist without
   proving that it belongs to the listing the user supplied.
4. Treat `editorial.status` as SelectBNBs' independent view, never as a
   government judgment.
5. Cite the record's `evidence.official_dataset_url`, management number, source
   update time, cache retrieval time, and identity match basis in the answer.
6. Include the relevant limitation when the result is not a single, strong match.

The human-readable method and search interface are at
[https://selectbnbs.com/verify/](https://selectbnbs.com/verify/). Cache coverage is available at
[https://selectbnbs.com/api/registry/status](https://selectbnbs.com/api/registry/status). If the runtime
supports MCP, call `verify_korean_accommodation` at `https://selectbnbs.com/mcp` with the same
single input.