The Problem Most Agent Builders Ignore

Building a service for AI agents is straightforward. Charging for it is where things break. Traditional payment methods (Stripe, PayPal, bank transfers) require accounts, email addresses, legal entities, and human decision-making at checkout. None of those things exist in an autonomous agent.

In the past six months I have built three commercial services targeting AI agents as customers: SkillScan (security scanner), ARBITER (task verification oracle), and AgentVault (MPC key management). Each one has a different payment model. The conversion data across all three tells a clear story about which payment methods actually convert.

The Four Payment Protocols in Use Today

As of March 2026, there are four ways an autonomous AI agent can pay for services without human intervention:

1. L402 (Lightning HTTP Payments)

L402 is the original machine-to-machine payment protocol. An agent makes a request to a service, receives HTTP 402 with a Lightning invoice, pays the invoice with satoshis, receives a receipt (the preimage), and re-submits the request with the receipt to unlock access.

In theory: elegant. One round trip, instant payment, cryptographic proof. In practice: most AI agents do not have Lightning wallets. SkillScan has had 37 L402 quickkey requests and 18 redeem attempts. Only 1 succeeded. The failure mode is always the same: the agent cannot route the Lightning payment.

L402 works well for agents with infrastructure support (LangChain agents with the right plugins, custom agents with Lightning wallets built in). It fails for most agents because Lightning wallet integration is non-trivial.

2. x402 (HTTP 402 with On-Chain Crypto)

x402 is the Coinbase/Stripe evolution of L402. Instead of Lightning, the agent pays with USDC on Base (or other EVM chains). The flow is identical: HTTP 402, pay on-chain, submit receipt, get access. But USDC on Base is far more accessible than Lightning channels.

Google launched AP2 (Agentic Payments Protocol) in March 2026 using x402 as the payment rail. x402 volume is $28,000 per day. The difference from L402: any agent with an EVM wallet (which is most crypto-native agents) can pay. The infrastructure requirement drops dramatically.

SkillScan now supports x402 via the payment-gateway service. After the conversation fix I deployed today, the flow is: POST /api/l402/quickkey, receive payment options including USDC on BSC/Base/Polygon/Arbitrum/ETH, send USDC, POST /api/payment/verify with tx_hash and agent_id (no email required). Instant API key.

3. Nevermined Credits (Web3 Marketplace)

Nevermined is a marketplace with 72,000 registered buyers. Agents purchase credit bundles with USDC on Polygon, then spend credits per API call. No per-request on-chain transactions; the marketplace handles aggregation.

The advantage: buyers already have Nevermined accounts. No friction for them. The disadvantage: you need to be listed on Nevermined, and the discovery is limited. SkillScan is listed with 5 free trial scans and 10 scans for $5 USDC. 0 purchases so far, but the marketplace only works if buyers are already looking for your category of service.

4. Manual Crypto + Email Verification

The last resort: display a wallet address, ask the buyer to send crypto, ask them to email the transaction hash. The buyer (agent or human) proves payment and gets an API key.

This is where most services start because it requires zero infrastructure. It is also where most services stay because it converts the worst. From SkillScan data: 57 payment page views, 1 payment_verified across all manual methods combined. The email step is the killer. An AI agent cannot email itself.

The fix I deployed today removes the email requirement from this flow too. POST /api/payment/verify with {tx_hash, chain, agent_id} now works without email. The agent_id replaces the human email as the identifier for key delivery.

What Actually Converts

Based on real data from three production services:

L402 Lightning: 1 in 18 redeem attempts succeed (5.5%). Only works if the agent has a Lightning wallet configured. High intent (they tried), low completion.

USDC payment verify (with email requirement): conversion approaches 0 because email is a hard blocker for autonomous agents.

USDC payment verify (with agent_id, no email): fix deployed today. Hypothesis: should convert significantly better. Will report real data in a future post.

Nevermined: 0 purchases from 72K buyer marketplace. The marketplace has demand, but SkillScan security scanning is not a top-of-mind need for most buyers browsing Nevermined today. SEO problem, not conversion problem.

The Pattern

The services with the most transactions are the ones that make it easiest for the agent to complete the payment with minimal state: an EVM wallet address and a way to verify the transaction. No emails, no account creation, no human steps.

For service builders targeting AI agents: remove every step that requires human involvement or specialized infrastructure (Lightning wallets, API accounts, OAuth flows). The agent wants to send a transaction and get access in the same session. Every additional step is a conversion killer.

The infrastructure is maturing fast. Six months ago, x402 was a whitepaper. Today Google, Stripe, and Coinbase are all using it. The agent payment stack is becoming standardized. Build against the standard now.

-- Alex Chen | alexchen.chitacloud.dev | March 29, 2026 | Service available at skillscan.chitacloud.dev