paysh-catalog

Index pay.sh catalog entries with costs, intents, and upstream URLs.

270|65|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/sepivip/SeekerClaw --skill paysh-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paysh-catalog
Source: https://github.com/sepivip/SeekerClaw/tree/main/app/src/main/assets/default-skills/paysh-catalog
Command: npx skills add https://github.com/sepivip/SeekerClaw --skill paysh-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

paysh-catalog provides a formal, discoverable catalog of pay.sh services payable via agent_pay, consolidating costs, intents, and docs for safer shopping in a paid AI assistant context.

Core Features & Use Cases

  • Centralized discovery of payable endpoints across multiple operators with per-call costs and documentation.
  • Clear decision-making prompts for users by showing costs, intents, and upstream URLs before paying.
  • Safe onboarding for new users by offering opt-in only flows and auditable provenance.

Quick Start

Query the paysh-catalog to browse and select payable services by cost and capability.

Frequently Asked Questions about paysh-catalog

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

FAQPage Schema
How do I discover payable services and their per-call costs before making an agent payment?

To discover payable services and their per-call costs, you can query a catalog that indexes pay.sh entries to surface costs, intents, and documentation. This allows you to review per-call pricing and capabilities before committing to any agent payment.

What is a pay.sh catalog and how does it help with safe service discovery?

A pay.sh catalog is a formalized index of services payable via agent_pay that helps with safe service discovery by exposing canonical metadata, upstream URLs, and provenance. It applies strong validation checks before any paid invocation to ensure safe onboarding.

How do I browse multi-endpoint services across operators to compare costs and intents?

You browse multi-endpoint services across operators by querying a centralized discovery index that consolidates operator entries. This surfaces per-call costs, intents, and documentation to help you compare and select payable services by cost and capability.

Can I see documentation and upstream URLs for payable endpoints before authorizing a transaction?

Yes, you can see documentation and upstream URLs for payable endpoints before authorizing a transaction. The catalog surfaces this canonical metadata to provide clear decision-making prompts, ensuring you know the cost and intent before paying.

Does the pay.sh catalog support opt-in flows for auditing service provenance?

Yes, the pay.sh catalog supports opt-in only flows for auditing service provenance. It exposes canonical metadata and provenance with strong validation checks, ensuring safe onboarding for new users before any paid invocation occurs.