# Actor Picker Korean English (`xman-workbook/actor-picker-korean-english`) Actor

Describe a task in Korean or English and get the Apify Store Actors that fit, with the price in plain words, real usage and run completion figures, cautions, and ready-to-use API and MCP connection URLs. No AI guesswork: a clear rule on live Store data.

- **URL**: https://apify.com/xman-workbook/actor-picker-korean-english.md
- **Developed by:** [X-man Tools](https://apify.com/xman-workbook) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 searches

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Actor Picker - Find the Right Apify Actor (Korean & English)

Tell it what you want to do, in Korean or English. It returns the Apify Store Actors that fit, each with a plain-language price, real usage figures, cautions, and the URLs you need to connect right away.

한국어로 "하고 싶은 일"을 적으면 Apify Store의 수많은 도구 가운데 맞는 것을 골라, 값과 믿을 만한 정도를 쉬운 말로 설명하고 바로 연결할 주소까지 돌려줍니다.

### When to use this

- You (or your AI agent) know the task but not which of the many Store Actors to trust.
- You want the price in plain words ("about $1 per 1,000 results") instead of an event table.
- You want to see how many people use an Actor and how often its runs finish without error before you pay for a run.
- You work in Korean. Korean task descriptions such as "네이버 플레이스 리뷰 수집" or "유튜브 영상 자막 가져오기" are understood through a built-in Korean term list.

### What you get for each recommended Actor

| Field | Meaning |
|---|---|
| `title`, `actor`, `developer`, `storeUrl` | What it is and where it lives |
| `listingExcerpt` | A short excerpt (at most 140 characters including the ellipsis) of the developer's own description; the full text is at `storeUrl` |
| `priceKo`, `priceEn` | The main price in plain words, with the start fee amount and the number of extra charged events when they exist |
| `priceUsdPer1000`, `perResultPriceConfirmed`, `priceMonthlyUsd` | Numbers. `priceUsdPer1000` is filled only when a per-result price is confirmed |
| `users30Days`, `totalUsers`, `publicRuns30Days`, `runCompletionRate30DaysPercent` | Usage figures from the Store, and the share of public runs in the last 30 days that finished without error |
| `trustKo`, `trustEn` | The same figures as one sentence |
| `cautionsKo`, `cautionsEn` | Warnings: few users, low success rate, no recent runs, maintenance or deprecation notices |
| `supportsAgenticPayments` | Whether the Store marks it as usable with agentic payments |
| `connect` | `runApiUrl`, `runSyncApiUrl`, `mcpServerUrl`, `inputSchemaPage`, `apiExamplesPage` |

The run also stores an `OUTPUT` record with `summaryKo` and `summaryEn`, the search keywords used, and the full list.

Example input:

```json
{ "query": "네이버 플레이스 리뷰 수집", "maxResults": 3 }
```

Example output item (shortened; the figures change over time):

```json
{ "rank": 1, "title": "Naver Place Reviews + Blog", "actor": "huggable_quote/naver-place-reviews-scraper",
  "users30Days": 31, "runCompletionRate30DaysPercent": 98.8, "cautionsKo": [],
  "priceUsdPer1000": 1,
  "connect": { "runApiUrl": "https://api.apify.com/v2/acts/huggable_quote~naver-place-reviews-scraper/runs",
               "mcpServerUrl": "https://mcp.apify.com/?tools=huggable_quote/naver-place-reviews-scraper" } }
```

### How it works, and its limits

- It searches the public Apify Store list with keywords taken from your sentence. It drops candidates that match fewer than half of the keywords, and candidates that do not mention a site you named. When you also name a sub-service that belongs to that site (for example Naver place, blog, shopping, news, cafe, map; Google maps, news, trends, play), the candidate must mention it too. When you name a kind of data from the built-in list (for example transcript or subtitles, reviews, comments, followers, email, price, jobs, ranking), the candidate must mention that kind of data too; singular and plural count as the same word. Candidates below a minimum match score are not returned. The site check covers the sites in the built-in list (about 60, such as Naver, Coupang, Instagram, YouTube, Google, Amazon, App Store); a site outside that list is treated as an ordinary keyword. The remaining candidates are ranked by keyword match, recent users and 30-day run completion rate. Many users is a sign of use, not proof of quality. No AI model is involved: the same candidates and figures always give the same order. The Store list and its figures change over time, so results can differ between runs. It is a rule-based ranking, not a guarantee that an Actor fits your exact case.
- Korean is handled by a term list (sites such as 네이버, 쿠팡, 인스타그램 and data words such as 리뷰, 가격, 자막). A Korean sentence made only of words outside that list returns `NO_KEYWORDS`; add the site name or write it in English. Words of exclusion are not understood: a site you name is always treated as wanted, so "not Baemin, Google Maps reviews" (배민 말고 구글 지도 리뷰) requires both sites and may return no match. Name only the sites you want.
- The price shown is the Actor's main price, not the total cost of a run. The `maxPriceUsdPer1000` filter compares only that main per-result price. For tiered prices it is the Free-plan price. When the main charged event is not a per-result event, the text says so and `priceUsdPer1000` stays empty. When a price cannot be read it says "could not be confirmed" rather than "free". Always check the listing before a large run.
- Usage and completion figures come from the Store at the time of the run (`retrievedAt`). A run that finished without error is not proof that its data was correct or complete.
- It does not run the recommended Actors and does not read their input schemas. Open `connect.inputSchemaPage` before the first run. The API URLs are POST endpoints that need a JSON input body and your own Apify API token; the synchronous URL waits at most 300 seconds.
- Recommendations are not paid placements. X-man Tools has no arrangement with the listed developers.

### Pricing

Pay per event. Every run, including runs that end in an error or no match, has the standard Actor start event ($0.00005 per GB of memory, at least one). This Actor's memory is capped at 1 GB, so the start event is charged once per run. A search that returns at least one recommendation adds one `search` event ($0.01), charged only after the recommendations have been stored. Invalid input, no match, and Store outages do not trigger the `search` event. The `charged` and `chargeStatus` fields report whether the `search` event was charged; if a run is interrupted right after charging, `chargeStatus` can remain `PENDING`, and the run's charge record is the reference. Platform usage is included.

### Data source

The public Apify Store list API (`https://api.apify.com/v2/store`). Only a short excerpt of each listing description is returned, with a link to the listing. The descriptions belong to their developers.

# Actor input Schema

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

Describe the task in Korean or English, naming the site and the data you need. Examples: "네이버 플레이스 리뷰 수집", "instagram profile posts", "유튜브 영상 자막 가져오기". Up to 300 characters.

## `maxResults` (type: `integer`):

Number of Actors to return, from 1 to 10.

## `maxPriceUsdPer1000` (type: `integer`):

Optional whole number. Keep only Actors whose confirmed main per-result price is at or below this many US dollars per 1,000 results. This is a cap on the main result price only, not on total cost: start fees and extra charged events are not added. Actors priced per month, per other event, or with an unconfirmed price are left out when this is set.

## `minUsers30Days` (type: `integer`):

Optional. Keep only Actors with at least this many users in the last 30 days.

## Actor input object example

```json
{
  "query": "네이버 플레이스 리뷰 수집",
  "maxResults": 5,
  "minUsers30Days": 0
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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": "네이버 플레이스 리뷰 수집"
};

// Run the Actor and wait for it to finish
const run = await client.actor("xman-workbook/actor-picker-korean-english").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": "네이버 플레이스 리뷰 수집" }

# Run the Actor and wait for it to finish
run = client.actor("xman-workbook/actor-picker-korean-english").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": "네이버 플레이스 리뷰 수집"
}' |
apify call xman-workbook/actor-picker-korean-english --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,xman-workbook/actor-picker-korean-english"
        }
    }
}
```

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/chhBXjXhy6WvOzqbf/builds/7gsUvh7SMa68IvxCT/openapi.json