OPX
Buyer-side machine commerce: choose where to spend using recent paid x402 provider evidence.
我該用這個嗎
品質與安全性
B
發現項目(1)
- LOW在 opx_choose_x402_provider 中
根據工具定義與協定合規性的自動化分析。
上下文成本
~296Token(工具定義)
~2.9 KB典型回應大小
極小的注意力影響(128k 上下文的 0.23%)
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"opx": {
"url": "https://opx-status.dev/mcp"
}
}
}遠端端點
https://opx-status.dev/mcpstreamable-http它能做什麼
工具清單
工具(1)
🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
⚪opx_choose_x402_provider(task, intent, freshness, q, budget, ...)
Choose the best x402 provider before spending. OPX uses recent paid performance evidence to recommend a primary provider and independent fallback. Costs $0.002 USDC on Base.
輸入結構描述
{
"type": "object",
"properties": {
"task": {
"type": "string",
"const": "web-search",
"description": "Call OPX before buying an x402 web-search provider. The supported task is web-search."
},
"intent": {
"type": "string",
"enum": [
"web",
"news",
"research",
"known-page",
"company"
],
"description": "Search job to route; defaults to web."
},
"freshness": {
"type": "string",
"enum": [
"any",
"day",
"week",
"month"
],
"description": "Preferred freshness class; defaults to any. Day/week evidence is currently coarse."
},
"q": {
"type": "string",
"description": "Optional routing context. OPX routes by intent and measured fixtures; it does not execute this query."
},
"budget": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Maximum downstream provider price in USD, excluding the OPX fee."
},
"max_latency_ms": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Maximum measured p50 downstream provider latency in milliseconds."
}
},
"required": [
"task"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}社群
證據
近期觀測
已驗證未記錄版本1 個工具