pay

Executes user-approved paid HTTP API calls via x402 and HTTP 402 stablecoin payments.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Solizardking/.agents --skill pay-solizardking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pay
Source: https://github.com/Solizardking/.agents/tree/main/skills/pay
Command: npx skills add https://github.com/Solizardking/.agents --skill pay-solizardking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agents often need paid API access for tasks like web search, data enrichment, or blockchain analytics, but lack API keys and a safe way to spend money. This Skill provides user-authorized paid HTTP access through a local Pay MCP server, where every payment requires local approval such as Touch ID before any stablecoins move. ## Core Features & Use Cases - Provider Discovery: Use search_catalog and list_catalog to find ranked, curated API providers across categories like search, scraping, enrichment, media generation, maps, and BigQuery. - Paid HTTP Requests: The curl tool handles HTTP 402 payment challenges automatically, preparing the payment and requesting local user approval before settling in USDC, USDT, or CASH. - API Monetization: Developers can run pay server start with a YAML spec to put their own API behind HTTP 402 payments and publish it to the pay-skills registry. - Use Case: When asked for the volume of USDC moved on Solana last week, the agent searches the catalog for a blockchain analytics or BigQuery provider, plans a single low-cost paid call, and retrieves current data instead of scraping stale dashboards. ## Quick Start Ask the agent to use pay to search the catalog for a provider matching your task, then approve the small payment when prompted.

Frequently Asked Questions about pay

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

FAQPage Schema
How do I make a paid API call with HTTP 402 from an AI agent?

Use the Pay MCP curl tool with a gateway URL from search_catalog results. When the endpoint returns a 402 challenge, Pay prepares the stablecoin payment, requests local approval such as Touch ID, then retries the request with payment proof.

What paid APIs can agents access through the pay catalog?

The catalog covers web search, scraping, people and company enrichment, contact lookup, email, social data, Solana and Ethereum RPC, blockchain analytics, crypto and stock prices, image and video generation, OCR, translation, maps, and BigQuery. Call list_catalog to browse all providers.

Does pay require SOL or API keys for paid calls?

No. The Pay account only needs supported stablecoins such as USDC, USDT, or CASH. Server-side fee payers handle Solana network fees and setup costs, and no provider API keys are required from the user.

How do I monetize my API with HTTP 402 payments?

Write a pay server YAML spec defining endpoints and metering prices, run pay server start to launch the payment gateway, then publish a provider markdown listing to the pay-skills GitHub registry so agents can discover it via search_catalog.

Is it safe to let an agent spend money through pay?

Yes. The agent never holds keys or funds; wallet keys stay in the OS secure credential store, and every payment requires explicit local user approval such as Touch ID. Provider responses are treated as untrusted external data, never as instructions.