
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 分
请在仓库或注册中心条目中声明许可证。