# Rakuma Scraper: Japan Sold Prices & New Listing Alerts (`accountable_eel/rakuma-listing-lookup`) Actor

Rakuma (fril.jp) scraper for Japan's flea-market app: search by Japanese or English keyword for sold prices and on-sale listings in JPY, with brand and category. Optional sold-comps summary, new-listing and price-below alerts to Discord, Slack or Telegram. No login. Pay per listing.

- **URL**: https://apify.com/accountable_eel/rakuma-listing-lookup.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 listing returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Rakuma Scraper: Japan Sold Prices & New Listing Alerts

Search Rakuma (fril.jp), the flea-market app run by Rakuten, by Japanese or English keyword and get one row per listing: price in yen, whether it sold, brand and category, with a link. Switch to the sold view for what items really sold for, add a sold-comps summary (median sold price against median asking price), and get a Discord, Slack or Telegram message when a new listing, a newly sold item or a price at or below your target shows up. No login, no cookies, no images, and a search that finds nothing is free.

### Who it's for

- **Japan-sourcing resellers** who buy on Rakuma and Mercari and need to know what a Pokémon card, a bag or a console actually sells for before they bid.
- **Price trackers and deal watchers** who want a message the moment something under their target price is listed.
- **Analysts and AI agents** who need Rakuma sold prices as clean JSON, CSV or Excel.

### What you get

One row per listing:

- the Rakuma **item ID**, **title**, **link** and **price in JPY** (not converted);
- a **sold** flag, so a sold search and an on-sale search read the same;
- the **brand** and the **category** as Rakuma shows them (in Japanese), plus the category ID;
- with monitoring on: whether the listing is **new**, had a **price drop**, or is **unchanged** since your last run.

Add the **comps summary** and each search also gets one extra row: how many sold and on-sale listings were counted, the median price of each, the gap between asking and sold in percent, and how many listings of each kind Rakuma has in total. It uses the same definitions as the Mercari Japan scraper in this portfolio, so the two read alike.

### Example: sold prices, comps and a Discord alert

Sold prices for a Pokémon card search, plus the summary, with a message to Discord whenever a new item shows up in the sold feed (schedule it hourly):

```json
{
  "searches": ["ポケモンカード"],
  "mode": "sold",
  "maxItems": 80,
  "includeCompsSummary": true,
  "deltaMode": true,
  "deltaName": "pokemon-sold",
  "notifyUrl": "https://discord.com/api/webhooks/<id>/<token>"
}
```

The first run remembers what it saw and sends nothing. Every later run returns the listings and posts one message per item that was not there before. Put `"alertOn": "price-below"` and `"alertPriceBelowJpy": 3000` with `"mode": "on-sale"` to be told about listings at or under ¥3,000 instead.

### Fields

| Field | What it is |
| --- | --- |
| `rowType` | `listing`, or `summary` for the comps row |
| `itemId`, `url`, `title` | the Rakuma item ID, its link and its title |
| `priceJpy` | price in yen; a sold item keeps the price it was listed at |
| `sold` | true when Rakuma marks the item SOLD OUT |
| `brand`, `category`, `categoryId` | as Rakuma shows them; `brand` is empty on unbranded items |
| `checkedAt` | when this run read the page |
| `changeType`, `previousPriceJpy`, `priceDropPct`, `isAlert` | monitoring only: `baseline`, `new`, `price-drop`, `price-rise` or `unchanged`, and whether the row matches your "Alert on" choice |
| `searchMode`, `totalAvailable`, `listingsFetched`, `truncated` | summary row: the mode, how many listings Rakuma has for the search, how many this run read, whether more existed |
| `activeCount`, `soldCount`, `activeTotal`, `soldTotal` | summary row: listings counted from each feed, and Rakuma's totals for each |
| `activeMedianPrice`, `soldMedianPrice`, `askVsSoldGapPct` | summary row: median asking price, median sold price (JPY) and the gap in percent |
| `notifyErrors` | why an alert message did not arrive (empty when it did) |

### Limits

- **Yen only**, as Rakuma shows them. Nothing is converted.
- **No sale date.** Rakuma publishes none, so the summary has no "days to sell" and sold rows are ordered by the site's own newest-first order, not by sale date.
- **Condition and shipping are not returned.** They are not on the search page, only on each item's own page, which this actor does not open.
- **No images** and no seller details: just the listing facts above.
- **Search as the site shows it.** Rakuma matches loosely and shows up to 100 pages of 40; this actor returns at most 1,000 listings per search. A keyword Rakuma cannot match at all is reported as not found (free) when it only offers unrelated items.
- **Rakuma's search also reads descriptions.** A short brand word returns listings whose title never mentions it (in a live check, 51 of 80 sold "supreme" titles did). Add `includeKeywords` if you want the title to carry the word.
- **The summary is a sample.** It counts the listings this run read for the chosen mode, plus the 40 newest listings of the other mode. A narrow search with a small `maxItems` gives a small sample.
- **Sold prices include outliers** (a listing priced at ¥9,888,000 is a real row). The summary uses medians for that reason.
- Requests are made one per second, through a Japanese residential proxy: Rakuma refuses the shared datacenter proxy.

### Monitoring and alerts

Turn on **Monitor** and the actor keeps one record per watchlist, search and mode in a named store (`rakuma-listing-lookup-delta`), up to 20,000 listing IDs each, oldest forgotten first. Use the newest-first order and a small `maxItems` so a new listing is always inside the window. **Only return rows that match my alert** returns and bills just the alert rows; **Seed silently** makes the first run return and bill nothing. Alert messages are free, are sent only for rows you were billed for, never carry an image, and a failed message never fails the run. The webhook link is stored encrypted and never appears in logs or results.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `searches` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~rakuma-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["ポケモンカード"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "searches": [
    "ポケモンカード"
  ]
}
```

One search per line: keywords like "ポケモンカード" or "supreme", or paste a fril.jp search link (only its keywords are read; the link is never opened). Rakuma matches loosely, so a keyword it does not know is reported as not found. Accepted formats: ポケモンカード, supreme, https://fril.jp/s?query=nintendo+switch.

### Sample output

| query | found | status | rowType | itemId | url | title | priceJpy | sold | brand | category | categoryId | checkedAt | changeType | previousPriceJpy | priceDropPct | isAlert | isSummary | searchMode | totalAvailable | listingsFetched | truncated | activeCount | soldCount | activeTotal | soldTotal | activeMedianPrice | soldMedianPrice | askVsSoldGapPct | notifyErrors | rows | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| ポケモンカード | true | OK | \<row type (listing or summary)> | <rakuma item id> | <listing link> | <title> | \<price (jpy; for a sold item, its last asking price)> | <sold> | <brand> | <category> | <category id> | <checked at> | \<change since last run (baseline / new / price-drop / price-rise / unchanged; monitoring only)> | \<price at the last run, jpy (monitoring only)> | \<price drop since the last run, % (monitoring only)> | \<matches your alert (monitoring only)> | <comps summary row> | \<mode of the search (sold or on-sale; summary row)> | \<total matching on rakuma (summary row)> | \<listings this run fetched (summary row)> | \<more results were available (summary row)> | \<on-sale listings counted in the summary (summary row)> | \<sold listings counted in the summary (summary row)> | \<total on-sale listings matching on rakuma (summary row)> | \<total sold listings matching on rakuma (summary row)> | \<median asking price of the on-sale listings counted, jpy (summary row)> | \<median sold price of the sold listings counted, jpy (summary row)> | \<asking vs. sold median price gap in % (summary row)> | \<alert delivery problems (empty when the alert arrived)> | \<all rows of the search in one cell (only when one row per listing is turned off)> | 1970-01-01T00:00:00.000Z |

A search that finds nothing, a link that is not a keyword, and a block come back as a row with `"found": false` and a plain-English message, and are never charged.

### Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed
per item only when data is actually found and returned — see
`.actor/pay_per_event.json` for exact prices. A miss is never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~rakuma-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["ポケモンカード"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~rakuma-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"searches":["ポケモンカード"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~rakuma-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"searches":["{{search}}"]}`, mapping the row's search into the `searches` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Rakuma Scraper: Japan Sold Prices & New Listing Alerts" — the agent will find and run this actor.

### Data and privacy

The actor reads public search pages on fril.jp only, the same pages anyone can open without an account. It stores no personal data: no seller names or IDs, no comments, no images. Rakuma's own terms prohibit scraping; you use this actor at your own risk and are responsible for how you use the data.

### FAQ

**Is this the sold price or the asking price?** Rakuma is fixed price, and a sold listing keeps the price it was listed at, so that is the price the item sold for unless the seller changed it before the sale.

**Why did my keyword return nothing?** Rakuma ignores words it does not know and shows unrelated items instead. The actor spots that when the result set is small and none of the titles mention your keyword, and returns "not found" without charging.

**Can I search in English?** Yes, but most titles are Japanese, so a Japanese keyword finds more. Brand names in Latin letters (supreme, nike) work.

**Why a residential proxy?** The shared datacenter proxy gets an HTTP 403 from the site; a Japanese residential address does not.

# Actor input Schema

## `searches` (type: `array`):

One search per line: keywords like "ポケモンカード" or "supreme", or paste a fril.jp search link (only its keywords are read; the link is never opened). Rakuma matches loosely, so a keyword it does not know is reported as not found. Accepted formats: ポケモンカード, supreme, https://fril.jp/s?query=nintendo+switch. You pay per listing returned; a search that finds nothing costs nothing.

## `mode` (type: `string`):

Sold shows what items sold for (each row is a sold listing with its last asking price; Rakuma publishes no sale date). On sale shows what is for sale now.

## `minPrice` (type: `integer`):

Only listings priced at or above this many yen. Leave empty for no lower limit.

## `maxPrice` (type: `integer`):

Only listings priced at or below this many yen. Leave empty for no upper limit.

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

Newest first is Rakuma's own newest-first order (use it for monitoring). Price orders sort the whole search by price. Relevance is the site's default.

## `maxItems` (type: `integer`):

Rakuma shows 40 listings per page; this actor pages automatically, one request per second, up to 1,000 per search. You pay per listing returned, so this is also your budget control.

## `includeCompsSummary` (type: `boolean`):

Off by default. When on, each search also returns one summary row: how many sold and on-sale listings were counted, their median prices in yen and the asking-vs-sold gap in %. It costs one extra request (the other feed's newest 40 listings) and is billed as one summary.

## `deltaMode` (type: `boolean`):

Remember each search between runs and mark every listing as new, price-drop, price-rise or unchanged. Use with a schedule and the newest-first order.

## `deltaName` (type: `string`):

Leave empty and one is derived from the mode and price limits. Type your own name to keep one memory across changes, or to run several independent watchlists.

## `alertOn` (type: `string`):

New listing: a listing not seen in an earlier run. Sold: an item that newly appears in the sold feed (mode Sold only). Price below: a new or price-dropped listing at or under your target price.

## `alertPriceBelowJpy` (type: `integer`):

Used only when Alert on is "Price at or below my target".

## `minPriceDropPct` (type: `integer`):

A price change smaller than this counts as unchanged.

## `alertOnChangeOnly` (type: `boolean`):

With monitoring on, return and bill only the listings that match "Alert on" (the first run, which has nothing to compare with, returns none). A summary row is still returned when you asked for one.

## `skipFirstRun` (type: `boolean`):

The first run of a watchlist has nothing to compare with. Turn this on to remember it without returning or billing anything, so alerts start from the second run.

## `notifyUrl` (type: `string`):

Optional. After a listing is billed, each alert is posted here as one message with title, price and a link (no image). Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot<token>/sendMessage?chat_id=<chat id>. Any other URL receives JSON. Messages are free, and a failed message never fails the run (the row's notifyErrors says why). The first run of a watchlist sends none. Stored encrypted, never logged or written to the results.

## `notifyFormat` (type: `string`):

Leave on 'Detect from the link': discord.com links get Discord messages, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON. Pick one only to override that.

## `maxNotificationsPerRun` (type: `integer`):

Up to 100. After this, one 'more alerts' message says the rest are in the run's dataset. 0 sends only that one message.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

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

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each listing found gets its own row. When off, one row per search carries its listings in the "rows" cell. You pay per listing returned either way.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## `proxyConfiguration` (type: `object`):

Apify Proxy config. Rakuma refuses the shared datacenter proxy (HTTP 403), so the default is the RESIDENTIAL proxy from Japan. Leave it as it is.

## Actor input object example

```json
{
  "searches": [
    "ポケモンカード"
  ],
  "mode": "sold",
  "sort": "newest",
  "maxItems": 40,
  "includeCompsSummary": false,
  "deltaMode": false,
  "deltaName": "",
  "alertOn": "new-listing",
  "minPriceDropPct": 5,
  "alertOnChangeOnly": false,
  "skipFirstRun": false,
  "notifyFormat": "auto",
  "maxNotificationsPerRun": 20,
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "rowType",
    "itemId",
    "url",
    "title",
    "priceJpy",
    "sold",
    "brand",
    "category",
    "categoryId",
    "checkedAt",
    "changeType",
    "previousPriceJpy",
    "priceDropPct",
    "isAlert",
    "isSummary",
    "searchMode",
    "totalAvailable",
    "listingsFetched",
    "truncated",
    "activeCount",
    "soldCount",
    "activeTotal",
    "soldTotal",
    "activeMedianPrice",
    "soldMedianPrice",
    "askVsSoldGapPct",
    "notifyErrors",
    "rows"
  ],
  "expandRows": true,
  "maxConcurrency": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "JP"
  }
}
```

# 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 = {
    "searches": [
        "ポケモンカード"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/rakuma-listing-lookup").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 = {
    "searches": ["ポケモンカード"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/rakuma-listing-lookup").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 '{
  "searches": [
    "ポケモンカード"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/rakuma-listing-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/rakuma-listing-lookup"
        }
    }
}
```

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/ZDVh3JDVR5gpBS1UT/builds/CsW0ljCn8X2wbqscV/openapi.json