Skip to content
cccskills
FreePublished on GitHubEnglish overview

roundhouse-x402

Find services that accept x402 payments, check agent or wallet details, and query payment data through Roundhouse. It also explains how to connect its MCP server or optionally configure its Base facilitator for seller payments.

OriginalShow the original description

Discover x402-paid services and ERC-8004 agent identity via Roundhouse (open catalog, paid SQL, MCP server, rh-x402 CLI), and optionally settle through Roundhouse's Base mainnet facilitator. Use when searching the x402 bazaar/index, vetting a payee or wallet, querying settlement or agent data, configuring Roundhouse MCP, or pointing a paywall at a hosted facilitator on Base.

affaan-m/ECC305,197 stars(GitHub 305,197 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Finding services that accept x402 payments
  • Checking an agent or wallet before payment
  • Querying settlement data with SQL
  • Connecting the Roundhouse MCP server
  • Configuring a Base payment facilitator

Overview

What it does

Use Roundhouse to find services and capabilities that accept x402 payments. The skill also explains how to check ERC-8004 agent information and wallets, and how to look up payment history and related data through the REST API or read-only SQL. It covers connecting the Roundhouse MCP server to a client and using the rh-x402 CLI to check prices, discover services, and call paid URLs. Sellers can also follow an example configuration for using the Roundhouse facilitator on Base to process payments.

When it helps

Use it to review a payee’s information before paying, find services that support x402, or let an agent look up Roundhouse data. Sellers can use it to configure payment facilitation for their paid services on Base. This skill does not replace spending limits or allowlist design.

Example requests

  • “Find web search services in the catalog and compare their prices.”
  • “Check the agent information and payment status for this wallet.”
  • “Show me how to configure Roundhouse MCP and use the Base facilitator.”

Notes

Most API lookups require ROUNDHOUSE_API_KEY, and read-only SQL is paid. Store the key in an environment variable or another secure mechanism; do not put it directly in a prompt or configuration file. rh-x402 signs with a local wallet, and the documented approach does not require pasting a private key. Set a limit for paid calls. If a paid call fails ambiguously, check its payment status before retrying.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt says to protect API keys, set payment limits, and check settlement before retrying.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt names the API key, MCP clients, and CLI installation, but does not cover every setup prerequisite.

Not counted in the score. Rated by AI (OpenAI Codex) as of Nov 18, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md12.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

accessibility

FreeSummary

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

  • Adding descriptive labels to icon-only buttons
  • Reviewing keyboard navigation and modal focus
  • Checking contrast and control sizes
affaan-m/ECC305.8KUpdated Oct 30, 2026

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

  • Investigating failures that appear only inside an agent application
  • Tracing old conversation content leaking into new sessions
  • Checking skipped or falsely claimed tool execution
affaan-m/ECC305.8KUpdated Oct 30, 2026

agent-eval

FreeSummary

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

  • Comparing coding agents on real development tasks
  • Evaluating a new tool or model before adoption
  • Checking performance after agent updates
affaan-m/ECC305.8KUpdated Oct 30, 2026

Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.

  • Define an AI agent’s tool set and input formats
  • Make tool results and next steps easier to interpret
  • Specify safe retries and stopping conditions
affaan-m/ECC305.8KUpdated Oct 30, 2026

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

  • Diagnosing repeated failures in an agent run
  • Investigating loops through the same tool calls
  • Reviewing output degradation as context grows
affaan-m/ECC305.8KUpdated Oct 5, 2026

Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.

  • Diagnosing repeated tool calls with no progress
  • Investigating quality loss as context grows
  • Checking file paths and environment mismatches
affaan-m/ECC305.8KUpdated Oct 30, 2026

See all skills by affaan-m

Report a problem with this skill