monetize-service

Build an x402 payment-protected Express API charging USDC per request on Base.

Updated May 10, 2026
One-click install
npx skills add https://github.com/Tsin418/crypto-research-agent --skill monetize-service-tsin418
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monetize-service
Source: https://github.com/Tsin418/crypto-research-agent/tree/main/.agents/skills/monetize-service
Command: npx skills add https://github.com/Tsin418/crypto-research-agent --skill monetize-service-tsin418

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monetize an AI or data endpoint so other agents can discover and pay to use it, instead of sharing it for free.

Core Features & Use Cases

  • Build an x402 payment-protected API: Create an Express server that returns HTTP 402 payment requirements and accepts USDC payments per request.
  • Charge per endpoint and per request: Configure pricing, network (Base mainnet or Base Sepolia), and pay-to address for each route.
  • Enable automated discovery via the x402 Bazaar: Register discovery extension metadata so other agents can find and confidently call your paid endpoints.
  • Use Case: Publish a priced research or compute endpoint (for example, “analyze market risk signals”) that other agents can call after paying the per-request USDC fee.

Quick Start

Run the monetization setup by creating an x402 Express payment server that protects GET /api/example, charges $0.01 in USDC on Base, and registers the endpoint for Bazaar discovery.

Frequently Asked Questions about monetize-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monetize an Express API with USDC payments on Base?

You can monetize an Express API by building an x402 payment-protected server that returns HTTP 402 requirements and accepts USDC payments per request on Base. It configures pricing, network, and pay-to address for each route so other agents pay to access your endpoint.

How does x402 payment middleware work for agent-to-agent workflows?

The x402 payment middleware intercepts requests to your Express routes and returns HTTP 402 payment requirements. When calling agents pay the per-request USDC fee on Base, the middleware verifies the transaction and allows access to your research, enrichment, or computation service.

Can I charge per request for my data endpoint instead of using a subscription model?

Yes, you can charge per request for a data endpoint by applying x402 payment middleware to your Express routes. This configures exact per-request pricing in USDC on Base mainnet or Base Sepolia, allowing automated agents to pay exactly for the calls they make.

How do I make my paid API discoverable for other agents to find and call?

To make your paid API discoverable, register discovery extension metadata with the x402 Bazaar during your server setup. This allows other agents to automatically find your priced endpoints and confidently call them after processing the USDC payment requirements.

What do I need to set up before configuring x402 per-request pricing on my routes?

Before configuring per-request pricing, you need an authenticated x402 wallet, an HTTP facilitator-backed x402 resource server, and registered payment schemes for Base networks. You then apply paymentMiddleware to your Express routes with the desired price, network, and payTo address.