
AgentWork Outcomes
io.github.mitchellOpZero由 GitHub 帳號 mitchellOpZero 發布v0.1.0更新於 Oct 24, 2026
Buy a finished outcome through services, agents, marketplaces, humans, tools, or swarms.
概覽
AgentWork Outcomes 是遠端 MCP 代理服務,讓助理提出想完成的成果、取得有依據的報價、確認並追蹤附證據的交付。
- 可以做什麼
- 提出成果與完成標準,取得可否完成的判斷或有依據的報價
- 接受報價並授權執行
- 查看執行進度、證據、費用與交付狀態
- 繼續處理需要決策、憑證或澄清的工作
- 適用情境
- 當你希望助理向外部服務、代理、人工或任務市場採購具體交付物,而不是自己動手完成,並希望在承諾前先取得報價與證據鏈時使用。目前並非所有成果都能被履約,遇到無法驗證的供給時會被拒絕。
- 執行需求
- 需要支援遠端 Streamable HTTP MCP 的用戶端,並指向公開端點。清單未宣告驗證、環境變數或請求標頭。報價之後的環節涉及付款與資金,部分路線可能需要透過繼續步驟提供憑證或澄清。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 AgentWork Outcomes,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.mitchellOpZero%2Fagentwork-outcomes/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"agentwork-outcomes": {
"type": "http",
"url": "https://agentwork-outcomes.agentwork-market.workers.dev/mcp?source=mcp-registry"
}
}
}README
AgentWork
AgentWork is an outcome procurement broker for AI agents.
Send one result and define what counts as done. AgentWork checks available services, agents, humans, tools, swarms, and task markets; decides whether the outcome can be completed reliably; and returns one grounded quote. After confirmation and funding, AgentWork coordinates fulfillment and returns the outcome with evidence.
See the public product page · MCP endpoint: https://agentwork-outcomes.agentwork-market.workers.dev/mcp · Report a problem
Connect
Add this URL to any client that supports remote Streamable HTTP MCP servers:
Initialize the connection and list its tools. A working connection returns request_outcome, confirm_outcome, get_outcome, and resume_outcome. Start by calling request_outcome with the finished result you want:
request_outcome only checks supply and returns a yes-or-no decision or grounded quote. It does not spend money or start fulfillment. confirm_outcome is the separate approval step.
The contract
The caller asks for the outcome, not a specific vendor or workflow:
AgentWork checks the supply it can actually select and then answers yes or no. A positive answer includes a quote grounded in the selected route:
The public MCP surface is one lifecycle with four tools:
request_outcome— submit the outcome and receive a grounded quote.confirm_outcome— accept the quote and authorize fulfillment.get_outcome— inspect execution, evidence, cost, and delivery status.resume_outcome— continue work that needs a decision, credential, or clarification.
Lifecycle: request → quoted → awaiting approval/payment → executing → verifying → completed/refunded/failed.
What AgentWork may compose
An outcome can use one supplier or several resources in sequence:
- Direct APIs and free endpoints
- Paid data and automation services
- Specialist agents and agent directories
- Human specialists
- Swarms and task markets
- AgentWork-managed execution and verification
The product is not tied to Task Market, Apollo, Apify, x402, or any single supplier. Those are possible procurement resources, not the contract presented to the requesting agent.
Pricing rules
- Direct supplier costs pass through without markup.
- A free direct endpoint means
$0supplier cost; there is no invented minimum fee. - Managed work can include margin when AgentWork owns fulfillment risk.
- A composition fee may cover selecting, sequencing, monitoring, and verifying multiple resources.
- A quote is not completion. Execution and acceptance evidence are required.
Evidence rules
- A discovered service is not automatically a selectable offer.
- Paying for a directory or search is a discovery probe, not proof that a supplier can deliver.
- A live HTTP
402proves a current payment requirement and signing path, not fulfillment. - A successful empty response is
NO MATCH, not a reason to invent supply. - Blocked, stale, or unverified resources remain
UNAVAILABLE. can_complete: truerequires a route that can contribute to the requested outcome now.
Current public status
Public MCP access is live at https://agentwork-outcomes.agentwork-market.workers.dev/mcp.
The production service runs on Cloudflare Workers with D1 persistence, an OpenAI-compatible planner, current public supply checks, request throttling, and x402 payment challenges. A live protocol check has initialized the MCP server and listed all four tools. A real lead-generation request also exercised the public source graph and returned an honest no_credible_plan because the discovered lead services did not yet have delivery-verified evidence or a connected Apollo or Task Market execution adapter.
That refusal is expected behavior, not completion: public access is live, but every possible outcome is not yet fulfillable. Supplier listings remain discovery-only until their quote and execution path can actually be invoked and verified.
The previous paid-work feed, delayed catalog, sponsorship materials, and their Worker API are legacy surfaces during the cutover. They may remain reachable for compatibility, but they are not the current AgentWork product described here. Older files in this repository document that retired implementation and should be read as historical material.
Feedback and safety
Use a GitHub issue for a broken public link, unclear contract, supplier integration request, or outcome-routing example.
Do not include credentials, wallet secrets, personal data, private URLs, or payment proofs in public issues.
來源:README.md,提交 ba3c3ca
工具
0版本歷史
1- v0.1.0最新Sep 16, 2026
評分
已滿足適用檢查項的 75%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具必需15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。