# Naver Search API → Clean English JSON (`maolab/naver-search-api`) Actor

Korean Naver search results normalized to English JSON via the official Naver Open API. News, blog, web, and shopping verticals.

- **URL**: https://apify.com/maolab/naver-search-api.md
- **Developed by:** [MAOLAB](https://apify.com/maolab) (community)
- **Categories:** Developer tools, E-commerce, AI
- **Stats:** 3 total users, 0 monthly users, 93.5% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $30.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Naver Search API → Clean English JSON

Search Korea's largest portal in your own language. This Apify Actor calls Naver's official Open Search API and returns clean English JSON, ready for AI agents, dashboards, and analytics pipelines.

### What it does

- Calls the **official Naver Open API** (no scraping, no ToS gray area) for **news, blog, web, and shopping** results
- **Normalizes Korean → English** with Claude Haiku, including HTML entity stripping and entity preservation (BTS, Samsung, BLACKPINK stay BTS, Samsung, BLACKPINK)
- Returns a **flat, predictable JSON schema** with title, summary, source URL, publish date, and translation confidence

### Use cases

1. **AI agents** — drop into Claude Desktop, Cursor, or any MCP client to make Korean web searchable in English chats
2. **Trend analysts** — track K-pop, K-drama, K-beauty, or any keyword across Naver News and Blogs in English
3. **E-commerce research** — pull Naver Shopping results for cross-border arbitrage, price monitoring, or competitor scans
4. **Newsroom & investor research** — surface Korean coverage of global brands, executives, or events without a translator
5. **Workflow automation** — wire into Make, n8n, Zapier, or LangChain for agent workflows that touch Korean data

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `query` | string (required) | — | Keyword. Korean (`방탄소년단`) and English (`BTS`) are both supported. |
| `search_type` | enum | `news` | One of `news`, `blog`, `webkr`, `shop`. |
| `max_results` | integer | `10` | Between 1 and 100. |
| `translate` | boolean | `true` | If `true`, normalize to English with Claude Haiku. If `false`, return raw Korean (still HTML-stripped). |
| `sort` | enum | `sim` | `sim` (relevance) or `date`. |

#### Example inputs

```json
{ "query": "BTS", "search_type": "news", "max_results": 5 }
```

```json
{ "query": "K-beauty trends", "search_type": "blog", "max_results": 20 }
```

```json
{ "query": "삼성전자 실적", "search_type": "news", "max_results": 10, "sort": "date" }
```

```json
{ "query": "iPhone 17 케이스", "search_type": "shop", "max_results": 15 }
```

```json
{ "query": "korea startup ecosystem", "search_type": "webkr", "max_results": 25 }
```

### Output

Each result is pushed to the default dataset as a flat record:

```json
{
  "title": "BTS announces world tour 2026",
  "summary": "BTS revealed their first world tour since 2024, opening in Seoul on June 12.",
  "source_url": "https://n.news.naver.com/article/...",
  "published_at": "Mon, 05 May 2026 10:00:00 +0900",
  "language": "ko",
  "translation_quality": 0.95,
  "search_type": "news",
  "source": "naver",
  "raw": { "title": "<b>BTS</b> 월드투어 발표", "description": "...", "link": "..." }
}
```

`raw` preserves the untouched Naver record so you can recover vertical-specific fields (e.g. `lprice`, `mallName`, `bloggername`) when you need them.

### Pricing

**Pay-per-event: $0.03 per result returned.** No subscription, no minimums.

| Run | Cost |
|---|---|
| 10 results | $0.30 |
| 100 results | $3.00 |
| 0 results (no match) | $0.00 |
| Errors (rate limit, bad credentials, network) | $0.00 |

### Why this Actor

| | This Actor | Generic web scraper | Raw Naver API |
|---|---|---|---|
| Korean → English translation | ✅ Claude Haiku | ❌ | ❌ |
| Official API (ToS-safe) | ✅ | ⚠️ Often gray | ✅ |
| Flat English JSON schema | ✅ | ❌ | ❌ |
| MCP / Make / n8n / Zapier | ✅ auto-listed | Sometimes | Manual integration |
| HTML & entity cleanup | ✅ | ❌ | ❌ |
| Pay-per-result, no subscription | ✅ | Varies | n/a |

### Compatibility

- **Apify Console** — run interactively or via the Apify API
- **Apify MCP server** — exposed at `mcp.apify.com`
- **Claude Desktop / Cursor / Cline** — via the Apify MCP connector
- **Make.com, n8n, Zapier** — auto-listed through Apify's native integrations
- **Anywhere with HTTP** — call the `run-sync-get-dataset-items` endpoint

### Compliance

- Uses the **official Naver Open API** under its commercial-allowed terms (25,000 calls/day quota per app, attribution required)
- Returns **metadata and short summaries only** — never republishes full article bodies
- **No personal data collection**; no scraping; no ToS gray areas
- Source attribution preserved in the `source_url` and `source` fields of every record

### Author

Built and maintained by an independent Korean developer focused on bridging Korean public data to global AI agents. For bugs, feature requests, or vertical additions, leave a comment on the Actor page.

***

Keywords: korean search api, korea search, naver api, naver search, korean news, korean blog, korean shopping, k-pop tracker, k-beauty trends, korea data mcp, claude mcp korea, cursor mcp korea, korean to english translation, korean web search api, korea ai agent.

# Actor input Schema

## `query` (type: `string`):

Keyword to search on Naver. Korean and English are both supported.

## `search_type` (type: `string`):

Which Naver Open Search vertical to query.

## `max_results` (type: `integer`):

How many results to return (1–100).

## `translate` (type: `boolean`):

If enabled, normalize each result to English with Claude Haiku. If disabled, return raw Korean (still HTML-stripped).

## `sort` (type: `string`):

Sort by relevance (default) or by date.

## Actor input object example

```json
{
  "query": "BTS",
  "search_type": "news",
  "max_results": 10,
  "translate": true,
  "sort": "sim"
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "BTS"
};

// Run the Actor and wait for it to finish
const run = await client.actor("maolab/naver-search-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "query": "BTS" }

# Run the Actor and wait for it to finish
run = client.actor("maolab/naver-search-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "BTS"
}' |
apify call maolab/naver-search-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maolab/naver-search-api"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/FI2e6NMhFjRcWWy1f/builds/8mqzagb0a1YmVveEu/openapi.json