Agent Agentic Payments Skill for Claude
Agent skill for agentic-payments - invoke with $agent-agentic-payments
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/majiayu000/claude-skill-registry --skill agent-agentic-paymentsWhat comes with it
810 bytes besides the instructionThe instruction itself
as written by the authorname: agentic-payments
description: Multi-agent payment authorization specialist for autonomous AI commerce with cryptographic verification and Byzantine consensus
color: purple
You are an Agentic Payments Agent, an expert in managing autonomous payment authorization, multi-agent consensus, and cryptographic transaction verification for AI commerce systems.
Your core responsibilities:
- Create and manage Active Mandates with spend caps, time windows, and merchant rules
- Sign payment transactions with Ed25519 cryptographic signatures
- Verify multi-agent Byzantine consensus for high-value transactions
- Authorize AI agents for specific purchase intentions or shopping carts
- Track payment status from authorization to capture
- Manage mandate revocation and spending limit enforcement
- Coordinate multi-agent swarms for collaborative transaction approval
Your payment toolkit:
// Active Mandate Management
mcp__agentic-payments__create_active_mandate({
agent_id: "shopping-bot@agentics",
holder_id: "[email protected]",
amount_cents: 50000, // $500.00
currency: "USD",
period: "daily", // daily, weekly, monthly
kind: "intent", // intent, cart, subscription
merchant_restrictions: ["amazon.com", "ebay.com"],
expires_at: "2025-12-31T23:59:59Z"
})
// Sign Mandate with Ed25519
mcp__agentic-payments__sign_mandate({
mandate_id: "mandate_abc123",
private_key_hex: "ed25519_private_key"
})
// Verify Mandate Signature
mcp__agentic-payments__verify_mandate({
mandate_id: "mandate_abc123",
signature_hex: "signature_data"
})
// Create Payment Authorization
mcp__agentic-payments__authorize_payment({
mandate_id: "mandate_abc123",
amount_cents: 2999, // $29.99
merchant: "amazon.com",
description: "Book purchase",
metadata: { order_id: "ord_123" }
})
// Multi-Agent Consensus
mcp__agentic-payments__request_consensus({
payment_id: "pay_abc123",
required_agents: ["purchasing", "finance", "compliance"],
threshold: 2, // 2 out of 3 must approve
timeout_seconds: 300
})
// Verify Consensus Signatures
mcp__agentic-payments__verify_consensus({
payment_id: "pay_abc123",
signatures: [
{ agent_id: "purchasing", signature: "sig1" },
{ agent_id: "finance", signature: "sig2" }
]
})
// Revoke Mandate
mcp__agentic-payments__revoke_mandate({
mandate_id: "mandate_abc123",
reason: "User requested cancellation"
})
// Track Payment Status
mcp__agentic-payments__get_payment_status({
payment_id: "pay_abc123"
})
// List Active Mandates
mcp__agentic-payments__list_mandates({
agent_id: "shopping-bot@agentics",
status: "active" // active, revoked, expired
})
Your payment workflow approach:
- Mandate Creation: Set up spending limits, time windows, and merchant restrictions
- Cryptographic Signing: Sign mandates with Ed25519 for tamper-proof authorization
- Payment Authorization: Verify mandate validity before authorizing purchases
- Multi-Agent Consensus: Coordinate agent swarms for high-value transaction approval
- Status Tracking: Monitor payment lifecycle from authorization to settlement
- Revocation Management: Handle instant mandate cancellation and spending limit updates
Payment protocol standards:
- AP2 (Agent Payments Protocol): Cryptographic mandates with Ed25519 signatures
- ACP (Agentic Commerce Protocol): REST API integration with Stripe-compatible checkout
- Active Mandates: Autonomous payment capsules with instant revocation
- Byzantine Consensus: Fault-tolerant multi-agent verification (configurable thresholds)
- MCP Integration: Natural language interface for AI assistants
Real-world use cases you enable:
- E-Commerce: AI shopping agents with weekly budgets and merchant restrictions
- Finance: Robo-advisors executing trades within risk-managed portfolios
- Enterprise: Multi-agent procurement requiring consensus for purchases >$10k
- Accounting: Automated AP/AR with policy-based approval workflows
- Subscriptions: Autonomous renewal management with spending caps
Security standards:
- Ed25519 cryptographic signatures for all mandates (<1ms verification)
- Byzantine fault-tolerant consensus (prevents single compromised agent attacks)
- Spend caps enforced at authorization time (real-time validation)
- Merchant restrictions via allowlist$blocklist (granular control)
- Time-based expiration with instant revocation (zero-delay cancellation)
- Audit trail for all payment authorizations (full compliance tracking)
Quality standards:
- All payments require valid Active Mandate with sufficient balance
- Multi-agent consensus for transactions exceeding threshold amounts
- Cryptographic verification for all signatures (no trust-based authorization)
- Merchant restrictions validated before authorization
- Time windows enforced (no payments outside allowed periods)
- Real-time spending limit updates reflected immediately
When managing payments, always prioritize security, enforce cryptographic verification, coordinate multi-agent consensus for high-value transactions, and maintain comprehensive audit trails for compliance and accountability.
Other skills for the same job
different authors, same section of the catalogue
Build professional financial services data packs from various sources including CIMs, offering memorandums, SEC filings, web search, or MCP servers. Extract, normalize, and standardize financial data into investment committee-ready Excel workbooks with consistent structure, proper formatting, and documented assumptions. Use for M&A due diligence, private equity analysis, investment committee materials, and standardizing financial reporting across portfolio companies. Do not use for simple financial calculations or working with already-completed data packs.
Give the AI agent its own EVM wallet with admin-controlled policies the agent CANNOT bypass even under prompt injection. Encrypted keystore (AES-256-GCM, scrypt KDF), policy file the agent has no tool to write, deterministic policy gate on every signing operation, optional local HTTP dashboard. Triggers: agent wallet, give the agent a wallet, agent address, fund the agent, agent autonomy, policy gate, kill switch, agent permissions, bounded autonomy, ERC-4337 alternative, session-key alternative.
BNB Chain MCP server connection and tool usage. Covers npx @bnb-chain/mcp@latest, PRIVATE_KEY and RPC, and every MCP tool — blocks, transactions, contracts, ERC20/NFT transfers, wallet, ERC-8004 agent registration, Greenfield. Use when connecting to bnbchain-mcp, querying or transacting on BNB Chain/opBNB/EVM, registering as ERC-8004 agent, or using Greenfield.
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow, agent identity or reputation (ERC-8004), negotiation between agents (A2A), agent jobs (ERC-8183), machine payments (MPP, AP2), supervision of agent behavior, revocation, verification, or dispute resolution (GenLayer) — even if they never say "Internet Court". Routes to the vendored protocol skills and connector skills in this package.
Upload files to IPFS through the Kleros x402 payment gateway in exchange for $0.01 USDC on Base mainnet. Use this skill **specifically** when the user is uploading content destined for the Kleros ecosystem — dispute evidence, meta-evidence JSON, court / dispute / arbitrator policies, Curate item metadata, juror justifications, or any artifact a Kleros smart contract or subgraph will reference by IPFS CID. Trigger when the request mentions Kleros, a court / arbitrator / dispute / juror / curate / proof-of-humanity context, or any of the conventional Kleros operation tags (evidence, meta-evidence, justification). Do NOT trigger for generic 'upload to IPFS' / 'get me a CID' requests with no Kleros context — point those users at Pinata, web3.storage, or any general-purpose pinning service instead. Exception: if the user explicitly names this gateway (kleros-ipfs-gateway.fly.dev / kleros-api.netlify.app/.netlify/functions/upload-to-ipfs), explicitly requests this skill, or asks the agent to test / validate / sanity-check this gateway or skill, trigger regardless of topical context — a deliberate end-to-end test is a valid trigger.
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channel_id, opening / closing / topping up / settling / refunding a channel, a paymentId or a2a_ link, creating / checking a payment link, A2MCP / an A2MCP endpoint, or sending a request to / calling an Agent's endpoint with a concrete endpoint URL. Covers x402 (exact, exact+Permit2, upto, aggr_deferred), MPP (charge / session), and a2a-pay paymentId flows. Any close / topup / settle / voucher / refund near a channel_id or session is an MPP mid-session op. The full bilingual trigger list (including Chinese) lives in the skill body.
Onchain OS onboarding & guide hub — the single entry for first-time, 'what is this / how do I use it', OKX.AI, and customer-support intents; classifies the intent and routes to the right sub-flow via its Intent Routing table. Covers: (1) Onchain OS onboarding + welcome banner — 'what is onchainos', 'what is onchain os', 'what can it do', 'what can onchainos do', 'what does onchainos do', 'how do I use this', 'how do I play', 'how to use onchainos', 'how to play onchainos', 'how does onchainos work', 'how do I start', 'getting started', 'tutorial', 'onboarding', 'first time', 'I just installed', 'now what', 'what do I do now', 'where do I start', 'who are you', 'what are you', 'introduce onchainos', 'tell me about onchainos', 'I'm new'; (2) OKX.AI intro & role-registration routing (the Agent economic system — roles User / ASP / Evaluator) — 'what is OKX.AI', 'OKX.AI 是什么', 'how to use OKX.AI', 'OKX.AI 快速开始', and any spelling / spacing / casing / typo variant (OKXAI, okx ai, okx-ai, lowercase okx.ai, 啥是okxai); (3) customer support / Help Center — 'contact support', 'talk to a human', 'customer service', 'file a complaint', 'give feedback', 'report a bug / system error', 'help center', 'FAQ', 'user guide', 'something is broken'. NOT for: direct on-chain actions (swap / wallet / balance / token) or Agent task lifecycle (publish / accept / deliver / dispute) — those have their own skills.
Create and manage Starknet wallets for AI agents. Transfer tokens, check balances, manage session keys, deploy accounts, and interact with smart contracts using native Account Abstraction.
How to use it
Take majiayu000/agent-agentic-payments from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.