# CarSensor Japan Used Cars (カーセンサー) Scraper (`ardent_fork/carsensor-japan-used-cars`) Actor

Dealer-stock used cars from carsensor.net by maker, model and prefecture: total and vehicle price, year, mileage, repair history, inspection, warranty, transmission, dealer name and location, full detail specs. No login, no API key.

- **URL**: https://apify.com/ardent\_fork/carsensor-japan-used-cars.md
- **Developed by:** [KF P](https://apify.com/ardent_fork) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 50.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 cars

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?

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

## CarSensor Japan Used Cars (カーセンサー) Scraper

Pulls dealer-stock used-car listings from **carsensor.net**, Recruit's used-car marketplace and one of the two largest in Japan (≈500,000 cars). Filter by maker, model and prefecture; get every list-page field and, optionally, the full detail page (fees, specs, warranty and maintenance text, dealer comment, images). No login, no API key.

Who uses this: used-car exporters and parallel importers pricing against Japanese dealer stock, valuation and price-index vendors, dealers benchmarking competitors, and analysts tracking JDM supply by model and region.

### Input

| field | type | notes |
|---|---|---|
| `brand` | string, required | 2-letter maker code from `https://www.carsensor.net/usedcar/b<CODE>/`: `TO` Toyota, `HO` Honda, `NI` Nissan, `MA` Mazda, `SB` Subaru, `SU` Suzuki, `DA` Daihatsu, `MI` Mitsubishi, `LE` Lexus, `ME` Mercedes-Benz, `BM` BMW, `VW` Volkswagen, `AU` Audi, `PO` Porsche … |
| `model` | string | Model code, the `s<code>` segment of a model URL (`/usedcar/bTO/s230/` → `230`, Pixis Epoch). `s230` is accepted too. Codes are in the model menu of any maker page. |
| `prefecture` | string | Romanised URL slug: `tokyo`, `kanagawa`, `osaka`, `aichi`, `hokkaido`, `fukuoka` … (the site spells `kouchi`, `ooita`). Regions work: `hokkaido`, `tohoku`, `kanto`, `koshinetsu`, `tokai`, `kansai`, `chugoku`, `shikoku`, `kyushu`. |
| `maxItems` | integer | Stop after this many cars (default 100, max 30,000). |
| `fetchDetails` | boolean | Open each car's detail page (default `true`). Off = list data only, ~30 cars per request. |
| `maxConcurrency` | integer | Parallel requests, 1–20 (default 5). |
| `proxyConfiguration` | object | Optional; the site answers plain requests. |

Example: `{ "brand": "TO", "model": "230", "prefecture": "kanto", "maxItems": 200 }`

### Output (one record per car)

From the list page: `id` (AU…), `url`, `brand`, `title`, `subText` (dealer's one-line pitch), `bodyType`, `color` (short), `totalPriceYen` (支払総額, all-in), `basePriceYen` (車両本体価格), `planPrices` (A/B プラン totals), `monthlyLoanYen`, `year` + `yearJp` (2022 / R04), `mileageKm`, `inspection` (車検), `repairHistory` / `hasRepairHistory` (修復歴), `warranty`, `maintenance`, `displacementCc`, `transmission`, `labels` (360°画像付, 車両品質評価書付, 販売店保証 …), `prefecture`, `city`, `shopName`, `shopUrl`, `shopReviewScore`, `imageUrl`.

Added by the detail page: `name`, `expensesYen` (諸費用), `warrantyDetail`, `maintenanceDetail`, `oneOwner`, `nonSmoking`, `serviceRecords`, `unregisteredNew`, `driveType`, `colorName`, `steering`, `seats`, `fuel`, `doors`, `shopComment`, `images` (main photo from the page's structured data; the gallery is JS-loaded), and `specs` — every row of the 基本情報 / 車両詳細 / 型式スペック tables as Japanese key → text (wheelbase, dimensions, weight, fuel economy, chassis-number tail, …).

Prices are integers in yen (the site shows 万円: 59.9万円 → 599000). `null` means the site did not show the value (e.g. 応談 = negotiable).

### Pricing

Pay per event: one `car` event per record pushed. Set a maximum total charge on the run to cap spend; the actor stops cleanly at the budget or at `maxItems`, whichever comes first, and never charges for a car twice — even across migrations and restarts.

### Notes and limits

- The site lists 32 cassettes per page, of which 1–2 are lease ads (`/usedcar/lease/`); those are skipped, so pages yield ~30 cars.
- Prefecture-filtered lists show a site-side count that tops out at 2,000; a maker-wide list (e.g. Toyota, ~118,000 cars) paginates much deeper. Narrow by model or prefecture for exhaustive pulls.
- Past the last page the site serves page 1 again; the actor detects this from the pager and stops.
- An unknown maker code fails the run immediately; an unknown model or prefecture path yields the site's empty list.
- Sold or removed cars answer 404 on the detail page and are skipped without charge.
- Keep concurrency modest; the actor sends plain GET requests with no proxy by default.

### Terms

carsensor.net is a public site; the actor reads only pages that are visible without an account and respects `robots.txt` (no `Disallow`). The site's 利用規約 (car-t-1008) forbids obstructing the service's operation; the default concurrency of 5 keeps load light. Data is collected for the user's own analysis; dealer names and phone numbers shown on the site are business, not personal, information. Use of the data remains the user's responsibility.

# Actor input Schema

## `brand` (type: `string`):

2-letter CarSensor maker code from the URL https://www.carsensor.net/usedcar/b<CODE>/ — TO Toyota, HO Honda, NI Nissan, MA Mazda, SB Subaru, SU Suzuki, DA Daihatsu, MI Mitsubishi, LE Lexus, ME Mercedes-Benz, BM BMW, VW Volkswagen, AU Audi, PO Porsche.

## `model` (type: `string`):

Optional model code, the s<code> segment of a model URL such as https://www.carsensor.net/usedcar/bTO/s230/ (230 = Pixis Epoch). Enter 230 or s230. Find codes in the model menu on any maker page.

## `prefecture` (type: `string`):

Optional romanised prefecture slug from the URL, e.g. tokyo, kanagawa, osaka, aichi, hokkaido, fukuoka (the site spells kouchi and ooita); regions work too: hokkaido, tohoku, kanto, koshinetsu, tokai, kansai, chugoku, shikoku, kyushu.

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

Stop after this many cars (default 100, max 30000). Each pushed car is one pay-per-event charge.

## `fetchDetails` (type: `boolean`):

Open every car's detail page for fees, full specs (drive, fuel, doors, seats, color name, one-owner, non-smoking …), warranty and maintenance text, dealer comment and images. Off = list data only (about 30 cars per request, much faster).

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

Parallel requests (1–20). Keep it modest; the site is a plain SSR site with no API.

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

Optional. The site answers plain requests; use a proxy only if your runs get blocked.

## Actor input object example

```json
{
  "brand": "TO",
  "model": "230",
  "prefecture": "tokyo",
  "maxItems": 100,
  "fetchDetails": true,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `items` (type: `string`):

Dataset items, one per used car (prices, year, mileage, repair history, inspection, dealer).

# 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 = {
    "brand": "TO"
};

// Run the Actor and wait for it to finish
const run = await client.actor("ardent_fork/carsensor-japan-used-cars").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 = { "brand": "TO" }

# Run the Actor and wait for it to finish
run = client.actor("ardent_fork/carsensor-japan-used-cars").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 '{
  "brand": "TO"
}' |
apify call ardent_fork/carsensor-japan-used-cars --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ardent_fork/carsensor-japan-used-cars"
        }
    }
}

```

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/6ETBJqWdJh5wcQgtU/builds/KcUduO8g7I7pDtt1M/openapi.json