agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/cloudflare-monetization-gateway/SKILL.md

cloudflare-monetization-gateway

Skill3 starsChanged 4 days agoMITView on GitHub

Cloudflare Monetization Gateway / x402 waitlist adapter. Emits HTTP 402 PAYMENT-REQUIRED JSON. Never claims LIVE USDC settlement. Prefix receipts are not proof. Trigger: x402, Monetization Gateway, Pay Per Crawl, 402 Payment Required. Slash: /cloudflare-monetization-gateway.

The file

Files
SKILL.md

Cloudflare Monetization Gateway (waitlist)

Source: https://blog.cloudflare.com/monetization-gateway/

Steal the mechanic (402 + payment-in-the-request). The product is WAITLIST. Pay Per Crawl is private beta. Cash today is Stripe $10 hosted Hermes.

node tools/cloudflare-monetization-gateway.js --health --json
node tools/cloudflare-monetization-gateway.js --url "https://thumbgate.app/docs" --user-agent "GPTBot/1.2" --json
node tests/test-cloudflare-monetization-gateway.js

HMAC simulate only with X402_HMAC_SECRET and --simulate / X402_ALLOW_SIMULATE=1. Settlement kind is simulated. capturedRevenueUsd stays 0.

NEVERALWAYS
Accept x402_… as paymentHMAC BOUND to the issued challenge (id + resource + traffic type + amount), verified against the persisted issuance record, single-use
Claim merchant-of-record / live USDCstatus: WAITLIST liveClaim: false
Put x402/USDC in dashboard or landingKeep it in this CLI + skill (hosted-source-of-truth)
Execute x402 spend from the economic routerExisting approval gate in hermes-economic-router.js
Honour a token whose challenge was never issued, is expired, or was already usedReject: challenge_not_issued / challenge_expired / challenge_already_consumed
Let simulated and real tokens share a shapeSimulated ones carry the x402sim.v2. prefix — nothing real is shaped like that
Buyer outreach / new SKU (ECI)Waitlist URL only

Waitlist: https://blog.cloudflare.com/monetization-gateway/
Pay Per Crawl signup: https://www.cloudflare.com/paypercrawl-signup/

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.