
Three.Ws Agent Payments
- 89 repo stars
- Updated July 28, 2026
- nirholas/three.ws
Creates governed x402 payment sessions with a budget, endpoint allowlist, and per-transaction caps so an agent can pay any x402 endpoint without holding a raw key.
About
three.ws Agent Payments is an MCP server that lets an agent pay any x402 endpoint through governed payment sessions: you create a session with a budget, an endpoint allowlist, and per-transaction caps, then the agent spends against a session bearer token (pss_...) instead of a raw key. Payments settle on-chain. A solo builder reaches for it to give an agent bounded, auditable spending power for machine-to-machine payments.
- Governed x402 payment sessions
- Budget, allowlist, and per-tx caps
- Session bearer token instead of raw key
- On-chain settlement
Three.Ws Agent Payments by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
claude mcp add --env THREE_WS_SESSION=YOUR_THREE_WS_SESSION --env PAYMENT_SESSION_TOKEN=YOUR_PAYMENT_SESSION_TOKEN --env THREE_WS_BASE=YOUR_THREE_WS_BASE --env THREE_WS_TIMEOUT_MS=YOUR_THREE_WS_TIMEOUT_MS agentcore-payments-mcp -- npx -y @three-ws/agentcore-payments-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 89 |
|---|---|
| Package | @three-ws/agentcore-payments-mcp |
| Transport | STDIO |
| Auth | Required |
| Last updated | July 28, 2026 |
| Repository | nirholas/three.ws ↗ |
What it does
Creates governed x402 payment sessions with a budget, endpoint allowlist, and per-transaction caps so an agent can pay any x402 endpoint without holding a raw key.
Who is it for?
bounded agent-driven machine payments
Skip if: traditional card checkout flows
What you get
- payment sessions
- governed payments