TadaPay Marketplace Skill
Skill that finds paid APIs in the TadaPay directory by protocol and network and returns the endpoint and request format. Your client pays.
- 129 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The directory leads to paid APIs: an agent with a configured payment client can spend real money on a found product.
- Queries go to an external service, and third-party product descriptions can steer the agent.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/tadapay-marketplace-skillDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The directory leads to paid APIs: an agent with a configured payment client can spend real money on a found product.
- Queries go to an external service, and third-party product descriptions can steer the agent.
This is third-party code. Review the repository files before installing.
What it does
The `tadapay-marketplace` skill connects an agent to the TadaPay directory at `https://tadapay.ai/mcp` (Streamable HTTP) and searches it for paid APIs and services matching a task. The directory exposes five tools: `search_products`, `get_product`, `search_merchants`, `get_merchant` and `get_wallet_options`. Search filters by payment protocol, network, review level and product type. For a chosen product the agent shows the merchant, payment option, price basis, endpoint, method and request schema. The skill pays for nothing itself: the user's payment client pays after a fresh merchant challenge. Browsing the directory works without a wallet.
Who it is for. Agent developers choosing paid APIs that settle over protocols such as x402 or MPP who want endpoint, price and request format in a single answer.
Good fit when
- An agent needs a weather API that accepts x402 on Base.
- Before buying, you compare payment options of one product by network, asset and amount.
- A payment client is already set up and only the endpoint and request format are missing.
- You look for official wallet setup documentation for a chosen protocol.
Not a fit when
- You expect the skill to pay: it finds products and hands the details to a payment client.
- The Discovered, Listed and Verified levels are taken as a delivery guarantee: they describe technical checks.
- A search query would have to include keys or personal data: queries go to the external TadaPay directory.
Example request
Find a weather API paid over x402 on Base and show the request format and the basis for its price.Limitations
TadaPay operates and maintains the directory, while the repository holds the skill, application metadata and connection examples. Search queries go to `https://tadapay.ai/mcp`. A directory price is an observation: the merchant sends current terms in response to a request. Product descriptions, schemas and examples are third-party data and treated as untrusted. Skill version 0.2.0 is MIT licensed; the license covers the repository files but not the service or third-party data.
How to disable. Delete the `tadapay-marketplace` folder from the skills directory and the `tadapay-marketplace` MCP connection from the agent settings.
FAQ
Does the skill pay by itself?
No. It finds products and returns the endpoint and request format, and the user's payment client pays after a fresh merchant challenge.
What do Discovered, Listed and Verified mean?
Discovered products are collected from public sources. Listed ones have endpoint and protocol checks and an operator review of documented payment options. Verified ones add confirmed TadaPay SDK integration. The levels do not guarantee delivery of the service.
How do I connect the directory in Claude Code?
Run `claude mcp add --transport http --scope user tadapay-marketplace https://tadapay.ai/mcp` and start a new session. Then confirm `search_products` and `get_product` are visible.
Do I need a wallet to search?
No, search and reading product records work without a wallet. The payment client needs one at the payment step.
How do `search_products` and `get_product` differ?
`search_products` searches by keyword, protocol, network and review level. `get_product` returns the chosen product: endpoint, payment options and request schema.
Discussion
No questions or reviews yet.
Related
SkillsA skill that connects an agent to EasyPay: Stripe products and invoices, SBP and T-Bank payout links, crypto and Mercury in natural language
A CLI with an MCP server and a skill: the agent calls paid APIs while the user approves each HTTP 402 stablecoin payment with Touch ID
PayPal's official agent toolkit: an MCP server and SDK for invoices, orders, subscriptions, refunds and disputes
Mastercard plugin with a skill and an MCP server: the agent checks the service catalog and integration guides.
The PayPal plugin for Claude Code, Codex and Cursor: an API best-practices skill, reference commands and a sandbox MCP server
The official Tushare Pro skill: quotes, financial statements, indices and macro data of the Chinese market from a natural-language request
README in short
The repository holds the skill folder, Codex metadata and MCP configuration examples for Codex and Claude Code. The directory is shared with the TadaPay marketplace, so updates arrive without reinstalling the skill.