# DC Inside Scraper (`research_master/dc-inside-scraper`) Actor

Collect public posts and comment threads from major, minor, and mini DC Inside galleries by feed, gallery search, or direct URL, with nested or flat results and separate coverage audits.

- **URL**: https://apify.com/research\_master/dc-inside-scraper.md
- **Developed by:** [Research Master](https://apify.com/research_master) (community)
- **Categories:** AI, Automation, Social media
- **Stats:** 2 total users, 1 monthly users, 71.4% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.20 / 1,000 dc inside post collecteds

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?

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

## DC Inside Scraper

Collect public posts and comment threads from Korean DC Inside galleries with auditable page and run coverage.

### Why choose this Actor

This Actor is designed for research and VOC workflows that need more than a sample of recent post titles.

| Capability | This Actor | Deprecated Store alternative | Typical single-page scraper |
| --- | --- | --- | --- |
| Major galleries | Yes | No | Sometimes |
| Minor galleries | Yes | Yes | Sometimes |
| Mini galleries | Yes | No | Rarely |
| Search inside selected galleries | Yes | No | Rarely |
| Direct post and list URLs | Yes | Yes | Varies |
| Comment pagination and reply depth | Yes | Yes | Often incomplete |
| Nested and flat analysis outputs | Yes | Yes | Usually one format |
| Korea residential proxy default | Yes | Proxy support only | Varies |
| Page and run coverage audits | KVS records | Not documented | No |
| Default memory | 512 MB | 4096 MB | Varies |

The existing `rafazafar/gall-dcinside-scraper` Store Actor was marked deprecated and under maintenance when this Actor was created. It targets minor galleries and does not document gallery search or explicit coverage audits.

### Recommended uses

- Korean consumer and product VOC from known DC Inside galleries
- Monitoring recent or recommended posts in selected communities
- Collecting full public discussion context for text analysis
- Exporting flat post/comment rows to CSV or BI tools
- Reproducible research that needs page-level failures and collection totals

### Do not use it for

- Estimating nationally representative public opinion from DC Inside alone
- Private, deleted, login-only, or age-gated content
- Writing posts, voting, logging in, or collecting account-only data
- Discovering every relevant Gallery from a broad topic; provide the Gallery IDs or URLs first
- Guaranteed historical completeness beyond the page, date, and result limits you set

DC Inside can block data-center or non-Korean traffic. The default proxy setting uses a sticky Korean residential session. Proxy availability and traffic charges depend on the Apify account running the Actor.

### Input

Provide at least one of:

- `startUrls`: DC Inside list or post URLs
- `galleryIds`: Gallery IDs such as `programming`, combined with `galleryType`

The Console form is prefilled with a bounded one-post `programming` Gallery run so Apify's automated quality test has a valid target and can finish within its five-minute limit. These prefill values do not replace the runtime defaults used by API calls, Schedules, or existing Saved Tasks.

Useful controls:

| Field | Default | Purpose |
| --- | --- | --- |
| `searchQueries` | empty | Search title and body inside every Gallery target |
| `sort` | `latest` | Use latest or recommended Gallery feed |
| `dateFrom`, `dateTo` | empty | Keep posts inside a KST date window |
| `maxPosts` | `20` | Global unique-post limit |
| `maxPagesPerTarget` | `10` | Hard page limit for each Gallery feed or search |
| `scrapeComments` | `true` | Fetch public comments and replies |
| `maxCommentsPerPost` | `100` | Per-post comment limit; `0` requests all accessible pages |
| `outputFormat` | `nested` | `nested`, `flat`, or `postsOnly` |
| `includeHtml` | `false` | Preserve post body HTML in addition to plain text |
| `proxyConfiguration` | Korean residential | Apify Proxy or custom proxy configuration |
| `maxConcurrency` | `2` | Concurrent post workers |
| `requestDelayMs` | `700` | Delay between requests from a worker |

#### Gallery search example

```json
{
  "galleryIds": ["programming"],
  "galleryType": "major",
  "searchQueries": ["AI"],
  "sort": "latest",
  "dateFrom": "2026-08-01",
  "maxPosts": 20,
  "maxPagesPerTarget": 3,
  "scrapeComments": true,
  "maxCommentsPerPost": 100,
  "outputFormat": "nested"
}
```

#### Direct post example

```json
{
  "startUrls": [
    {
      "url": "https://gall.dcinside.com/board/view/?id=programming&no=1847628"
    }
  ],
  "maxPosts": 1,
  "scrapeComments": true,
  "maxCommentsPerPost": 20,
  "outputFormat": "flat"
}
```

### Dataset output

Every Dataset row has a stable `record_type`:

- `post`: one successfully parsed public post
- `comment`: emitted only in `flat` mode

Important post fields include:

```json
{
  "record_type": "post",
  "source": "dcinside",
  "gallery_id": "programming",
  "gallery_type": "major",
  "post_id": "1847628",
  "url": "https://gall.dcinside.com/board/view/?id=programming&no=1847628",
  "title": "Post title",
  "body_text": "Post body",
  "author_name": "Displayed nickname",
  "author_id": null,
  "author_ip": "Displayed IP fragment",
  "created_at": "2026-08-24T14:30:25+09:00",
  "view_count": 100,
  "recommendation_count": 5,
  "comment_count": 2,
  "media_urls": [],
  "comments": [],
  "comments_collected": 2,
  "comments_complete": true,
  "matched_query": "AI",
  "source_list_url": "https://gall.dcinside.com/board/lists/?id=programming&page=1",
  "scraped_at": "2026-08-24T06:00:00.000Z"
}
```

In `nested` mode, `comments` contains comment IDs, parent IDs, reply depth, public author fields, text, timestamps, and media URLs. In `flat` mode, the post row has an empty `comments` array and each comment is a separate Dataset row.

### Audit records

Audits are deliberately kept out of the default Dataset:

- `PAGE_AUDITS`: sanitized request and parser status for list, post, and comment pages
- `RUN_AUDIT`: input summary, target/page/post counts, comment coverage, failures, and completion status

This separation keeps Dataset exports analysis-ready and prevents audit rows from being confused with business results if result-based pricing is configured later.

### Pay-per-event integration

The source code uses two custom event names:

- `post`: one successfully saved post
- `comment`: one successfully saved or nested public comment/reply

Post events are charged through the durable post Dataset write. Flat comment events are charged through their Dataset writes; nested comment events are charged only after the containing post has been saved. `RUN_AUDIT.charging` records attempted and charged counts for both events plus whether the run reached its spending limit.

When enabling pay-per-event pricing in Apify Console, configure both custom events and remove `apify-default-dataset-item`. Keeping the synthetic Dataset event would charge flat comment rows twice and make nested and flat output prices inconsistent. Page requests, retries, failures, `PAGE_AUDITS`, and `RUN_AUDIT` are never custom charge events.

### Coverage interpretation

- `complete_for_requested_pages`: all requested pages finished without recorded failures
- `limited_by_max_posts`: collection stopped at the requested global post limit
- `partial`: one or more target, post, or comment requests failed
- `failed`: no posts were saved and the run recorded failures

A successful HTTP response is not enough: a post is saved only after the expected DC Inside detail selectors are present and parsed.

### Responsible collection

Only public page content is collected. Use conservative limits and delays, follow applicable laws and DC Inside terms, and avoid redistributing personal data. Displayed nicknames, user IDs, and partial IP strings are public page fields but may still be personal data in your jurisdiction.

### Local development

```bash
npm install
npm test
npm run check
apify run
```

The project uses HTTP requests and Cheerio rather than a browser. Comments are requested from DC Inside's public JSON endpoint, with a mobile endpoint fallback.

# Actor input Schema

## `startUrls` (type: `array`):

Add public gall.dcinside.com list or post URLs. List URLs are paginated; direct post URLs are collected once.

## `galleryIds` (type: `array`):

Add gallery IDs without a URL, such as programming. The selected gallery type below is applied to every ID.

## `galleryType` (type: `string`):

Choose the URL family used for gallery IDs. Full URLs above determine their own type.

## `searchQueries` (type: `array`):

Search post titles and bodies within each gallery. Direct post URLs ignore this setting.

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

Collect the latest feed or the gallery's recommended-post feed.

## `dateFrom` (type: `string`):

Keep posts on or after this date.

## `dateTo` (type: `string`):

Keep posts on or before this date.

## `maxPosts` (type: `integer`):

Maximum unique posts saved across the whole run.

## `startPage` (type: `integer`):

First page number for gallery-list targets.

## `maxPagesPerTarget` (type: `integer`):

Hard pagination limit for each gallery feed or gallery search.

## `scrapeComments` (type: `boolean`):

Collect public comments and replies for each successfully parsed post.

## `maxCommentsPerPost` (type: `integer`):

Stop after this many comments per post. Use 0 for all available comments.

## `outputFormat` (type: `string`):

Nested saves one row per post with comments inside. Flat saves one post row plus one row per collected comment. Posts only skips comments.

## `includeHtml` (type: `boolean`):

Keep sanitized inner HTML alongside plain text for downstream media or formatting analysis.

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

Use Apify Proxy or your own proxy URLs. Disabling the proxy may cause timeouts or blocked pages.

## `requestDelayMs` (type: `integer`):

Minimum pause between requests from each worker.

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

Lower concurrency is gentler and often more reliable on DC Inside.

## `requestTimeoutSecs` (type: `integer`):

Maximum time for one HTTP request before retrying.

## `maxRetries` (type: `integer`):

Retry blocked, timed out, or server-error responses with a fresh proxy session.

## `debugMode` (type: `boolean`):

Log sanitized request and parser diagnostics without response bodies or credentials.

## Actor input object example

```json
{
  "galleryIds": [
    "programming"
  ],
  "galleryType": "major",
  "sort": "recommended",
  "maxPosts": 1,
  "startPage": 1,
  "maxPagesPerTarget": 1,
  "scrapeComments": true,
  "maxCommentsPerPost": 3,
  "outputFormat": "nested",
  "includeHtml": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "KR"
  },
  "requestDelayMs": 700,
  "maxConcurrency": 1,
  "requestTimeoutSecs": 45,
  "maxRetries": 3,
  "debugMode": false
}
```

# Actor output Schema

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

Default dataset containing successfully parsed public posts and, in flat mode, comment records.

## `pageAudits` (type: `string`):

Listing, post, and comment request audit records stored in the default key-value store.

## `runAudit` (type: `string`):

Run totals, coverage status, and failures stored in the default key-value store.

# 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 = {
    "galleryIds": [
        "programming"
    ],
    "sort": "recommended",
    "maxPosts": 1,
    "maxPagesPerTarget": 1,
    "maxCommentsPerPost": 3,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "KR"
    },
    "maxConcurrency": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("research_master/dc-inside-scraper").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 = {
    "galleryIds": ["programming"],
    "sort": "recommended",
    "maxPosts": 1,
    "maxPagesPerTarget": 1,
    "maxCommentsPerPost": 3,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "KR",
    },
    "maxConcurrency": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("research_master/dc-inside-scraper").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 '{
  "galleryIds": [
    "programming"
  ],
  "sort": "recommended",
  "maxPosts": 1,
  "maxPagesPerTarget": 1,
  "maxCommentsPerPost": 3,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "KR"
  },
  "maxConcurrency": 1
}' |
apify call research_master/dc-inside-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,research_master/dc-inside-scraper"
        }
    }
}

```

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/9bUGBHPKLuNK3hRz2/builds/oPQxOh8bAyh5drexP/openapi.json