# Hifido Japan Used Audio — What It Actually Sold For (`jpmarketdata/hifido-japan-audio-sold-comps`) Actor

Type a model like Accuphase E-460 and see what it actually sold for at Hifido in Japan, from ten years of sold records. You get the typical sold price and range in yen, how many sold, the original list price and what share of it holds. $0.02 per model, no results = no charge. Unofficial.

- **URL**: https://apify.com/jpmarketdata/hifido-japan-audio-sold-comps.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** E-commerce, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 model analyzeds

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

## Hifido Japan Used Audio — What It Actually Sold For

> **Unofficial** — independent tool, **not affiliated with, endorsed by, or sponsored by Hifido**. It reads only publicly visible pages. Support, reliability guarantees and the full disclaimer are at the bottom of this page.

**What it does:** Type a model like `Accuphase E-460` and get what Hifido Japan really sold it for, from ten years of sold records — not today's asking prices.

**You enter:** A model number, plus one of Hifido's audio sections. Example: `Accuphase E-460` in all audio.

**You get:** One row — how many actually sold, typical sold price and lowest–highest in yen, the original Japanese list price and the share of it the model still holds, warranty mix, arrival years, which branches sold them, and how many are in stock today.

**Price:** $0.02 per model. No results = no charge. +$0.002 per unit row if you also want the individual units (off by default).

**Example:** enter `Accuphase E-460` → 13 units actually sold · typical ¥398,000 · range ¥328,000–420,000 · 82.9 percent of the ¥480,000 list price · 95 of the 108 rows dropped as other models · 0 in stock right now (real run, 2026-09-10)

> Unofficial — not affiliated with Hifido. Reads public pages only.

### Why sold prices are the point here

Every other used-audio tool can tell you what a shop is *asking* today. Hifido keeps its sold units on the public site — 43,436 of them for the last ten years, and a keyword search reaches back further — with the price each one actually sold for.

The `Accuphase E-460` measured on 2026-09-10 is the case in one line: **0 units in stock**, and **13 units that really sold**, typical ¥398,000. Asking prices had nothing to say about that model that day. Thirteen transactions did.

### Why the share of list price is unusual

The same record carries the maker's original Japanese list price, so this tool can say what share of it a model still holds — `residualShare`. The E-460 held **82.9 percent** of a ¥480,000 list price.

It is computed unit by unit (each unit against its own list price), then the middle value of those, because a model's list price often changes during its life: eleven of those thirteen units list at ¥480,000 and two at ¥504,000, from a consumption-tax change. **A unit with no list price on file is left out rather than guessed at**, and `residualShare.coverage` says how much of the model that leaves — `1.0` means every unit had one.

### Why 95 of 108 rows are thrown away

Hifido's search also reads the description text. `Accuphase E-460` returns **108** rows, and only **13** of them are an E-460 — the rest are option boards (AD-30, DAC-40, AD-50 …) whose descriptions mention the E-460, priced from ¥29,800. Put those in the middle of a ¥400,000 amplifier and the answer is off by a factor of seven.

So every figure here comes from units whose **own model line** is the model you asked for. `looseMatchDropped` says how many rows were thrown away, and `otherModelsInResults` names what they were — useful in its own right when you searched a maker name and want to know which models came back.

The match is exact, not "contains": `SP-LE8T mk2` is a different speaker from `SP-LE8T` and is not priced as one.

### What this cannot tell you

- **When a unit sold.** Hifido publishes the arrival timestamp and no sale date at all. So there is no days-to-sell and no days-on-shelf anywhere in the output. `arrivalYearMix` counts arrivals, which is a record of how many units the shop handled each year, not how fast they moved.
- **The final amount someone paid.** These are the shop's fixed retail prices for units that sold. Anything negotiated at the counter is not public.
- **A typical price for a search too wide to read.** The sold archive comes back in an order Hifido does not publish and ignores every sort setting, so pricing only the first pages would report that order rather than the market. When a search is wider than the pages setting, `priceBasis` switches to `price-ladder`: the prices then come from the shop's own counts per price band and cover **every unit the search matched**, not one model, and the per-model fields are left empty rather than computed off an arbitrary first page. Search the model number instead of the maker, or narrow the section.

### Output

One row per run, plus one row per unit when the unit list is on.

`Measured on 2026-09-10 (real run, model "Accuphase E-460", section "2")`

```json
{
  "type": "audio_sold_comps",
  "model": "Accuphase E-460",
  "genre": "2",
  "genreLabel": "All audio equipment",
  "status": "ok",
  "keywordMatches": 108,
  "itemsRead": 108,
  "pagesRead": 4,
  "looseMatchDropped": 95,
  "otherModelsInResults": [
    {
      "model": "AD-30",
      "units": 33
    },
    {
      "model": "DAC-40",
      "units": 23
    },
    {
      "model": "AD-50",
      "units": 17
    },
    "... 4 more model numbers"
  ],
  "soldCount": 13,
  "soldPriceJpy": {
    "min": 328000,
    "p25": 368000,
    "median": 398000,
    "p75": 398000,
    "max": 420000,
    "average": 380615
  },
  "priceBasis": "full-scan",
  "listPriceJpy": {
    "min": 480000,
    "p25": 480000,
    "median": 480000,
    "p75": 480000,
    "max": 504000,
    "average": 483692
  },
  "residualShare": {
    "median": 0.8292,
    "p25": 0.7458,
    "p75": 0.8292,
    "unitsWithListPrice": 13,
    "coverage": 1.0
  },
  "warrantyGradeMix": [
    {
      "grade": "2-year warranty",
      "labelJapanese": "２年保証",
      "units": 0
    },
    {
      "grade": "warranty",
      "labelJapanese": "保証",
      "units": 13
    },
    {
      "grade": "sold as-is",
      "labelJapanese": "現状品",
      "units": 0
    },
    {
      "grade": "junk",
      "labelJapanese": "ジャンク品",
      "units": 0
    },
    {
      "grade": "not stated",
      "labelJapanese": "表記なし",
      "units": 0
    }
  ],
  "arrivalYearMix": [
    {
      "arrivalYear": 2011,
      "units": 1
    },
    {
      "arrivalYear": 2013,
      "units": 1
    },
    "... 2016, 2017 (4 units), 2018, 2019, 2020, 2023"
  ],
  "shopBreakdown": [
    {
      "shop": "大須本店",
      "units": 5
    },
    {
      "shop": "日本橋店",
      "units": 5
    },
    {
      "shop": "秋葉原店",
      "units": 2
    },
    {
      "shop": "京都店",
      "units": 1
    }
  ],
  "maker": "Accuphase",
  "makerCountry": "Japan",
  "makerCountryCode": "22",
  "releaseYear": 2010,
  "inStockNow": 0,
  "inStockAskJpy": {
    "min": null,
    "p25": null,
    "median": null,
    "p75": null,
    "max": null,
    "average": null
  },
  "askVsSoldMedianShare": null,
  "resultCountCheck": "ok",
  "arrivalYearCheck": "ok",
  "hint": null,
  "sourceUrls": [
    "https://www.hifido.co.jp/sold/?KW=Accuphase+E-460&G=2&P1=&P2=&A=10&N=&Y=&CT=0&LNG=J&OD=0&SD1=0&O=0&L=30",
    "https://www.hifido.co.jp/?KW=Accuphase+E-460&G=2&P1=&P2=&A=10&N=&Y=&CT=0&LNG=J&OD=0&SD1=0&O=0&L=30"
  ],
  "requestsUsed": 5,
  "fetchedAt": "2026-09-10T04:16:52+00:00"
}
```

Some fields worth knowing:

| Field | What it is |
|---|---|
| `soldCount` | Units of this model that actually sold. Empty under `price-ladder`, where not every page was read. |
| `keywordMatches` | What Hifido's own search matched, description hits included — always at least `soldCount`. |
| `priceBasis` | `full-scan` = every page read, prices measured unit by unit. `price-ladder` = the shop's counts per price band, covering the whole search. |
| `residualShare` | Share of the original list price, per unit, with the share of units that had a list price. |
| `looseMatchDropped` | Rows read whose own model line is a different model. |
| `resultCountCheck` | `ok` when the pages delivered exactly as many rows as Hifido said it had. |
| `arrivalYearCheck` | A Hifido product code starts with its arrival year, so each row states its year twice. `ok` when the two agree. |
| `askVsSoldMedianShare` | Today's asking price against the sold price: `0.1` means stock is 10 percent above what the model has been selling for. Empty when either side is missing. |

### Input

| Field | Default | What it changes |
|---|---|---|
| `model` | `Accuphase E-460` | The model, as the shop prints it. The maker may be in front. |
| `genre` | `2` (all audio equipment) | Which section to look in: 51 audio sections, plus two that cover everything. Narrowing it is how a wide search fits in the pages below. |
| `includeItems` | `false` | Also return one row per matching unit, at $0.002 each. |
| `maxPages` | `4` | Pages read, 30 units a page, up to 6. Beyond that the run switches to `price-ladder`. |

### How it reads the site

Two server-rendered pages, `www.hifido.co.jp/` for current stock and `www.hifido.co.jp/sold/` for the sold archive. No login, no cookie, no browser. `www` only — the shop's staging host is publicly reachable but is never addressed here.

Hifido's robots.txt allows everything and asks for no delay between requests, and the site publishes no terms of use, so the restraint is this tool's own: **3 seconds between calls and at most 16 calls in a whole run**, neither reachable from the input. A default run makes 5.

Item descriptions are not read at all. They end with the name of the staff member who wrote them, and no output field here contains a person.

### If something goes wrong

- **Wrong number or a failed run?** Open a ticket on the **Issues** tab. I read every one and reply within 2 business days (Japan time).
- **You never get a fake "empty" result.** If the site can't be read, the run fails and says so.
- **No results = no charge.** You only pay for results you actually get.
- **Checked every week.** An automatic test runs this tool weekly; if the site changes, I fix it.
- **Public pages only.** No login, no personal data, and it goes easy on the site.

### More tools by the same author

- [Mercari Japan Sold Prices — What Items Really Sell For](https://apify.com/jpmarketdata/mercari-japan-price-checker)
- [Yahoo! Auctions Japan Sold Prices — Median, Range, Bids](https://apify.com/jpmarketdata/yahoo-auction-sold-comps)
- [Daikokuya Japan Buyback — What a Shop Actually Paid](https://apify.com/jpmarketdata/daikokuya-japan-brand-buyback-checker)
- [Japan Used Camera & Lens — Dealer Price vs Sold Price](https://apify.com/jpmarketdata/japan-camera-gear-sold-comps)
- [Japan Figure & Gunpla — New Price vs Used Sold Price](https://apify.com/jpmarketdata/japan-figure-gunpla-resale-value)
- [Used iPhone & Android Prices Japan — Dealer vs Sold](https://apify.com/jpmarketdata/japan-phone-resale-value)
- [Yahoo, Mercari & PayPay Japan — Same Item, 3 Prices](https://apify.com/jpmarketdata/japan-resale-cross-market-checker)
- [Mercari & Yahoo Japan Demand — Sold vs Still Listed](https://apify.com/jpmarketdata/japan-sell-through-rate)

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): <https://apify.com/jpmarketdata>

### Disclaimer

Unofficial, independent tool — **not affiliated with, endorsed by, or sponsored by Hifido**. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.

# Actor input Schema

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

The model as Hifido prints it on the product line: `E-460`, `SP-LE8T`, or with the maker in front, `Accuphase E-460`. Every figure is measured over units whose own model line is this model. Hifido's search also reads description text, so units that merely mention it go to `looseMatchDropped` and stay out of the prices. One run is one model, a flat $0.02; nothing sold is not charged.

## `genre` (type: `string`):

Which of Hifido's audio sections to look in. `2` covers all audio equipment. Picking one section drops units that merely share the word, which lowers the counts and can move the typical price. It also decides whether a wide search fits in the pages below: a maker name across all audio can match thousands of units, and one section brings it under that. Charging is unchanged.

## `includeItems` (type: `boolean`):

Off by default: a run costs a flat $0.02 for the summary. Turn it on to also get one row per unit that matched your model — sold price in yen, original Japanese list price, warranty, branch, arrival date, link — at +$0.002 per row. The rows are the units already read for the summary, so this adds rows, not waiting. At most 180 sold rows plus 30 units in stock now.

## `maxPages` (type: `integer`):

How much of the search this run reads, 30 units a page. Hifido returns sold records in an order it does not publish, so prices are measured unit by unit only when every page was read. When the search is wider, `priceBasis` switches to `price-ladder` and the prices cover every unit the search matched, not one model. It also caps the rows charged at $0.002 each when the list above is on: 30 a page.

## Actor input object example

```json
{
  "model": "Accuphase E-460",
  "genre": "2",
  "includeItems": false,
  "maxPages": 4
}
```

# Actor output Schema

## `soldPriceSummaries` (type: `string`):

One row per model with the typical sold price and range in yen, how many sold, the original Japanese list price and what share of it the sold price holds, and which shops sold them.

# 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 = {
    "model": "Accuphase E-460",
    "genre": "2",
    "includeItems": false,
    "maxPages": 4
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/hifido-japan-audio-sold-comps").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 = {
    "model": "Accuphase E-460",
    "genre": "2",
    "includeItems": False,
    "maxPages": 4,
}

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/hifido-japan-audio-sold-comps").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 '{
  "model": "Accuphase E-460",
  "genre": "2",
  "includeItems": false,
  "maxPages": 4
}' |
apify call jpmarketdata/hifido-japan-audio-sold-comps --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/hifido-japan-audio-sold-comps"
        }
    }
}
```

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/aCwss68TqJFqgaGzY/builds/DC6AbFOs65x651SMa/openapi.json
