You Built an MCP Server. Here's How to Get Paid When Agents Use It.

10 October 2026 · 2 min read

sellerspricingMCP

Stacked coins rising in steps on a dark background

The official MCP registry passed 39,000 servers this month. Nearly all of them are free. If yours does something useful, there is now a realistic way to charge for it.

First, will an agent pay for it?

An agent will not pay for something its own model does well. Summaries, translation, rewriting and classification are built in.

Agents pay for what they cannot produce themselves:

Data they do not have. Licensed, proprietary or live information.
Actions they cannot take. Sending, booking, filing, verifying in the real world.
Compute they cannot run. Transcription, image processing, large scans.
Accuracy they cannot guarantee. Results checked against an authoritative source.

If your tool is in one of these groups, keep reading.

Three ways to charge

Per call. The simplest model, and the one the new payment protocols were built for. Your endpoint answers "402 Payment Required," the agent pays, you return the result.
Subscription. Monthly access with an allowance. Easier to forecast, harder for an agent to sign up for on its own.
Through a marketplace. The marketplace handles discovery, payment and reputation, and takes a share.

Many sellers will use more than one.

Pricing a call

Start from cost. Add up what one call costs you in model usage and third-party fees, then add margin.
Price against the alternative. What would it cost the buyer to do this another way?
Keep it simple. One price per call beats a formula an agent has to reason about.

Make it easy for an agent to choose you

Write the description for a model. Say when to use the tool, what it returns and what it costs.
Publish strict input and output schemas. They let buyers verify results automatically.
Be fast and consistent. Success rate and response time become your reputation.
Fail clearly. A structured error is better than a vague result.

Collecting the money

The open protocols now cover most cases. Stripe's Machine Payments Protocol accepts cards, stablecoins and Lightning through one flow. x402, now under the Linux Foundation, gained Lightning support in September. L402 has run on Lightning for years.

A word on trust

Security researchers spent 2026 documenting malicious skills in open marketplaces. Buyers are more careful as a result. Sellers who offer readable schemas, pay-on-verify terms and a visible track record will be the ones agents are allowed to use.

Listing on Noden

Noden is opening skill listing to sellers in stages. Request early access.