# Qiita + Zenn Tech Article Scraper (Japan) (`morikuma/qiita-zenn-tech-corpus`) Actor

Collect Japanese technical articles from Qiita and Zenn by tag, keyword or user. Markdown/plain-text bodies, tags, likes, authors — ready for RAG, fine-tuning, dev-trend research and content ideation. Pay per article.

- **URL**: https://apify.com/morikuma/qiita-zenn-tech-corpus.md
- **Developed by:** [yuuki mori](https://apify.com/morikuma) (community)
- **Categories:** Developer tools, AI
- **Stats:** 3 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 article (with body)s

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

## Qiita + Zenn Tech Article Scraper (Japanese developer corpus)

Collects Japanese technical articles from **[Qiita](https://qiita.com)** and **[Zenn](https://zenn.dev)** — the two largest developer knowledge-sharing platforms in Japan — and returns them as clean JSON with **Markdown / plain-text bodies**. Built for Japanese **LLM datasets (RAG, fine-tuning, evaluation)**, developer-trend research and content ideation.

### What you get

| Field | Description |
|---|---|
| `platform` | `qiita` or `zenn` |
| `title`, `url`, `id` / `slug` | Article identity |
| `author`, `authorName`, `publication` | Author (and Zenn publication if any) |
| `publishedAt`, `updatedAt` | ISO 8601 |
| `likes`, `stocks` / `bookmarks`, `comments` | Engagement metrics — use `minLikes` as a quality filter |
| `tags` | Qiita tags / Zenn topics |
| `bodyMarkdown` (Qiita) / `bodyText` (Zenn) | Full body. Qiita returns the author's original Markdown; Zenn body is converted to plain text preserving headings and code blocks |
| `bodyLength`, `articleType`, `emoji` | Extras |

### Input

- **Tags / topics** — e.g. `claude`, `python`, `nextjs`, `生成AI`. Applied to both platforms.
- **Keywords** (Qiita only) — free-text search in title/body.
- **User names** — pull everything an author published.
- **Minimum likes** / **Published after** — dataset quality and recency filters. Filtering happens *before* charging, so you don't pay for skipped articles.
- **Include body** — turn off for metadata-only crawls (cheaper).
- **Qiita access token** (optional) — raises the Qiita API limit from 60 to 1,000 requests/hour (each request fetches up to 100 articles).

### Pricing (pay per event)

- **Article (with body)** — full body + metadata.
- **Article (metadata only)** — title, URL, author, tags, likes, dates.

The Apify free plan is enough to try it.

### Use cases

- **Japanese RAG / fine-tuning corpora** — e.g. "all Qiita + Zenn articles tagged `claude` with ≥ 20 likes since 2025" in one run.
- **Developer trend research** — which frameworks / tools are Japanese engineers writing about this month?
- **Content ideation for tech blogs & YouTube** — find high-engagement topics and gaps.
- **Competitive intelligence for dev-tool vendors** — track how your product and competitors are discussed in Japan.

### Example output

```json
{
  "platform": "zenn",
  "title": "Claude Codeで実行してほしくないコマンドには代替手段を伝える",
  "url": "https://zenn.dev/example/articles/abc123",
  "author": "example",
  "publishedAt": "2026-09-14T10:00:00.000+09:00",
  "likes": 42,
  "tags": ["Claude", "ClaudeCode", "AI"],
  "bodyText": "## はじめに\nClaude Code の設定で…",
  "bodyLength": 5102
}
```

### Notes

- Qiita is accessed through its official public API; Zenn through its public JSON endpoints and server-rendered article pages, at low request rates.
- Article content belongs to its authors. Use the data in accordance with each platform's terms and Japanese copyright law (research, analysis and internal RAG use are typical).
- See also: **PR TIMES Press Release Scraper** by the same developer for Japanese business news.

# Actor input Schema

## `platforms` (type: `array`):

Which platforms to collect from.

## `tags` (type: `array`):

Qiita tags / Zenn topics, e.g. claude, python, react, 生成AI. Case-insensitive.

## `keywords` (type: `array`):

Free-text search on Qiita (title/body). Zenn has no public keyword search API.

## `users` (type: `array`):

Qiita user IDs / Zenn usernames to collect all articles from.

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

Stop after this many articles (total).

## `minLikes` (type: `integer`):

Skip articles with fewer likes (quality filter for datasets).

## `publishedAfter` (type: `string`):

Skip articles published before this date (YYYY-MM-DD).

## `includeBody` (type: `boolean`):

Include full article body (Markdown for Qiita, plain text for Zenn). Turn off for metadata only (cheaper).

## `qiitaToken` (type: `string`):

Raises the Qiita API limit from 60 to 1,000 requests/hour. Create at https://qiita.com/settings/applications (read_qiita scope).

## Actor input object example

```json
{
  "platforms": [
    "qiita",
    "zenn"
  ],
  "tags": [
    "claude"
  ],
  "keywords": [],
  "users": [],
  "maxItems": 100,
  "minLikes": 0,
  "includeBody": true
}
```

# Actor output Schema

## `articles` (type: `string`):

JSON array of articles: platform, title, url, author, publishedAt, likes, tags, bodyMarkdown (Qiita) / bodyText (Zenn).

## `articlesCsv` (type: `string`):

Same data as CSV.

# 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 = {
    "tags": [
        "claude"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("morikuma/qiita-zenn-tech-corpus").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 = { "tags": ["claude"] }

# Run the Actor and wait for it to finish
run = client.actor("morikuma/qiita-zenn-tech-corpus").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 '{
  "tags": [
    "claude"
  ]
}' |
apify call morikuma/qiita-zenn-tech-corpus --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,morikuma/qiita-zenn-tech-corpus"
        }
    }
}
```

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/NJ1l8kUGW1Cx8ccsJ/builds/1ITYFTIcFbCXlDbea/openapi.json