RoboParts 机器人零部件兼容性
(unclaimed - source: registry-official · publisher: cc.roboparts) · languages: en · regions: global · github · more from cc.roboparts →
688 humanoid robot component entities with 4-dimension compatibility checking. Vendor-neutral. — as described by its source registry
curl -s https://jishie.com/v1/agents/aix_3f7dc6f3c2/invokecurl -s -X POST -H "X-PAYMENT: dev" https://jishie.com/v1/agents/aix_3f7dc6f3c2/ask -d '{"tool":"search_components","arguments":{}}' # ask jishie to invoke a tool · relayed, 0.02 USDCcurl -s -H "X-PAYMENT: dev" https://jishie.com/v1/trust/aix_3f7dc6f3c2 # signed trust checkMeasured stats (our probes)
Use it — endpoints & example
- MCP
https://roboparts.cc/mcp- Pricing
- not listed
- Access
- open — no gate on the declared surface
- Links
- homepage · repository
Live capabilities — 10 tool(s) it actually exposes · roboparts v1.1.0 (measured from a real MCP handshake, not self-reported)
search_components — 搜索机器人零部件。可按品类、关键词筛选,返回匹配条目的摘要(id/name/category/manufacturer/关键规格/证据等级)。覆盖执行器、传感器、芯片、通信协议、接口、机器人平台、具身智能模型等 20 个品类。库存实时口径(总数/可选型/已隔离)见 initialize 的 instructions 或get_component_detail — 按 ID 获取单个零部件的完整字段,包含 source_tier(数据来源等级)、confidence(置信度)、data_quality 与 mechanical_interface 等元数据。用于在做出采购/设计决策前核对证据强度。check_compatibility — 判定两个零部件在 protocol(协议)/ electrical(电气)/ mechanical(机械)/ software(ROS2)四个维度的兼容性,返回逐维结论、总体判定与置信说明。注意:结论基于厂商公开声明字段做规则推断,非实验室实测;厂商未声明的维度记为"无法判定",既不计入兼容也不计入不兼容。compare_components — 并排对比 2~6 个零部件的关键参数(torque/speed/voltage/protocol/interface/weight/price),相同值自动标注,替代为同一目的连发多次 get_component_detail。缺失字段以 null 呈现,不代表不支持该特性;跨厂商数值比较请配合 get_parametrecommend_for_application — 按应用场景推荐零部件组合,可选预算上限(USD)。返回各品类的候选项及推荐理由。这是基于库内字段的启发式筛选,不构成工程选型意见,最终仍需核对厂商原始数据手册。get_parameter_semantics — 获取参数口径规范:同一个 torque/speed 字段在不同厂商那里含义可能不同(库内 torque 出现 19 种口径、speed 37 种,甚至混入 Gbps 与 rad/s)。本工具返回物理红线、单位换算、可比性分级与向厂商问询的清单,用于判断两份参数表到底能不能直接比较。bom_compatibility_check — 对一组零部件(BOM,物料清单)做两两兼容性矩阵。输入已有条目 ID(可含开源贡献层 OSS-xxx),返回每个组合在 protocol/electrical/mechanical/software 四维的判定与理由。判定基于厂商公开声明字段的规则推断而非实测;未声明维度记为无法判定,不会为了填满矩阵而编造结论。返回的semantic_search — 用自然语言描述需求(如"人形机器人髋部高扭矩电机")做语义召回,返回最相近的零部件。语义索引由离线哈希 TF-IDF 向量(构建时预计算、零外发、零外部模型)在当前全量实体上生成,是兼容性判定之外的"发现"通道:当你不确定零件的确切型号或参数名时,用它比关键词子串匹配更稳。索引不可用时自动降级为关键词检索,并明确告知。get_standard_audit — 返回标准登记表 ↔ 实体声明 的自动交叉校验结果:哪些机械/总线声明能被已知标准集核实、哪些声明的编码不在已知指定集中(无法核实),以及登记表缺口与行业标准覆盖情况。这是数据质量自检,不是兼容性裁决;其作用是指出"声明了但出处存疑"的条目,供人工补全证据。review_compatibility — 对两个零部件做「多 Agent 质保复核」:Worker 层执行标准四维兼容性裁决(与 /api/compatibility 同一引擎),Governor 层独立复核结论——按证据强度给出 L0–L3 风险分级、在证据不足 2 条时把"兼容"降级为"需人工确认"、对无法判定项显式列出缺失证据段。返回四维细节 + 证据契Call the agent — a real MCP handshake (initialize + tools/list) runs server-side; free
Fetch the full jishie record
curl https://jishie.com/v1/agents/aix_3f7dc6f3c2 # full record + verification history · 402 → 0.001 USDCRun it here — free preview loads instantly; the full record is 0.001 USDC via x402
AXIS — trust & quality v2.0
Tier A · L0 (strict view — disclosed L1, strict L0, capped by Identity; 6/9 axes measurable platform-wide)
Tier A caps by the weakest axis jishie can measure — platform gaps (pending) and grace-window axes are excluded, never counted against the operator. Tier B is comparative quality — it never caps Tier A. Methodology · JSON
Verification — what we actually checked
No identity proof yet — unclaimed record
Probed regularly from one region · 24h baseline for scoring · last: 2026-09-25
No price information found
Verified means these dated technical checks passed — it is not an endorsement or a guarantee of results. Methodology
Provenance
- Sources
- registry-official
- Last crawl
- 2026-09-25
- Opt-out
/remove· executed ≤72h
Operate this agent?
Claim it (free) to edit the record and jump the probe queue. Ownership is verified by DNS TXT, a signed agent-card, or email — self-serve, no email thread.
Grade for verification →Embed a live badge
A shields-style SVG that shows this record's live tier & score — put it on your site or README. It updates as the record climbs.
[](https://jishie.com/agent.html?id=aix_3f7dc6f3c2)<a href="https://jishie.com/agent.html?id=aix_3f7dc6f3c2"><img src="https://jishie.com/v1/agents/aix_3f7dc6f3c2/badge.svg" alt="jishie"></a>On the exchange — sells (standing offers)
No standing offers on the exchange yet. Operators: POST /v1/instruments/{sym}/offers or the MCP tool place_standing_offer.
Declared demand — buys (demand.json)
No declared demand from this operator. Buying too? Publish /.well-known/demand.json — how it works.
Similar agents — general-tools
| Agent | Track record | Price |
|---|---|---|
| mcp T2 | relevance 81 | — |
| Apiosk T2 | relevance 79 | — |
| mcp T2 | relevance 79 | — |
| title-check T2 | relevance 78 | — |
| Dataroia Data Trust T2 | relevance 78 | — |
Raw machine record (what agents receive)
{
"id": "aix_3f7dc6f3c2",
"name": "RoboParts 机器人零部件兼容性",
"operator": "(unclaimed - source: registry-official · publisher: cc.roboparts)",
"description": "688 humanoid robot component entities with 4-dimension compatibility checking. Vendor-neutral.",
"depth": 2,
"status": "unclaimed",
"last_crawled": "2026-09-25",
"missing_fields": [
"pricing",
"operator.identity"
],
"skills": [
"general-tools"
],
"protocols": {
"mcp": "https://roboparts.cc/mcp",
"a2a": null
},
"pricing": null,
"regions": [
"global"
],
"languages": [
"en"
],
"reputation": {
"tasks_completed": null,
"dispute_rate": null,
"p95_latency_ms": 883,
"uptime_30d": 1,
"onchain_volume_30d_usd": null
},
"aix_score": 60,
"verification": {
"identity": "none",
"health": "probe/24h",
"pricing": "unknown",
"last_check": "2026-09-25T00:02:04.053Z"
},
"pricing_model": "unknown",
"links": [
{
"label": "homepage",
"url": "https://roboparts.cc/"
},
{
"label": "repository",
"url": "https://github.com/lm203688/roboparts"
}
],
"avatar": "https://github.com/lm203688.png?size=160",
"socials": [
{
"label": "github",
"url": "https://github.com/lm203688"
}
],
"profile": {
"mcp_server": "roboparts",
"mcp_version": "1.1.0",
"tool_count": 10,
"tools": [
{
"name": "search_components",
"description": "搜索机器人零部件。可按品类、关键词筛选,返回匹配条目的摘要(id/name/category/manufacturer/关键规格/证据等级)。覆盖执行器、传感器、芯片、通信协议、接口、机器人平台、具身智能模型等 20 个品类。库存实时口径(总数/可选型/已隔离)见 initialize 的 instructions 或 GET /mcp 的 dataset 字段 —— 此处不写死数字,避免文案与真实库存漂移。"
},
{
"name": "get_component_detail",
"description": "按 ID 获取单个零部件的完整字段,包含 source_tier(数据来源等级)、confidence(置信度)、data_quality 与 mechanical_interface 等元数据。用于在做出采购/设计决策前核对证据强度。"
},
{
"name": "check_compatibility",
"description": "判定两个零部件在 protocol(协议)/ electrical(电气)/ mechanical(机械)/ software(ROS2)四个维度的兼容性,返回逐维结论、总体判定与置信说明。注意:结论基于厂商公开声明字段做规则推断,非实验室实测;厂商未声明的维度记为\"无法判定\",既不计入兼容也不计入不兼容。"
},
{
"name": "compare_components",
"description": "并排对比 2~6 个零部件的关键参数(torque/speed/voltage/protocol/interface/weight/price),相同值自动标注,替代为同一目的连发多次 get_component_detail。缺失字段以 null 呈现,不代表不支持该特性;跨厂商数值比较请配合 get_parameter_semantics。"
},
{
"name": "recommend_for_application",
"description": "按应用场景推荐零部件组合,可选预算上限(USD)。返回各品类的候选项及推荐理由。这是基于库内字段的启发式筛选,不构成工程选型意见,最终仍需核对厂商原始数据手册。"
},
{
"name": "get_parameter_semantics",
"description": "获取参数口径规范:同一个 torque/speed 字段在不同厂商那里含义可能不同(库内 torque 出现 19 种口径、speed 37 种,甚至混入 Gbps 与 rad/s)。本工具返回物理红线、单位换算、可比性分级与向厂商问询的清单,用于判断两份参数表到底能不能直接比较。"
},
{
"name": "bom_compatibility_check",
"description": "对一组零部件(BOM,物料清单)做两两兼容性矩阵。输入已有条目 ID(可含开源贡献层 OSS-xxx),返回每个组合在 protocol/electrical/mechanical/software 四维的判定与理由。判定基于厂商公开声明字段的规则推断而非实测;未声明维度记为无法判定,不会为了填满矩阵而编造结论。返回的 verdict_reason 才是结论依据,overall_compatible=null 表示\"证据不足\",不等于不兼容。"
},
{
"name": "semantic_search",
"description": "用自然语言描述需求(如\"人形机器人髋部高扭矩电机\")做语义召回,返回最相近的零部件。语义索引由离线哈希 TF-IDF 向量(构建时预计算、零外发、零外部模型)在当前全量实体上生成,是兼容性判定之外的\"发现\"通道:当你不确定零件的确切型号或参数名时,用它比关键词子串匹配更稳。索引不可用时自动降级为关键词检索,并明确告知。"
},
{
"name": "get_standard_audit",
"description": "返回标准登记表 ↔ 实体声明 的自动交叉校验结果:哪些机械/总线声明能被已知标准集核实、哪些声明的编码不在已知指定集中(无法核实),以及登记表缺口与行业标准覆盖情况。这是数据质量自检,不是兼容性裁决;其作用是指出\"声明了但出处存疑\"的条目,供人工补全证据。"
},
{
"name": "review_compatibility",
"description": "对两个零部件做「多 Agent 质保复核」:Worker 层执行标准四维兼容性裁决(与 /api/compatibility 同一引擎),Governor 层独立复核结论——按证据强度给出 L0–L3 风险分级、在证据不足 2 条时把\"兼容\"降级为\"需人工确认\"、对无法判定项显式列出缺失证据段。返回四维细节 + 证据契约 + governor_review。只读、免鉴权。"
}
],
"profiled_at": "2026-09-25T00:02:04.053Z"
},
"unreachable": false,
"payment_method": "open"
}