`agent-pay check`: accept an MCP config file as the registry
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with the agent-pay check --registry loader and the existing atomic-units registry format it expects, then read the linked CONTRIBUTING.md and docs/REVIEWING.md. Add a branch for the MCP config shape (a network and merchants object) that converts decimal strings with exact parsing, such as viem's parseUnits, and maps price to pricePin and tolerancePct to toleranceBps. Done means tests cover both file shapes and a clear error for anything else, and the preset question is answered in the issue before coding.
由索引模型根据 Issue 内容生成。
描述
An owner who already runs agent-pay-mcp has their sellers in an MCP config: decimal USDC strings such as "price": "0.003", "maxPerTx": "0.005". agent-pay check --registry expects a different JSON, with atomic units and pricePin. So today they would maintain two files.
What: when the --registry file is an object with network and merchants (the MCP config shape), convert it: decimal strings become atomic units, price becomes pricePin, and tolerancePct becomes toleranceBps. Also accept "preset": "verified" if it's easy to share the preset data. Otherwise report clearly that presets aren't supported there yet.
Acceptance:
- Tests for both file shapes, and a clear error for anything else.
- The conversion is exact: no floating point, so use viem's
parseUnitsor equivalent.
New to the repo? Start with CONTRIBUTING.md. Every outside PR goes through the review gates in docs/REVIEWING.md. Please discuss any new dependency in this issue first. Comment here before starting, so two people don't build the same thing.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 3 小时 51 分钟
- 30 天内合并 PR
- 3
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DeepFirstHQ/deepfirstsearch 的其他 Issue
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 62/100
-
enhancement help wanted
难度 3/5 1-2 天 新手友好度 50/100
-
good first issue integration
难度 4/5 3-5 天 新手友好度 45/100
-
help wanted integration
难度 3/5 1-2 天 新手友好度 50/100
-
enhancement good first issue
难度 3/5 1-2 天 新手友好度 62/100
查看 DeepFirstHQ/deepfirstsearch 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 67/100
agilepathway/label-checker#739 · 4 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
CopilotKit/OpenBot#800 ·
维护者通常 1 天内回复
-
Endpoint links in the tag operations list are below the 24px target size可能已有人在做 @AdzerKI 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 79/100
ehmpathy/rhachet-roles-bhuild#471 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复