# Carsensor Japan Used Car Scraper (Listings & Details) (`stone_jadex/carsensor-used-car-scraper`) Actor

Scrape public Carsensor (carsensor.net) Japan used-car list cards and optional detail pages into structured dataset rows: prices in JPY, mileage, shops, equipment, and pay-per-event pricing for list-row or detail-row exports.

- **URL**: https://apify.com/stone_jadex/carsensor-used-car-scraper.md
- **Developed by:** [Stone Jade](https://apify.com/stone_jadex) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## Carsensor Used Car Scraper

Carsensor Used Car Scraper gives Japanese used-car dealers and market researchers structured results from public pages. Start with Carsensor used-car list or detail URLs, or freeword keywords and export maker, model, total and base prices, mileage, year and shop location.

### What you can do

- Compare total payment and vehicle base prices in JPY for comparable cars, rather than treating them as the same amount.
- Use model year and mileage in kilometres to organize similar vehicles before comparing asking prices.
- Group cars by prefecture and city, and connect a listing to its public shop information for dealer research.

### Who uses it

- A used-car dealer can compare a model’s total price, year and mileage across prefectures to assess similar stock.
- A market researcher can enrich selected cars with equipment and public shop details to investigate why comparable listings differ.

### Result preview

**Illustrative only:** invented examples show the shape of the data; they are not real results. A dash indicates an unavailable value.

| Maker | Model | Total price | Base price | Year | Mileage | Prefecture |
| --- | --- | --- | --- | --- | --- | --- |
| Example | Hatchback | 1,200,000 JPY | 1,100,000 JPY | 2020 | 35,000 km | Tokyo |
| Example | Wagon | 1,800,000 JPY | 1,700,000 JPY | 2021 | 20,000 km | Osaka |
| Example | Hatchback | 950,000 JPY | 850,000 JPY | 2018 | 50,000 km | Kyoto |

Fields may be absent when the source does not publish them.

### Why choose this Actor

- Freeword searches, maker/model list URLs and direct detail URLs can be combined; duplicate car IDs are removed across inputs.
- List rows expose both total and base prices. Optional detail enrichment adds specifications and shop information; failed detail fetches retain the list row at the list event.

### Pricing

Prices in **USD**, verified on 4 November 2026. Check the current Pricing tab before running.

| Result type | Event price |
| --- | ---: |
| List car | $1.5 per 1,000 results |
| Car with details | $2.5 per 1,000 results |

The detail event replaces the list event for the same result; the two are not added together. For example, 1,000 results at the list car rate incur $1.5 in result-event charges. This calculation covers Actor event charges. Review Pricing for any separately listed platform usage; later access to stored data follows Apify's applicable storage pricing.

### Try it in three steps

1. Enter Carsensor used-car list or detail URLs, or freeword keywords. Set a small result limit for your first run.
2. Turn on **Include detail pages** for extra specifications and shop information, or leave it off for list results. Run the Actor.
3. Inspect the dataset and export the results in your preferred available format.

### Coverage and FAQ

**What are the limits?** A failed detail fetch retains the list row and uses the list event. Ended or missing direct listings can produce no row.

The requested result limit defaults to 100 and can be set up to 100,000 per run.

**Is this a live feed?** Each run is a snapshot of available source information. Listings, prices and other details may change after collection; a requested maximum is a ceiling, not a promise of that many results.

**Can I use the data for ongoing analysis?** Yes, export it to your own workflow. Scheduling repeated runs or acting on the exported results requires your own workflow.

# Changelog

This Actor's version history is a separate document: https://apify.com/stone_jadex/carsensor-used-car-scraper/changelog.md

# Actor input Schema

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

Carsensor used-car URLs under https://www.carsensor.net/usedcar/. List page URLs (maker/model index or freeword) are paginated as before. Detail page URLs (https://www.carsensor.net/usedcar/detail/AU…/ or …/index.html) are scraped directly, one detail row each, charged as detail-row (includeDetails not needed). List and detail URLs can be mixed; duplicates are deduped (detail URLs by carId, query/fragment ignored; a car from a detail URL is not repeated from a list). Malformed detail URLs (e.g. no AU… id) are skipped with a warning in OUTPUT.warnings; detail URLs that return 404 or an ended listing give no row and no charge, with a warning. Other hosts are rejected.

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

Search keywords turned into freeword list URLs (/usedcar/freeword/<encoded>/index.html). Prefer this over the robots-disallowed /usedcar/search.php.

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

Stop after this many unique car rows have been pushed (and charged under pay-per-event). Default 100; allowed range 1..100000.

## `maxPagesPerSearch` (type: `integer`):

Maximum list pages to fetch for each start URL / keyword search. Default 20; maximum 200.

## `includeDetails` (type: `boolean`):

When true, fetch each car detail page, merge extra fields (specs, shop phones shopTels and captionTels — numbers the shop wrote in photo captions — address, loan …), and charge detail-row instead of list-row. On detail fetch failure the list-level row is kept with detailError and charged as list-row.

## `requestIntervalSecs` (type: `number`):

Minimum seconds between HTTP requests (serial). Default 1. Raised automatically when robots.txt Crawl-delay is higher.

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

Apify proxy configuration. Default off (direct). When enabled, only datacenter proxy groups are used; the RESIDENTIAL group is ignored. Custom proxyUrls are your own and are used as given (not filtered).

## Actor input object example

```json
{
  "maxItems": 100,
  "maxPagesPerSearch": 20,
  "includeDetails": false,
  "requestIntervalSecs": 1,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Carsensor used-car rows saved in the default dataset. List-only runs contain list-card fields; runs with details merge the detail fields and add detailError on failed or ended detail pages.

## `summary` (type: `string`):

Run totals, charged events, request statistics, warnings, errors, and the reason the run stopped, stored in the OUTPUT key-value record.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("stone_jadex/carsensor-used-car-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("stone_jadex/carsensor-used-car-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 '{}' |
apify call stone_jadex/carsensor-used-car-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stone_jadex/carsensor-used-car-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/9liQfRmPC4RwfBLzm/builds/ufQpMIG2EJ2MqcUQ3/openapi.json