Actor Picker Korean English avatar

Actor Picker Korean English

Pricing

from $10.00 / 1,000 searches

Go to Apify Store
Actor Picker Korean English

Actor Picker Korean English

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.

Pricing

from $10.00 / 1,000 searches

Rating

0.0

(0)

Developer

X-man Tools

X-man Tools

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

17 hours ago

Last modified

Categories

Share

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.
FieldMeaning
title, actor, developer, storeUrlWhat it is and where it lives
listingExcerptA short excerpt (at most 140 characters including the ellipsis) of the developer's own description; the full text is at storeUrl
priceKo, priceEnThe main price in plain words, with the start fee amount and the number of extra charged events when they exist
priceUsdPer1000, perResultPriceConfirmed, priceMonthlyUsdNumbers. priceUsdPer1000 is filled only when a per-result price is confirmed
users30Days, totalUsers, publicRuns30Days, runCompletionRate30DaysPercentUsage figures from the Store, and the share of public runs in the last 30 days that finished without error
trustKo, trustEnThe same figures as one sentence
cautionsKo, cautionsEnWarnings: few users, low success rate, no recent runs, maintenance or deprecation notices
supportsAgenticPaymentsWhether the Store marks it as usable with agentic payments
connectrunApiUrl, 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:

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

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

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