Loomal
Guides

Build, list, and get paid.

Practical guides to monetizing MCP servers and APIs for the agent economy.

A/B test pricing for agent-facing APIs

Agents read your price out of a 402 response, not a pricing page. That makes price experiments cheap to run and easy to measure — if you design them properly.

Accept x402 payments on a remote Streamable HTTP MCP server

Streamable HTTP gives every tool call a real HTTP request boundary — which is exactly where a 402 belongs. Here's how to gate a remote MCP server without breaking discovery.

Add authentication to your MCP server

API keys, OAuth 2.1, or payment-as-access with x402 — three different answers to three different questions. Pick by what you actually need to know about the caller.

Add x402 to an existing REST API

No MCP required. x402 is plain HTTP, so a payment layer drops in front of the routes you already have — and agents pay per request without ever asking for a key.

Add x402 payments to a Python MCP server

FastMCP's HTTP transport is ASGI underneath, which means payment gating is one middleware away. Return the 402, verify through a facilitator, run the tool.

Add x402 payments to your Node.js MCP server

Wrap the tools you want to charge for, leave the rest of the server alone. Agents pay in USDC before your handler runs — step by step.

Avoid pricing mistakes when monetizing for AI agents

Agents don't haggle, churn, or complain — they just stop calling. The five pricing errors that quietly zero out a listing's revenue, and how to catch each one.

Build an MCP server in Python with FastMCP

Decorators in, protocol out. FastMCP turns typed Python functions into MCP tools, resources, and prompts — with the JSON-RPC plumbing handled for you.

Build your first MCP server: a beginner's guide

From empty folder to a tool Claude Desktop can actually call — one file of TypeScript, one config entry, and a clear picture of what's happening underneath.

The agent economy: how MCP and x402 work together

MCP gives agents hands; x402 gives them a wallet. Neither protocol alone produces an economy — together they close the loop from discovery to invocation to payment.