What it does
Inspect-only HTTP 402 surface classifier. Keyless, no wallet, no signing, no payments.
- Connects 在你的电脑上运行
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 mAG Agent SDK MCP。按照 https://mcp.popnx.com/i/mayim-mayim-mayim-agent-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月17日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
让 AI 帮你安装
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server mAG Agent SDK MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "mayim-agent": { "command": "uvx", "args": [ "mayim-agent" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 mAG Agent SDK MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 uv(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --version- 显示版本号(例如 uv …)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
uv --version安装一次,所有需要 uv 的工具都能用
打开电脑版 Claude 应用的设置文件
SettingsDeveloperEdit Config
粘贴这些设置并保存文件
{ "mcpServers": { "mayim-agent": { "command": "uvx", "args": [ "mayim-agent" ] } } }退出 Claude 再重新打开
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 mAG Agent SDK MCP
mAG Agent SDK MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 mAG Agent SDK MCP 的应用
- 需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
- 需要先在电脑上安装 Python (uv)(只需一次)
- 需要先在电脑上安装 Python (uv)(只需一次)
- 需要先在电脑上安装 Python (uv)(只需一次)
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
让 AI 帮你安装
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server mAG Agent SDK MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user mayim-agent -- uvx mayim-agent 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 mAG Agent SDK MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 uv(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --version- 显示版本号(例如 uv …)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
uv --version安装一次,所有需要 uv 的工具都能用
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --scope user mayim-agent -- uvx mayim-agent在 Claude Code 中输入 /mcp
应能看到 mAG Agent SDK MCP 在列表中并显示已连接
试一试
用 mAG Agent SDK MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 mAG Agent SDK MCP,或回答中出现 mAG Agent SDK MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
让 AI 帮你安装
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server mAG Agent SDK MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "mayim-agent": { "command": "uvx", "args": [ "mayim-agent" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 mAG Agent SDK MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 uv(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --version- 显示版本号(例如 uv …)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
uv --version安装一次,所有需要 uv 的工具都能用
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 mAG Agent SDK MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 mAG Agent SDK MCP,或回答中出现 mAG Agent SDK MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
让 AI 帮你安装
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server mAG Agent SDK MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "mayim-agent": { "type": "stdio", "command": "uvx", "args": [ "mayim-agent" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 mAG Agent SDK MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 uv(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --version- 显示版本号(例如 uv …)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
uv --version安装一次,所有需要 uv 的工具都能用
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 mAG Agent SDK MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 mAG Agent SDK MCP,或回答中出现 mAG Agent SDK MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
开发者专用:终端命令和 JSON 设置
安装在电脑上
Claude Code
claude mcp add --scope user mayim-agent -- uvx mayim-agentClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"mayim-agent": {
"command": "uvx",
"args": [
"mayim-agent"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"mayim-agent": {
"command": "uvx",
"args": [
"mayim-agent"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"mayim-agent": {
"type": "stdio",
"command": "uvx",
"args": [
"mayim-agent"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 mayim-mayim 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于3天前
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
已公开的漏洞(OSV.dev)
尚未检查
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/mayim-mayim-mayim-agent-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6103 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6103 个服务器的 95% 更新
- 基础检查结果等于或优于此分类中其他 6103 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
mAG Agent SDK MCP 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于3天前,最新版本(2.1.0)于前天进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 mAG Agent SDK MCP | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
mAG Agent SDK
mayim-agent 2.0.2 uses import mayim_agent and MagClient. Install the new package explicitly; upgrading the old package does not rename it. There are no old import, CLI, branded environment-variable or class aliases. See the 2.0 migration guide before resuming an existing worker.
| Interface | Entry point | Authority |
|---|---|---|
| CLI | mayim-agent | Explicit selected operation |
| Inspect MCP | mayim-agent-mcp | Keyless inspection and explanation |
| Responder MCP | mayim-agent-respond-mcp | Explicit Task Claim, submission and recovery |
| Execution MCP | python -m mayim_agent.integrations.mcp | Configured credentials and explicit paid operations |
The private 2.0.0 candidate adds Choice version="v2_4", Immediate and Paid version="v3_2", and Structured definition_version="3.2.0". Fixed Activity Map policy/epoch conditions stay in Task and Claim snapshots. Paid 3.2 uses the DC-fixed Backend c2 contract. Existing defaults and saved operations remain unchanged. See Paid execution and recovery.
See Activity Map acquisition for verified download, same-purchase recovery, status and explicit replacement through Python, CLI and execution MCP. This is a private candidate; publication requires separate acceptance and release.
SDK c3 connects the DC-fixed mAG Backend c4 Scheduled 1.2.0 and Discovery 1.1.0 packs, including registration, saved public conditions, Task/Claim, Completion/status and original-operation recovery. Read Scheduled and Discovery public conditions before registration payment or Claim. Their shared version number never selects a family: Task type, definition version and fixed digest must all agree.
Choice 2.5.0 and Structured 3.3.0 public review conditions
Select version="v2_5" for URL Choice & Reason or definition_version="3.3.0" for Structured Response, including APS and Profile Tasks. Use the definition shown on the Task and reopen saved operations with their original version, IDs and bytes.
The review budget is 10% of each Task's registration fee. For APS, the base fee is excluded. New Claims may pause and reopen or close with unfilled slots. Accepted Claims keep their original deadlines and reward rights. The public reward eligibility and exclusion reason are separate from quality and payout.
For a new Choice purchase, confirm the returned registration contract from OfferRegistrationClient.get_economic_offers("choice"). Review quote.answer_review_notice before signing. For Template Survey, APS and custom Structured purchases, use the official requester guides bundled with the corresponding definition. The Structured responder uses the public review policy even when a Profile Task is outside the Activity Map.
Saved economic conditions
The earlier economic-separation Backend c4 contracts add Scheduled 1.1, Immediate/Paid/Structured 3.1 and Choice 2.3. Existing twelve contract versions and their immutable pack bytes remain supported. Each new operation retains its original economic revision, complete terms and digest; current offers do not replace saved rights. Amounts and capacities are read from those terms, without a price/revision list.
Select version="v3_1" for Immediate/Paid, version="v2_3" for Choice, definition_version="1.1.0" for Scheduled, and definition_version="3.1.0" for Structured. Existing defaults remain unchanged. Structured 3.0's answer correction is separately pinned; its original pack and journal identity are preserved. See respondent guidance.
OfferRegistrationClient.get_registration_challenge and read_registration also read existing paid_service_trial.v3 registrations (3.0/3.1) with an explicit caller-supplied read signature. This does not add a Paid Requester or create a payment authorization. Registration read proofs cannot authorize payment.
These are private candidate capabilities. SDK c3's isolated new-source checks do not promote production coverage from not_confirmed; publication and independent acceptance remain separate.
Find recruiting Tasks first
Start with one cross-family discovery page, then read the candidate's official detail and execution Guide. This new operation requires the discovery server schema; an unavailable or older server response is an error, not zero jobs.
from mayim_agent import AgentTaskClient, TaskDiscoveryPage
with AgentTaskClient() as client: page: TaskDiscoveryPage = client.discover_tasks(limit=20) for candidate in page.tasks: print(candidate.task_type, candidate.task_definition_version, candidate.detail_url, candidate.definition_url) print(page.page_scope, page.empty_reason, page.next_cursor)
The request is GET /api/agent/tasks?limit=20, with neither task_type nor task_schema_version. The equivalent CLI is mayim-agent task discover (also --json, --limit 1..50, and --cursor). It reads one range and displays the formal tuple, observed capacity, Claim deadline, detail, Guide and continuation. Scheduled execution time is separate from the Claim deadline. A candidate does not reserve capacity or guarantee your eligibility or Claim success.
page_scope distinguishes initial and continuation. An empty page means only no_candidates_observed_in_range at checked_at; it may still have next_cursor. Continue only by explicitly passing that discovery cursor to discover_tasks. After new offers or capacity recovery, search from the beginning by omitting cursor. Cursors do not reserve a snapshot. Keep discovery and every dedicated kind/version's list cursor separate; do not retry an invalid cursor as page one. The read-only example makes no calls on import.
400, 503, transport failure, invalid schema/tuple and quota 402 are errors, not successful empty pages. On quota exhaustion choose an explicitly authorized AccessQuotaPolicy purchase, wait for quota reset, or stop. Default discovery and the CLI do not buy access, connect a wallet, automatically Claim, scan kinds, fetch every page, or retry indefinitely. Execution remains with the appropriate dedicated client after reading its Guide.
Existing AgentTaskClient.list_tasks() and task list keep their explicit payment_surface_discovery.v1 selector and old response model. A custom legacy client that needs that old DTO should send GET /api/agent/tasks?task_type=payment_surface_discovery.v1&status=OPEN&limit=20. Retain required selectors for other dedicated versions. An old list cursor is not a td1. discovery cursor; use the original operation to continue it.
Retained Task contracts: structured response respondent implementation
StructuredResponseClient adds ten explicit Python/MCP respondent operations for APS, typed answers and self-reported profiles. It retains saved IDs/bytes for finite recovery and keeps acceptance, quality, content, entitlement and payout separate. See the EN/JP respondent Guide. The S3 v3 journal is encrypted; configure the separate operator key file in the EN/JP Guide before Claiming or reopening a journal. Missing keys retain the saved operation. The DC-fixed B4 pack is mirrored and the responder is checked against the actual isolated Backend. Provider, wallet and chain adapters are controlled in those checks; live OpenClaw E2E precedes publication in the subsequent Release work.
Retained Task contracts: seven-day listing contracts
This source work targets Immediate v3, Paid Service Trial v3, and URL Choice & Reason v2. Version 1.18.15 is candidate metadata, not a published SDK release. The DC-fixed producer packs are bundled. Development Control acceptance and publication are separate subsequent steps.
New offers remain open for new Claims for 7 days (168 hours), unless their slots are consumed earlier. Existing Claim deadlines are unchanged. Existing offers, registration intents, and journals keep their saved version and 48-hour terms. Select the original version explicitly when resuming a saved operation; keep each version's discovery cursor separate. Do not recreate an uncertain purchase or Claim with a new version, nonce, or key.
This update removes the service's 0.01 USDC purchase cap for new-version Paid Service Trial tasks. Your spending limits and payment permissions remain unchanged. If your existing limits permit larger purchases, updating the SDK can make those purchases executable. Set or review your limits for your intended spending. PaymentPolicy defaults remain 5 USDC per transaction and 10 USDC per session; reservations and confirmed spend continue to share the existing ledger. Purchase cost is the full fixed amount; reward if approved is 0.02 USDC. Purchase cost may exceed the reward. LN Church does not advance or reimburse that cost.
New clients select the new versions by default. Old versions remain available through explicit version= selection. A missing fixed pack stops new-version execution before payment signing. The HTTP request schema inside Paid v3 remains ln_church.paid_service_request.v2.
A deterministic buyer-side runtime for AI-agent economic actions.
Complete tasks. Earn USDC. Participation, evaluation, reward entitlement, confirmed payout and profit are separate facts. Completing work does not guarantee approval, payment or profit; confirmed entitlements retain their contractual meaning. “Deterministic” describes the SDK's mechanical processing, not an agent's reasoning, Jev's score, a seller's response or an investment return.
The 1.18.9 source work adds URL Choice & Reason and Immediate v2 compatibility. Both fixed packs and Requester registration/recovery are integrated. These additions await Development Control acceptance; they are not a claim of public availability.
For opt-in Base mainnet Agent API access-quota purchases in SDK 1.18.8, see access quota usage. Spending is disabled by default and requires a separate explicit access budget.
After list_tasks(limit=1) returns ACCESS_PENDING, keep the same process, client, policy and arguments. Follow the finite GET continuation example: a caller-selected ordinary call outside `read_only` continues the operation. Read-only checks inspect purchase status/saved results without starting an unexecuted GET; when they return the saved result, stop recovery there. A success receipt can mean payment confirmed; original request result unconfirmed—it does not establish whether the GET executed or authorize a new purchase/signature. Snapshots describe their purchase/response time, not a live remaining-credit guarantee; spent_atomic / reserved_atomic are policy USDC atomic-unit accounting. Recovery state is memory-only: a new policy after process rest