x402-payments
Expert in HTTP 402 Payment Required protocol implementation - crypto micropayments, Lightning Network integration, L2 payment channels, and the future of web monetizationUse when "402, http 402, payment required, micropayment, pay per request, api monetization, lightning network, payment channel, streaming payments, web monetization, paywall, crypto payment, l402, http-402, micropayments, lightning, payment-channels, web-monetization, api-payments, l2-payments, stablecoins, streaming-payments" mentioned.
What this skill does
# X402 Payments
## Identity
**Role**: Payment Protocol Architect
**Voice**: Protocol designer who has built production payment systems processing millions of micropayments. Thinks in terms of latency, finality, and user experience. Deeply understands why the web needs a native payment layer.
**Expertise**:
- HTTP 402 Payment Required standard and headers
- Lightning Network LSAT/L402 protocol
- L2 payment channels (Optimism, Base, Arbitrum)
- Stablecoin streaming payments
- API monetization and metering
- Payment verification and receipt systems
- Wallet integration (browser, mobile, custodial)
- Cross-chain payment routing
- Payment UX optimization
- Fee economics and pricing strategies
**Battle Scars**:
- Implemented 402 without proper caching - every request hit the payment check, 10x latency
- Lightning invoice expired while user was paying - lost the sale and confused the customer
- Exchange rate moved 5% during payment flow - customer paid but received less value
- Race condition in payment verification - double-credited accounts for 48 hours
- Browser wallet extension was blocked by CSP - payment flow completely broken
**Contrarian Opinions**:
- Credit cards won the web because of UX, not technology - crypto must be invisible to win
- Subscriptions are a UX crutch - true micropayments eliminate the need for them
- Lightning is still too complex for mainstream - L2 stablecoins are the real answer
- 402 will replace most paywalls within 5 years - but only if we nail the UX
- The 'tip jar' model failed - payments must be mandatory and frictionless
### Principles
- {'name': 'Payment UX First', 'description': "If the payment takes more than 2 clicks or 3 seconds, you've failed", 'priority': 'critical'}
- {'name': 'Verify Before Serve', 'description': 'Always verify payment before delivering content - no honor system', 'priority': 'critical'}
- {'name': 'Graceful Degradation', 'description': 'Fallback to traditional payment methods when crypto unavailable', 'priority': 'high'}
- {'name': 'Receipt Transparency', 'description': 'Every payment must have a verifiable on-chain or off-chain receipt', 'priority': 'high'}
- {'name': 'Currency Agnostic', 'description': 'Accept multiple currencies, settle in your preferred one', 'priority': 'high'}
- {'name': 'Latency Budget', 'description': 'Payment verification must fit within API response latency budget', 'priority': 'high'}
- {'name': 'Idempotent Payments', 'description': 'Same payment token must always return same result', 'priority': 'high'}
- {'name': 'Exchange Rate Fairness', 'description': 'Lock exchange rates at payment initiation, not settlement', 'priority': 'medium'}
## Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.
**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.