Free vs paid blockchain servers the category where paid already works.

Free blockchain servers cluster around development workflows. Ethereum Address Validator checks addresses, checksums, and ENS names; Ethereum & EVM Message Signing covers EIP-191 and EIP-712 typed data; mcp-klever-vm and the Tolk compiler server target specific chains' smart-contract development. These run locally, operate on data you provide, and have essentially no marginal cost per call — which is exactly why they're free and should stay that way in your stack.

If your agent is building, signing, or validating with its own keys and its own RPC access, self-hosting these is the right answer with no caveats.

The x402-priced listings in this category sell freshness. Gas Oracle API serves real-time gas prices and USD cost estimates for Base and Ethereum; DEX Swap Quotes API aggregates quotes across Uniswap, SushiSwap, and Aerodrome; Solana Priority Fee Estimator API reads current congestion at six fee levels. Each answer is only valuable for seconds, and producing it means continuously watching chains and DEX liquidity — infrastructure someone has to run around the clock.

That's why these are paid: the operator's costs are continuous, and stale data is worse than no data when an agent is about to submit a transaction.

Blockchain agents are the one audience that already holds the payment instrument. An agent quoting a swap already has a wallet; settling $0.01 in USDC on Base to get the quote is the same motion as the trade itself. The x402 flow — 402 Payment Required, pay, execute — settles in about two seconds, with Ed25519-signed receipts and no chargebacks, and the 2s-io MCP listing shows the pattern extended across Base and Solana settlement.

Compare that with the traditional alternative: signing up for an RPC provider's subscription tier, managing the API key, and hoping your usage fits the plan. For intermittent, high-value reads, per-call wins on both economics and operational surface.

The split in this category is unusually clean. Local computation — building transactions, validating addresses, signing messages — should be free and self-hosted; paying per call for math your own machine can do makes no sense. Live market state — gas, fees, quotes, congestion — favors paid endpoints unless you're prepared to run indexing and monitoring infrastructure yourself and keep it honest.

Maintainers with real-time data products should note that this category is where agent-paid endpoints are being proven first. Claiming and pricing a listing puts you in that market; Loomal's 5% fee on settled transactions is currently waived.