agentleFS
mistertechie06mistertechie06/x402-payments-skill/x402-payments/SKILL.md

x402-payments

Skill0 starsChanged 9 months agoNo licenceView on GitHub

Use whenever the user wants to add payments to an API, monetize endpoints, implement x402, handle HTTP 402 responses, create paid APIs, set up crypto paywalls, accept USDC, or build agent payments. Trigger on: x402, 402 Payment Required, paid API, paywall, micropayments, USDC payments, agent payments, monetize API, payment middleware, x402-next, x402-express, x402-fetch, Sentinel, payment router, audit trail, budget caps, payment receipts, facilitator. Also trigger when turning a free API into paid, adding per-request pricing, or building AI agent autonomous payment flows. Covers Base (EVM) and Solana with USDC. Covers Chainlink CRE (Chainlink Runtime Environment) workflows triggered by x402 payments. Trigger also on: Chainlink CRE, CRE workflow, onchain automation with payments, price alerts with x402, Chainlink price feeds with payments, x402 CRE integration, paid CRE workflows, monetize Chainlink workflows. Even without "x402" mentioned — if they want to charge for API access with crypto or build agent payment infrastructure, this skill applies.

  • Reads credentials
  • Installs packages

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. valeo-cash/x402-payments-skill★ 364% same

    Wrote their own version · 2

    1. nirholas/XActions★ 648same name
    2. altananetwork/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.