[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C3XVRXYNB5J69Y53AH4CVM":3,"skill-same:01M7C3XVRXYNB5J69Y53AH4CVM":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7C3XVRXYNB5J69Y53AH4CVM","mpp-agent",null,"Pay HTTP 402 APIs via Machine Payments Protocol (MPP).","fengwhang\u002Fmercury","fengwhang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F325040254?v=4","01M7C3K54Y41KVGPHEMKEP9X70","01M7C3K55NTZ4B36YP2JY1NMJ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fpayments\u002Fmpp-agent\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mpp-agent\ndescription: Pay HTTP 402 APIs via Machine Payments Protocol (MPP).\nversion: 0.1.0\nauthor: Teknium (teknium1), Hermes Agent\nlicense: MIT\nplatforms: [linux, macos]\nmetadata:\n  mercury:\n    tags: [Payments, MPP, HTTP-402, Tempo, Stripe]\n    related_skills: [stripe-link-cli, stripe-projects]\n---\n\n# MPP Agent Skill\n\nWraps the Machine Payments Protocol (MPP, https:\u002F\u002Fmpp.dev) clients so Hermes can pay for per-request API access against servers that respond with `HTTP 402 Payment Required`.\n\nThree client options, all distributed via npm. Pick the lightest one that solves the user's need. Gated `[linux, macos]` while the broader payments tooling matures on Windows.\n\n## When to Use\n\n- A merchant API returns `HTTP 402` with a `www-authenticate` header — and the user wants to actually pay it, not just log the response.\n- The user asks to \"pay per request\", \"set up an agent wallet\", \"use Tempo \u002F Privy \u002F AgentCash\", or wants to discover MPP-priced services.\n- A Stripe Link spend has produced a Shared Payment Token (SPT) and the agent needs to attach it to the 402 challenge — in that flow, prefer `link-cli mpp pay` (see the `stripe-link-cli` skill).\n\n## Choosing a client\n\n| Tool | When | Setup |\n|---|---|---|\n| `link-cli` | User already has Stripe Link set up, or the 402 challenge advertises `method=\"stripe\"` | see the `stripe-link-cli` skill |\n| Tempo Wallet | MPP services with spend controls, service discovery | `tempo wallet login` |\n| Privy Agent CLI | Multi-chain wallets, browser-based funding | `privy-agent-wallets login` |\n| AgentCash | 300+ pre-priced APIs via one USDC.e balance | `npx agentcash onboard` |\n| `mppx` | Dev + debugging, smallest dep surface | `npm install -g mppx` then `mppx account create` |\n\nDefault: if the user already has Stripe Link configured or the 402 challenge specifies `method=\"stripe\"`, use `link-cli mpp pay` (the `stripe-link-cli` skill). Otherwise `mppx` for one-off paid calls and debugging, and Tempo Wallet when the user wants persistent spend controls.\n\n## Prerequisites\n\n- Node.js 20+ on `PATH`\n- A funded wallet (Tempo \u002F Privy \u002F AgentCash) OR an `mppx` account\n- For Tempo \u002F Privy \u002F AgentCash: follow their respective onboarding skills:\n  - `https:\u002F\u002Ftempo.xyz\u002FSKILL.md`\n  - `https:\u002F\u002Fagents.privy.io\u002Fskill.md`\n  - `https:\u002F\u002Fagentcash.dev\u002Fskill.md`\n\nUse `web_extract` to fetch any of those SKILL.md files if the user picks one.\n\n## Procedure (mppx, fastest path)\n\nRun all commands through the `terminal` tool.\n\n### 1. Install + create an account\n\n```\nnpm install -g mppx\nmppx account create\n```\n\nStore the resulting account credentials wherever the CLI tells you (the CLI writes them under its own config — do not paste them into the agent transcript).\n\n### 2. Inspect the merchant's 402 challenge\n\nIf the user gives you a URL, probe it first to confirm it actually speaks MPP:\n\n```\ncurl -i \u003Curl>\n```\n\nA real MPP 402 looks like:\n\n```\nHTTP\u002F1.1 402 Payment Required\nwww-authenticate: tempo amount=0.1 currency=...\n```\n\n### 3. Pay the request\n\n```\nmppx \u003Curl>\n```\n\nFor non-GET methods or request bodies:\n\n```\nmppx \u003Curl> --method POST --data '\u003Cjson>'\n```\n\n`mppx` handles the 402 challenge\u002Fcredential dance automatically and prints the merchant's actual response on success.\n\n### 4. Verify the receipt\n\n`mppx` attaches the receipt header automatically. To inspect:\n\n```\nmppx \u003Curl> -v\n```\n\n## Procedure (Tempo Wallet)\n\nThe Tempo Wallet skill at https:\u002F\u002Ftempo.xyz\u002FSKILL.md is the canonical reference; fetch it with `web_extract` and follow it. Headline:\n\n```\ntempo wallet login\ntempo wallet pay \u003Curl>\n```\n\nSpend controls and service discovery live in the wallet UI at https:\u002F\u002Fwallet.tempo.xyz.\n\n## Pitfalls\n\n- **`HTTP 402` without `method=\"stripe\"` cannot be paid by Stripe Link.** If the challenge advertises only Tempo \u002F other methods, use `mppx` (or whichever wallet matches) — Link will reject it. Conversely, if it advertises `method=\"stripe\"`, prefer Link via the `stripe-link-cli` skill so the spend goes through the user's approved card.\n- **Multiple challenges in one header.** `www-authenticate` may list several methods (e.g. `tempo, stripe`). The Link CLI's `mpp decode` will pick the Stripe one; `mppx` will pick Tempo. There's no single \"right\" client — pick by which wallet the user has funded.\n- **Zero-amount challenges.** Some MPP endpoints charge `$0.00` and just want a proof credential. These work without a funded wallet. Don't refuse them as \"broken.\"\n- **Wallet keys never enter agent context.** All four clients store keys under their own config dirs (or generate per-session ephemeral keypairs, in Privy's case). Do not `cat`\u002F`read_file` them.\n- **Server-side MPP is a different skill.** If the user wants to ADD 402 to their own API, this skill is wrong — point them at https:\u002F\u002Fmpp.dev\u002Fquickstart\u002Fserver and the `mppx\u002Fnextjs` \u002F `mppx\u002Fhono` \u002F `mppx\u002Fexpress` \u002F `mppx\u002Felysia` middlewares. A dedicated `mpp-server` skill may land later.\n\n## Verification\n\n```\nmppx --version && mppx account list\n```\n\nExit code 0 means installed and an account exists.\n","# MPP Agent Skill\n\nWraps the Machine Payments Protocol (MPP, https:\u002F\u002Fmpp.dev) clients so Hermes can pay for per-request API access against servers that respond with `HTTP 402 Payment Required`.\n\nThree client options, all distributed via npm. Pick the lightest one that solves the user's need. Gated `[linux, macos]` while the broader payments tooling matures on Windows.\n\n## When to Use\n\n- A merchant API returns `HTTP 402` with a `www-authenticate` header — and the user wants to actually pay it, not just log the response.\n- The user asks to \"pay per request\", \"set up an agent wallet\", \"use Tempo \u002F Privy \u002F AgentCash\", or wants to discover MPP-priced services.\n- A Stripe Link spend has produced a Shared Payment Token (SPT) and the agent needs to attach it to the 402 challenge — in that flow, prefer `link-cli mpp pay` (see the `stripe-link-cli` skill).\n\n## Choosing a client\n\n| Tool | When | Setup |\n|---|---|---|\n| `link-cli` | User already has Stripe Link set up, or the 402 challenge advertises `method=\"stripe\"` | see the `stripe-link-cli` skill |\n| Tempo Wallet | MPP services with spend controls, service discovery | `tempo wallet login` |\n| Privy Agent CLI | Multi-chain wallets, browser-based funding | `privy-agent-wallets login` |\n| AgentCash | 300+ pre-priced APIs via one USDC.e balance | `npx agentcash onboard` |\n| `mppx` | Dev + debugging, smallest dep surface | `npm install -g mppx` then `mppx account create` |\n\nDefault: if the user already has Stripe Link configured or the 402 challenge specifies `method=\"stripe\"`, use `link-cli mpp pay` (the `stripe-link-cli` skill). Otherwise `mppx` for one-off paid calls and debugging, and Tempo Wallet when the user wants persistent spend controls.\n\n## Prerequisites\n\n- Node.js 20+ on `PATH`\n- A funded wallet (Tempo \u002F Privy \u002F AgentCash) OR an `mppx` account\n- For Tempo \u002F Privy \u002F AgentCash: follow their respective onboarding skills:\n  - `https:\u002F\u002Ftempo.xyz\u002FSKILL.md`\n  - `https:\u002F\u002Fagents.privy.io\u002Fskill.md`\n  - `https:\u002F\u002Fagentcash.dev\u002Fskill.md`\n\nUse `web_extract` to fetch any of those SKILL.md files if the user picks one.\n\n## Procedure (mppx, fastest path)\n\nRun all commands through the `terminal` tool.\n\n### 1. Install + create an account\n\n```\nnpm install -g mppx\nmppx account create\n```\n\nStore the resulting account credentials wherever the CLI tells you (the CLI writes them under its own config — do not paste them into the agent transcript).\n\n### 2. Inspect the merchant's 402 challenge\n\nIf the user gives you a URL, probe it first to confirm it actually speaks MPP:\n\n```\ncurl -i \u003Curl>\n```\n\nA real MPP 402 looks like:\n\n```\nHTTP\u002F1.1 402 Payment Required\nwww-authenticate: tempo amount=0.1 currency=...\n```\n\n### 3. Pay the request\n\n```\nmppx \u003Curl>\n```\n\nFor non-GET methods or request bodies:\n\n```\nmppx \u003Curl> --method POST --data '\u003Cjson>'\n```\n\n`mppx` handles the 402 challenge\u002Fcredential dance automatically and prints the merchant's actual response on success.\n\n### 4. Verify the receipt\n\n`mppx` attaches the receipt header automatically. To inspect:\n\n```\nmppx \u003Curl> -v\n```\n\n## Procedure (Tempo Wallet)\n\nThe Tempo Wallet skill at https:\u002F\u002Ftempo.xyz\u002FSKILL.md is the canonical reference; fetch it with `web_extract` and follow it. Headline:\n\n```\ntempo wallet login\ntempo wallet pay \u003Curl>\n```\n\nSpend controls and service discovery live in the wallet UI at https:\u002F\u002Fwallet.tempo.xyz.\n\n## Pitfalls\n\n- **`HTTP 402` without `method=\"stripe\"` cannot be paid by Stripe Link.** If the challenge advertises only Tempo \u002F other methods, use `mppx` (or whichever wallet matches) — Link will reject it. Conversely, if it advertises `method=\"stripe\"`, prefer Link via the `stripe-link-cli` skill so the spend goes through the user's approved card.\n- **Multiple challenges in one header.** `www-authenticate` may list several methods (e.g. `tempo, stripe`). The Link CLI's `mpp decode` will pick the Stripe one; `mppx` will pick Tempo. There's no single \"right\" client — pick by which wallet the user has funded.\n- **Zero-amount challenges.** Some MPP endpoints charge `$0.00` and just want a proof credential. These work without a funded wallet. Don't refuse them as \"broken.\"\n- **Wallet keys never enter agent context.** All four clients store keys under their own config dirs (or generate per-session ephemeral keypairs, in Privy's case). Do not `cat`\u002F`read_file` them.\n- **Server-side MPP is a different skill.** If the user wants to ADD 402 to their own API, this skill is wrong — point them at https:\u002F\u002Fmpp.dev\u002Fquickstart\u002Fserver and the `mppx\u002Fnextjs` \u002F `mppx\u002Fhono` \u002F `mppx\u002Fexpress` \u002F `mppx\u002Felysia` middlewares. A dedicated `mpp-server` skill may land later.\n\n## Verification\n\n```\nmppx --version && mppx account list\n```\n\nExit code 0 means installed and an account exists.\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"platforms":36,"description":7},"Teknium (teknium1), Hermes Agent","0.1.0",{"mercury":26},{"tags":27,"related_skills":33},[28,29,30,31,32],"Payments","MPP","HTTP-402","Tempo","Stripe",[34,35],"stripe-link-cli","stripe-projects",[37,38],"linux","macos","main","94a12cab2ce32e2020d179b5d579d0cbcbd0f206","hermes\u002Foptional-skills\u002Fpayments\u002Fmpp-agent","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury","https:\u002F\u002Fgithub.com\u002Ffengwhang","2026-10-09 08:26:42",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add fengwhang\u002Fmercury --skill mpp-agent",{"tool":51,"command":52},"bunx","bunx skills add fengwhang\u002Fmercury --skill mpp-agent",{"tool":54,"command":55},"pnpm","pnpm dlx skills add fengwhang\u002Fmercury --skill mpp-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fhermes\u002Foptional-skills\u002Fpayments\u002Fmpp-agent\u002FSKILL.md",true,[],[60,67,74,81,87,94],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7C4BTY3ND38CN200ZCTH6NV","greet","A greeting skill for testing","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Fmarketplace\u002Ffixtures\u002Fvalid-marketplace\u002Fplugins\u002Fhello-plugin\u002Fskills\u002Fgreet\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7C4BSNZTPW8JR5NGCQXGSEZ","valid-skill","A valid skill for testing purposes.","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Fvalid-skill\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7C4BRA7J8C06KSVW100F1W1","unknown-field","A skill with an unknown frontmatter field.","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Funknown-field\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7C4BNB04KQGCJ835JE8AR13","no-frontmatter","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Fno-frontmatter\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7C4BM38TZFYT1AJ6SKHPZZ2","child-skill","A nested skill in a subdirectory.","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Fnested\u002Fchild-skill\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7C4BJDN7RFFCM28CGX15Q97","different-name","A skill with a name that doesn't match the directory.","https:\u002F\u002Fgithub.com\u002Ffengwhang\u002Fmercury\u002Fblob\u002Fmain\u002Fomp\u002Fpackages\u002Fcoding-agent\u002Ftest\u002Ffixtures\u002Fskills\u002Fname-mismatch\u002FSKILL.md",[],[]]