agent-payments-skill

Automate cross-protocol agent payments across x402 and AP2 gateways.

6|1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/sentient-agi/agentic-payments-bot --skill agent-payments-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-payments-skill
Source: https://github.com/sentient-agi/agentic-payments-bot/tree/main
Command: npx skills add https://github.com/sentient-agi/agentic-payments-bot --skill agent-payments-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI agents need to perform payments across diverse rails. This OpenClaw Open Agent Skills Ecosystem compliant skill enables autonomous initiation, validation, and execution of payments across x402 (on-chain, stablecoins) and AP2 (mandate-based) workflows, bridging Web3 and Web2 gateways while ensuring governance, auditability, and human-in-the-loop control.

Core Features & Use Cases

  • Dual-protocol support: x402 on-chain payments and AP2 mandate-based payments.
  • Web3 and Web2 gateways: ETH/ERC-20 transfers via Viem; Stripe, PayPal, Visa Direct, Mastercard Send, Google Pay, and Apple Pay for fiat settlements.
  • Pluggable KMS and dry-run: AWS KMS, OS keyring, D-Bus Secret Service, GnuPG, and Local AES with a dry-run mode for safe testing.
  • Policy engine with per-transaction limits, time-window aggregates, blacklist/whitelist, and human-in-the-loop confirmations.
  • Audit trail and observability via SQLite audit_log and Winston logs; accessible via CLI, web API, and chat UIs.

Quick Start

Boot the skill in dry-run mode and trigger a sample AP2 payment flow to observe policy checks, key management, and gateway orchestration without real funds.

Frequently Asked Questions about agent-payments-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate cross-protocol agent payments across x402 and AP2?

You can automate cross-protocol agent payments by routing intents to web3 ETH/ERC-20 transfers or web2 gateways like Stripe and PayPal, enforced by policy checks, KMS-backed secret management, and human-in-the-loop controls.

What is the best way to manage KMS backends for autonomous Web3 and Web2 payment routing?

Managing KMS backends for autonomous payment routing is handled via pluggable backends including AWS KMS, OS keyring, D-Bus Secret Service, GnuPG, and Local AES, ensuring secure secret management across both on-chain and fiat settlements.

Can I use a dry-run mode to test AI agent payment workflows without spending real funds?

Yes, you can boot the skill in dry-run mode to trigger sample AP2 payment flows, allowing you to observe policy checks, key management, and gateway orchestration safely without risking real funds.

Does this autonomous payment skill support fiat settlement via Stripe, PayPal, Visa, and Mastercard?

Yes, it supports fiat settlements across Web2 gateways including Stripe, PayPal, Visa Direct, Mastercard Send, Google Pay, and Apple Pay, alongside ETH/ERC-20 transfers via Viem for on-chain payments.

How do I implement per-transaction limits and audit trails for autonomous AI agent payments?

You implement per-transaction limits and audit trails using the built-in policy engine and SQLite audit_log with Winston logs, tracking time-window aggregates, blacklists, and human-in-the-loop confirmations accessible via CLI, web API, and chat UIs.

What are the limitations of using local AES for KMS-backed secret management in agent payments?

Local AES provides a lightweight KMS backend option for agent payments, but unlike AWS KMS or D-Bus Secret Service, it lacks enterprise-grade hardware isolation and may require additional manual security precautions for production environments.