原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

carsensor Price Range MCP Server for AI Agents

作者:czcz0009版本 0.1.0i★ 0i在云端运行官方网站 ↗
注册名称io.github.czcz0009/carsensor-price-range-mcp

安装方法

能做什么

Get a used car's market-price range (min/max/median) by model and year from carsensor.net.

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 需要 Authorization
  • 分类 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分15/100

质量: 基础检查通过 3/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 carsensor Price Range MCP Server for AI Agents。按照 https://mcp.popnx.com/i/czcz0009-carsensor-price-range-mcp.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 3/5 项检查 · 你的提问会经过开发者的服务器(woolen-snake--carsensor-price-range-mcp.apify.actor) · ✓ 命令已检查 2026年11月20日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 5 分钟

需要 carsensor Price Range MCP Server for AI Agents 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 注册并创建 carsensor Price Range MCP Server for AI Agents 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    获取密钥的方法见下方开发者的 README

  2. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称carsensor Price Range MCP Server for AI Agents
    Remote MCP server URL · 地址https://woolen-snake--carsensor-price-range-mcp.apify.actor/mcp

    在 Request headers 下添加这个名称和值

    Header 名称Authorization
    值Bearer <在这里粘贴你的密钥>

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  4. 在聊天中开启

    +Connectorscarsensor Price Range MCP Server for AI Agents

  5. 试一试

    用 carsensor Price Range MCP Server for AI Agents 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 carsensor Price Range MCP Server for AI Agents,或回答中出现 carsensor Price Range MCP Server for AI Agents 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 carsensor Price Range MCP Server for AI Agents

carsensor Price Range MCP Server for AI Agents 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式

你可以改用这些方式

A · 使用能连接 carsensor Price Range MCP Server for AI Agents 的应用

  • 需要 carsensor Price Range MCP Server for AI Agents 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
  • 需要 carsensor Price Range MCP Server for AI Agents 的密钥(在开发者网站创建)
  • 需要 carsensor Price Range MCP Server for AI Agents 的密钥(在开发者网站创建)
  • 需要 carsensor Price Range MCP Server for AI Agents 的密钥(在开发者网站创建)

B · 其他 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code · 约 5 分钟

需要 carsensor Price Range MCP Server for AI Agents 的密钥(在开发者网站创建)

  1. 注册并创建 carsensor Price Range MCP Server for AI Agents 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    获取密钥的方法见下方开发者的 README

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user carsensor-price-range https://woolen-snake--carsensor-price-range-mcp.apify.actor/mcp --header 'Authorization: Bearer your-value'

    按 Enter 前,把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Claude Code 中输入 /mcp

    应能看到 carsensor Price Range MCP Server for AI Agents 在列表中并显示已连接

  5. 试一试

    用 carsensor Price Range MCP Server for AI Agents 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 carsensor Price Range MCP Server for AI Agents,或回答中出现 carsensor Price Range MCP Server for AI Agents 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 5 分钟

需要 carsensor Price Range MCP Server for AI Agents 的密钥(在开发者网站创建)

  1. 注册并创建 carsensor Price Range MCP Server for AI Agents 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    获取密钥的方法见下方开发者的 README

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 carsensor Price Range MCP Server for AI Agents 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Cursor 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 carsensor Price Range MCP Server for AI Agents 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 carsensor Price Range MCP Server for AI Agents,或回答中出现 carsensor Price Range MCP Server for AI Agents 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 5 分钟

需要 carsensor Price Range MCP Server for AI Agents 的密钥(在开发者网站创建)

  1. 注册并创建 carsensor Price Range MCP Server for AI Agents 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    获取密钥的方法见下方开发者的 README

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 carsensor Price Range MCP Server for AI Agents 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 VS Code 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 carsensor Price Range MCP Server for AI Agents 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 carsensor Price Range MCP Server for AI Agents,或回答中出现 carsensor Price Range MCP Server for AI Agents 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://woolen-snake--carsensor-price-range-mcp.apify.actor/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 carsensor Price Range MCP Server for AI Agents 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user carsensor-price-range https://woolen-snake--carsensor-price-range-mcp.apify.actor/mcp --header 'Authorization: Bearer your-value'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "carsensor-price-range": {
      "url": "https://woolen-snake--carsensor-price-range-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "carsensor-price-range": {
      "type": "http",
      "url": "https://woolen-snake--carsensor-price-range-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

需要你填写的值

  • Authorization 机密 必填 HTTP header
    Your own Apify API token, formatted as 'Bearer '. Get one at https://console.apify.com/settings/integrations. Required because this server bills each successful call via Apify Pay-Per-Event ($0.03/ca…

说明仍为英文原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.1.0
分类i
其他
发布到注册中心i
2026年8月26日
代码最后更新i
2026年8月28日
最近检查
2026年11月15日
作者
czcz0009
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 czcz0009 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于3个月前

  • ✓ 通过

    有许可证

    使用 ISC

  • ! 注意

    端点有响应

    拒绝访问(HTTP 401),且未提供 OAuth 登录。可能需要密钥,也可能是拦截机器人,尚未确认。

  • ! 注意

    使用 OAuth 登录

    需要你自己复制粘贴密钥或令牌

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/czcz0009-carsensor-price-range-mcp.svg)](https://mcp.popnx.com/en/servers/czcz0009-carsensor-price-range-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20868 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 20868 个服务器的 25% 更新
  • 基础检查结果等于或优于此分类中其他 20868 个服务器的 11%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

carsensor Price Range MCP Server for AI Agents 安全吗?

它在 5 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:Authorization

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于3个月前,最新版本(0.1.0)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万4天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92762个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582414个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
carsensor Price Range MCP Server for AI Agents
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥是否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查3/54/44/44/41/44/4
许可证ISCAGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

carsensor Price Range MCP Server for AI Agents

If you're building an AI agent, chatbot, or app that needs to answer "is this used car's asking price fair?" — not a guess, but a number grounded in real market data — this MCP server gives you exactly that in a single tool call. resolvePriceRange(carModel, year) returns a market-price range (min / max / median) computed live from carsensor.net's own official price-by-model-year market statistics — the same data carsensor itself publishes on its 相場(market price) pages, turned into a structured, ready-to-use number instead of a page you'd have to read and interpret yourself.

What you get:

  • One tool, resolvePriceRange, taking just a car model name and a year — no API keys to manage for the underlying data source, no HTML to parse yourself
  • priceRangeYen: { min, max, median } plus sampleSize (how many real carsensor listings the estimate is based on) and confidence (normal / low — honestly downgraded, not hidden, when the year can't be fully verified against carsensor's own data; see "Known limitations")
  • Always-on hosting via Apify Standby mode — no server to run yourself. Connect any MCP client (Claude Desktop, Claude Code, your own agent) directly to a stable HTTPS endpoint, or call it as a plain Streamable HTTP MCP server from your own app's code
{

"ok": true, "carModel": "プリウス", "year": 2018, "priceRangeYen": { "min": 750000, "max": 4772500, "median": 1573112 }, "sampleSize": 412, "confidence": "normal", "disclaimer": "carsensor.net上の公開情報(相場ページの価格×年式集計)を基にした参考値です。個体差・装備差・実際の商談結果は反映されません。" }

Pay-per-event pricing — see "Pricing" below. Full input/output details, setup, and technical design are further down this page.

⚠️ Disclaimer (please read)

  • This Actor automatically retrieves information that is publicly available on carsensor.net. You are responsible for how you retrieve and use this data.
  • The site owner's Terms of Use, robots.txt, or access blocking could change without notice, which could stop this Actor from working or change its output unexpectedly.
  • `priceRangeYen` is a statistical estimate derived from carsensor's own published price×model-year aggregate data, not a guarantee of any individual vehicle's true value. It does not account for condition, trim/grade differences, or mileage (see "Known limitations"). Always verify a specific vehicle's price on carsensor.net itself before making any purchase or sale decision based on this data.

Who is this for?

  • AI agents and chatbots that need to ground a "what is this actually worth?" answer in real market data instead of the model's own (often outdated or hallucinated) knowledge of used-car pricing
  • App/tool developers building car-shopping, valuation, or trade-in estimation features who want a ready-made price-range lookup instead of scraping and maintaining their own carsensor.net integration
  • Anyone who wants this as a plain MCP tool call rather than a batch scrape — this Actor is the single-tool, call-on-demand counterpart to our batch-oriented carsensor-resale-value-scout Actor (which scores whole lists of listings against the same underlying market data)

What can't it do (please read before integrating)

  • Mileage is not a supported input yet. Only car model and year are used — the price range reflects carsensor's own model-year aggregate, not a mileage-adjusted estimate. A future version may add this.
  • Model-name resolution can occasionally fail or be slow on first use for an unfamiliar model — see "Known limitations" for why, and how caching mitigates this after the first call.
  • This is a statistical estimate, not an appraisal. See the Disclaimer above.

Input / Output

Input (MCP tool call arguments):

ParameterTypeRequiredDescription
carModelstringYesCar model name, same free-text format as carsensor's own search (e.g. "プリウス", "N-BOX")
yearintegerYesModel year, 4-digit (e.g. 2018)

Output (success):

FieldTypeDescription
priceRangeYen.min / .max / .medianinteger (JPY)Estimated market-price range for this model/year
sampleSizeintegerNumber of carsensor listings the estimate is aggregated from
confidence"normal" \"low""low" when the year only matches an open-ended bucket in carsensor's data (see "Known limitations") — a note field explains why when this happens
cacheStatusobjecttier1/tier2 — whether this call hit cached data or made a fresh request to carsensor.net (informational only, does not affect price — see "Pricing")

Output (model not found / no data for that year): { "ok": false, "reason": "no_code_resolved" | "no_matching_data", "message": "..." } — not charged (see "Pricing").

Usage example

Claude Desktop / any MCP client config:

{

"mcpServers": { "carsensor-price-range": { "url": "https://woolen-snake--carsensor-price-range-mcp.apify.actor/mcp", "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" } } } }

Calling it directly from your own app (Node.js, `@modelcontextprotocol/sdk`):

import { Client } from '@modelcontextprotocol/sdk/client/index.js';

import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';

const transport = new StreamableHTTPClientTransport( new URL('https://woolen-snake--carsensor-price-range-mcp.apify.actor/mcp'), { requestInit: { headers: { Authorization: Bearer ${process.env.APIFY_TOKEN} } } }, ); const client = new Client({ name: 'my-app', version: '1.0.0' }); await client.connect(transport);

const result = await client.callTool({ name: 'resolvePriceRange', arguments: { carModel: 'プリウス', year: 2018 }, }); console.log(JSON.parse(result.content[0].text));

Pricing

EventPriceTrigger
Price range resolved (resolve-price-range-success)$0.03Charged only when resolvePriceRange successfully returns a price range. Not charged when the car model can't be resolved or no matching year data exists

Flat pricing regardless of whether the call hit cached data or triggered a fresh request to carsensor.net — see "How the price was set" below for the full reasoning, including why cache-tiered pricing was deliberately rejected.

How the price was set

$0.03 sits between this Actor family's base classification tier ($0.015, e.g. listing-extracted on our carsensor-resale-value-scout Actor) and its heavier derived-signal tier ($0.045–$0.065, e.g. value-score-computed) — reflecting that a price range is a computed market signal, not a raw data fetch, while this tool's underlying infra cost (well under $0.001/call, most calls served from cache) leaves a large margin either way.

Why cache hits and misses are priced the same: the value delivered — priceRangeYen, sampleSize, confidence — is identical either way; caching is purely an internal performance/cost optimization, not a difference in what you get. Pricing it differently would also create a perverse incentive to shorten the cache TTL (more misses = more revenue), which runs directly against this tool's own design goal of minimizing load on carsensor.net.

Data source and calculation

Uses carsensor.net's own publicly-published 相場(market price) page for the resolved model (/usedcar/souba/{makerCode}_S{modelCode}/), specifically its "price × model-year" cross-tabulation (price bucket, year bucket, listing count per cell) — official aggregate data carsensor itself computes from its own live inventory, not a third-party estimate.

  • median is a count-weighted average of each matching year-bucket's price-bucket midpoint
  • min / max come from the actual price-bucket bounds of the matching cells (open-ended buckets, e.g. "¥4,150,000 or more", are approximated with a ±15% heuristic — an empirical adjustment, not a statistically derived one)
  • This is grade-level aggregate data (e.g. all Toyota Prius trims combined), not individual-listing pricing — it doesn't account for trim/grade differences, equipment, or condition

Caching (2-tier)

TierKeyValueStorageExpiry
1Car model name{ makerCode, modelCode }File-persistedUnbounded (carsensor's model coding is effectively static)
2{makerCode}_S{modelCode}carsensor's price×model-year cellsFile-persisted12 hours

A cache hit on both tiers means zero HTTP requests to carsensor.net for that call. On the Apify-hosted version, this cache is scoped to a single Standby run/container instance — concurrent sessions can land on different container instances with independent caches, so the real-world hit rate on the hosted version may be lower than what a single long-running local process would see. A future version may move this to Apify's Key-Value Store (shared across runs) if this turns out to matter in practice.

Access interval and logging

Requests to carsensor.net are paced at a minimum 1000ms interval (1500ms by default) as a load-reduction measure — the same floor used by our carsensor-resale-value-scout Actor. Every call is logged (model, year, per-tier cache hit/miss, HTTP requests actually made, response time, outcome) for future monitoring — not exposed to callers, used only for operating this Actor responsibly.

FAQ

Why is `confidence` sometimes `"low"`? carsensor's year axis has an open-ended bottom bucket in its own data (e.g. "2012 or earlier"). Any year at or before that bound will match it, whether or not the model actually existed yet in that year — there's no way to fully verify plausibility from this data alone, so confidence is honestly downgraded rather than reported as certain. See the note field on such responses for the specific reason.

Why does my first call for a given model take a few seconds, but repeat calls are much faster? The first call for an unfamiliar model needs up to 3 real requests to carsensor.net (search → detail page → market-price page) to resolve which model this is. Once resolved, the model→code mapping is cached effectively permanently, and the price data itself is cached for 12 hours — so repeat calls for the same model are near-instant.

Does this cover mileage? Not yet — see "What can't it do."

How is this different from `carsensor-resale-value-scout`? That Actor is a batch scraper: give it a search term, get back a list of live listings each scored against this same market data. This Actor is the single-call, on-demand counterpart, built for AI agents and apps that want one number for one model/year — not a list to scrape and process.

Known limitations

  • Model-name resolution has no direct lookup — it goes through carsensor's own freeword search and reads a matching listing's page to identify the model. For a genuinely unrecognized model (typo, non-existent model), carsensor's search results page still contains a "you might also like" widget with unrelated cars; this Actor explicitly detects and excludes that widget so it doesn't get mistaken for a real match — confirmed via live testing.
  • `confidence` cannot fully verify whether a queried year is plausible for a given model — see FAQ.
  • This is a grade-level aggregate, not an individual-listing price — see "Data source and calculation."
  • The file-based cache is per-container on the hosted (Apify Standby) version — see "Caching."
  • This tool's underlying scraping logic is deliberately duplicated from, not imported from, `carsensor-resale-value-scout`'s codebase, to keep the two independently-deployed Actors decoupled. A carsensor.net markup change affecting one may require a matching fix in the other.
  • Not listed on Smithery: Apify Standby's authentication response isn't OAuth-discovery-conformant, whi

只显示了开头部分;其余内容请在仓库中阅读