agentleFS
OpenCMCOpenCMC/skills-for-ai-agents-by-CoinMarketCap/skills/cmc-x402/SKILL.md

cmc-x402

Skill75 starsChanged 24 days agoMITView on GitHub

Access CoinMarketCap data via x402 pay-per-request protocol with USDC payments on Base. Use when users mention x402, want CMC data without API keys, ask about pay-per-request APIs, or need to integrate CMC with on-chain payments. Also use for any Coinbase x402 protocol questions. Trigger: "x402", "pay per request", "no API key", "USDC payment", "CMC without subscription", "/cmc-x402"

  • Reads credentials
  • Installs packages

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before using x402 endpoints, ensure you have:

    line 22
  2. Very specific:

    Use /x402/v3/cryptocurrency/quotes/latest with symbol or id parameter.

    line 32
  3. Very specific:

    Use /x402/v3/cryptocurrency/listing/latest with limit parameter.

    line 36
  4. Very specific:

    Use /x402/v1/dex/search with keyword parameter.

    line 40
  5. Very specific:

    Use /x402/v4/dex/pairs/quotes/latest with pair address.

    line 44
  6. Very specific:

    Use the MCP endpoint at https://mcp.coinmarketcap.com/x402/mcp.

    line 48
  7. Distinctive:

    All parameters from the standard CMC Pro API work with x402 endpoints.

    line 98

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CoinMarketCap x402

Pay-per-request crypto market data powered by the x402 protocol. Access CoinMarketCap endpoints instantly with on-chain USDC payment. No API key or subscription required.

What is x402?

x402 is an open payment protocol developed by Coinbase that enables automatic stablecoin payments over HTTP. Instead of managing API keys, you pay $0.01 USDC per request on Base. The x402 client library handles payment signing automatically.

Learn more: https://docs.x402.org

Prerequisites

Before using x402 endpoints, ensure you have:

  1. Node.js 18+ and npm installed
  2. Base network wallet with a private key you control
  3. USDC on Base to pay for requests ($0.01 per request)
  4. Small amount of ETH on Base for gas fees

Use Cases

Get current prices for specific coins: Use /x402/v3/cryptocurrency/quotes/latest with symbol or id parameter. Example: Get BTC and ETH prices for a portfolio tracker.

List top cryptocurrencies: Use /x402/v3/cryptocurrency/listing/latest with limit parameter. Example: Display top 100 coins ranked by market cap.

Search for DEX tokens: Use /x402/v1/dex/search with keyword parameter. Example: Find a memecoin by name when you don't know the contract address.

Get DEX pair trading data: Use /x402/v4/dex/pairs/quotes/latest with pair address. Example: Monitor liquidity and volume for a specific Uniswap pool.

AI agent data access: Use the MCP endpoint at https://mcp.coinmarketcap.com/x402/mcp. Example: Let Claude or other LLMs fetch live crypto data with automatic payment.

Quick Start

Install the x402 TypeScript SDK:

npm install @x402/axios @x402/evm viem

Fetch data with automatic payment:

import { createX402AxiosClient } from "@x402/axios";
import { ExactEvmScheme, toClientEvmSigner } from "@x402/evm";
import { privateKeyToAccount } from "viem/accounts";
import { createPublicClient, http } from "viem";
import { base } from "viem/chains";

// SECURITY: Never hardcode private keys in source code.
// Use environment variables: process.env.PRIVATE_KEY
// For production, use a dedicated hot wallet with limited funds.
const account = privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`);
const publicClient = createPublicClient({ chain: base, transport: http() });
const signer = toClientEvmSigner(account, publicClient);

const client = createX402AxiosClient({
  schemes: [new ExactEvmScheme(signer)],
});

const response = await client.get(
  "https://pro.coinmarketcap.com/x402/v3/cryptocurrency/quotes/latest",
  { params: { symbol: "BTC,ETH" } }
);

console.log(response.data);

Endpoints

Base URL: https://pro.coinmarketcap.com

EndpointPathUse For
Quotes/x402/v3/cryptocurrency/quotes/latestCurrent prices for specific coins
Listings/x402/v3/cryptocurrency/listing/latestTop coins by market cap
DEX Search/x402/v1/dex/searchFind DEX tokens by keyword
DEX Pairs/x402/v4/dex/pairs/quotes/latestDEX pair trading data

All parameters from the standard CMC Pro API work with x402 endpoints. See endpoints.md for full parameter reference.

MCP for AI Agents

The x402 MCP endpoint lets AI agents access CMC data with automatic payment.

Connection URL:

https://mcp.coinmarketcap.com/x402/mcp

Transport: Streamable HTTP (POST)

Connect using any MCP client with an x402-aware HTTP transport. The server exposes the same tools as the REST endpoints and supports automatic tool discovery.

Pricing

$0.01 USDC per request on Base (Chain ID: 8453).

Payment only occurs on successful data delivery. If the request fails, no payment is deducted.

References

  • endpoints.md - Full parameter reference for all endpoints
  • payment-details.md - 402 response format, contract addresses, manual integration

Resources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.