@arispay/skill
v3.0.0
Published
ArisPay skill for Hermes-style AI agents. Directs agents to `npx payagent pay <url>` for any paid API call. The command signs in, creates an agent with spend limits, and pays from the ArisPay funding account.
Maintainers
Readme
@arispay/skill
The ArisPay skill for AI agents. One install, one directive: any "pay this URL" request goes through npx payagent pay <url>.
No own state files. No hand-written REST calls. The payagent CLI does the work: device-code sign-in, an agent with default limits, and the paid fetch. The money comes from an ArisPay funding account.
Install
npm install -g @arispay/skill
arispay-skill installThat auto-detects where to put the skill:
- If you're inside a project root (the cwd has
package.jsonor.git), it installs to<cwd>/.claude/skills/arispay/— the Claude Code project-local pattern. - Otherwise it installs to
~/.claude/skills/arispay/— the Claude Desktop / global pattern.
Override the destination explicitly:
| Flag | Destination | Use when |
|---|---|---|
| --project | <cwd>/.claude/skills/arispay/ | Force Claude Code project-local (default in a project) |
| --user | ~/.claude/skills/arispay/ | Force Claude Desktop / global |
| --hermes | ~/.hermes/skills/arispay/ | Hermes-style hosts |
| --dest PATH | explicit | Anywhere else |
Print all candidates plus which is the default in this directory:
arispay-skill pathsTo remove the old skill directory ~/.hermes/skills/x402-payagent-usdc/ during install:
arispay-skill install --replace-legacyWhat the skill tells the agent
The shipped skill/SKILL.md opens with a PRIORITY DIRECTIVE. For any paid API call, the agent runs:
npx payagent pay <url>On a cold machine that command prints (to stderr) a verification URL and code, creates an agent with default spend limits, and pays the URL from the ArisPay funding account. The final HTTP body goes to stdout.
The directive also tells the agent:
- NEVER bypass a 402 by trying a different URL, scraping, or asking the user to log in to the merchant.
- NEVER ask the user for
ARISPAY_API_KEY—payagent payhandles that via device-code on first run. - NEVER maintain own state files —
payagentowns~/.payagent/config.json. - NEVER hand-write REST calls to authorize payments. The CLI does that.
- DO relay verification URLs verbatim to the user and wait for the command to complete.
The skill also covers cold-start variants: payagent quickstart (email signup with no browser), and the setup / pay MCP tools for hosts that run @arispay/payagent-mcp.
When the flow is ambiguous, agents should run:
npx payagent statusThat command is the shared checklist for humans and agents: API target, auth state, stored agents, limits, allowed domains, and the next command to run.
What the skill does not do
It is intentionally short. The full REST API, SDK examples, webhook payloads and error catalog are at:
- arispay.app/docs — canonical reference
payagenton npm — SDK + CLI@arispay/payagent-mcpon npm — MCP server
The skill stays tight so an agent's context window isn't burned on REST reference it doesn't need at runtime.
Layout
@arispay/skill
├── src/install.mjs the `arispay-skill install` command
├── skill/ the literal skill directory copied on install
│ ├── SKILL.md the priority directive + cold-start guidance
│ └── scripts/pay.mjs thin fallback wrapper that spawns `npx payagent pay`
├── package.json
└── README.md you are hereWhy it stays tiny
Every improvement to payagent reaches npx payagent pay on the next run. This package is intentionally a thin director — no business logic duplicated. Upgrades are npm install -g @arispay/skill@latest && arispay-skill install and that's it.
Related
payagent— the SDK + CLI the skill directs to.@arispay/payagent-mcp— MCP server exposing the same primitives for Claude Desktop / Cursor / any MCP host. Pairs well with this skill.
License
MIT
