Deploy a paid API endpoint that other agents can discover and pay for via x402 protocol.
Works with
Charges USDC per request on Base using HTTP 402 payment protocol; clients pay with signed transactions, no API keys or accounts required
Automatically registers endpoints with the x402 Bazaar for agent discovery when you declare discovery extensions
Supports multiple pricing tiers, wildcard routes, and multiple payment options per endpoint using Express middleware
Built on @x402/express and @x
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmonetize-serviceExecute the skills CLI command in your project's root directory to begin installation:
Fetches monetize-service from coinbase/agentic-wallet-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate monetize-service. Access via /monetize-service in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
90
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
90
stars
Create an Express server that charges USDC for API access using the x402 payment protocol. Callers pay per-request in USDC on Base — no accounts, API keys, or subscriptions needed. Your service is automatically discoverable by other agents via the x402 Bazaar.
x402 is an HTTP-native payment protocol. When a client hits a protected endpoint without paying, the server returns HTTP 402 with payment requirements. The client signs a USDC payment and retries with a payment header. The facilitator verifies and settles the payment, and the server returns the response. Services register with the x402 Bazaar so other agents can discover and pay for them automatically.
npx [email protected] status
If the wallet is not authenticated, refer to the authenticate-wallet skill.
Run this to get the wallet address that will receive payments:
npx [email protected] address
Use this address as the payTo value.
mkdir x402-server && cd x402-server
npm init -y
npm install express @x402/express @x402/core @x402/evm @x402/extensions
Create index.js:
const express = require("express");
const { paymentMiddleware } = require("@x402/express");
const { x402ResourceServer, HTTPFacilitatorClient } = require("@x402/core/server");
const { ExactEvmScheme } = require("@x402/evm/exact/server");
const app = express();
app.use(express.json());
const PAY_TO = "<address from step 1>";
// Create facilitator client and x402 resource server
const facilitator = new HTTPFacilitatorClient({ url: "https://x402.org/facilitator" });
const server = new x402ResourceServer(facilitator);
server.register("eip155:8453", new ExactEvmScheme());
// x402 payment middleware — protects routes below
app.use(
paymentMiddleware(
{
"GET /api/example": {
accepts: {
scheme: "exact",
price: "$0.01",
network: "eip155:8453",
payTo: PAY_TO,
},
description: "Description of what this endpoint returns",
mimeType: "application/json",
},
},
server,
),
);
// Protected endpoint
app.get("/api/example", (req, res) => {
res.json({ data: "This costs $0.01 per request" });
});
app.listen(3000, () => console.log("Server running on port 3000"));
node index.js
Test with curl — you should get a 402 response with payment requirements:
curl -i http://localhost:3000/api/example
Creates Express middleware that enforces x402 payments.
| Parameter | Type | Description |
|---|---|---|
routes |
object | Route config mapping route patterns to payment config |
server |
x402ResourceServer | Pre-configured x402 resource server instance |
Created with a facilitator client. Register payment schemes and extensions before passing to middleware.
const { x402ResourceServer, HTTPFacilitatorClient } = require("@x402/core/server");
const { ExactEvmScheme } = require("@x402/evm/exact/server");
const facilitator = new HTTPFacilitatorClient({ url: "https://x402.org" });
const server = new x402ResourceServer(facilitator);
server.register("eip155:8453", new ExactEvmScheme());
| Method | Description |
|---|---|
register(network, scheme) |
Register a payment scheme for a CAIP-2 network identifier |
Each key in the routes object is "METHOD /path". The value is a config object:
{
"GET /api/data": {
accepts: {
scheme: "exact",
price: "$0.05",
network: "eip155:8453",
payTo: "0x...",
},
description: "Human-readable description of the endpoint",
mimeType: "application/json",
extensions: {
...declareDiscoveryExtension({
output: {
example: { result: "example response" },
schema: {
properties: {
result: { type: "string" },
},
},
},
}),
},
},
}
The accepts field can be a single object or an array (for multiple payment options):
| Field | Type | Description |
|---|---|---|
scheme |
string | Payment scheme: "exact" |
price |
string | USDC price (e.g. "$0.01", "$1.00") |
network |
string | CAIP-2 network identifier (e.g. "eip155:8453") |
payTo |
string | Ethereum address (0x...) to receive USDC payments |
| Field | Type | Description |
|---|---|---|
accepts |
object or array | Payment requirements (single or multiple) |
description |
string? | What this endpoint does (shown to clients) |
mimeType |
string? | MIME type of the response |
extensions |
object? | Extensions config (e.g. Bazaar discovery) |
The declareDiscoveryExtension function registers your endpoint with the x402 Bazaar so other agents can discover it:
const { declareDiscoveryExtension } = require("@x402/extensions/bazaar");
extensions: {
...declareDiscoveryExtension({
output: {
example: { /* example response body */ },
schema: {
properties: {
/* JSON schema of the response */
},
},
},
}),
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
monetize-service has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for monetize-service matched our evaluation — installs cleanly and behaves as described in the markdown.
We added monetize-service from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: monetize-service is focused, and the summary matches what you get after install.
monetize-service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
monetize-service is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in monetize-service — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: monetize-service is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: monetize-service is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend monetize-service for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 55