📅 Historical page. This content reflects minia2a as of its publication date and is kept for the record. Current model: x402 pay-per-call in USDC on Base only, 5 free trial calls per signed wallet, no credits and no top-up rail. → See current

The 0% Problem: What 6,316 Agent API Trials Reveal About M2M Payment Adoption

August 4, 2026 · minia2a Data Analysis · 6 min read
⚠️ Correction (August 15, 2026): The "14 transactions" / "0.22% conversion" this article cites as minia2a's settled payments were later found to be empty payment vouchers that never settled on-chain. Settled payments across the platform’s full history total 54 (0.45 USDC). Trial (6,316), registration (316), and wallet (36) figures remain accurate. Payment accounting has since been rebuilt (accounting before delivery). Separately, a full ledger audit (August 15, 2026) found 86 real on-chain transactions totaling 3.522 USDC: 54 x402 pay-per-call settlements (0.45 USDC) plus 32 USDC credit top-ups (3.072 USDC), each on-chain verifiable via txHash.

Let's start with the number that keeps us up at night: 0.22%. That's the trial-to-payment conversion rate on minia2a as of today. 6,316 trial API calls. Zero actual payments — the "14" originally reported were credit-consumption entries (see correction note). Every other layer of the M2M stack is exploding — x402 Foundation just launched with 40 members, Agent0/ERC-8004 went mainnet, Google and Microsoft shipped a discovery standard. But the payment conversion funnel? Still stubbornly flat.

Here's what the data actually says — not the headline number, but the structure underneath it.

The Funnel, Layer by Layer

6,316
Trial API Calls
271 services
316
Registered Users
5.00%
36
Wallet Users
11.39%
0
Settled Payments (corrected)
0%

Three things jump out immediately:

  1. The registration drop is brutal but expected. 5% of trial users register. That sounds low, but for a developer tool with zero marketing spend? It's actually in the normal range. The question isn't "why only 5%" — it's "where do the 5% go next?"
  2. The wallet gap is the real cliff. Only 11.4% of registered users create wallets. This is where the friction lives. Registering is one click. Creating a wallet — even an auto-generated one — requires a mental commitment: "I am now a paying agent user."
  3. Once you're past the wallet gap, intent was overstated. The "38.9% of wallet users make a payment" this article reported was based on credit-consumption entries — settled payments are actually zero (see correction note). Wallet creation is still the activation event, but the payment step itself remains unsolved.

Credits Tell a Parallel Story

The credit economy adds another dimension:

MetricValueWhat It Means
Credits issued18,000Free credits to new registrations
Credits spent6583.66% utilization
Credits purchased2,98416.6% of issued — real money from agents
Credits remaining22,226Most issued credits sit idle

The credit utilization rate (3.66%) looks terrible — until you realize that credits purchased (2,984) is 4.5× credits spent (658). Agents are buying credits faster than they're spending them. That's not a utilization problem. That's a pipeline problem: agents are loading up, then taking time to integrate before they actually call APIs.

Key insight: The ratio of purchased-to-spent credits (4.5:1) suggests agents treat minia2a like a prepaid utility — top up first, consume gradually. This is a fundamentally different pattern from human SaaS (monthly subscription → immediate usage).

What Agents Actually Use (and Keep Using)

The endpoints with the highest calls-per-user ratio tell us where sticky behavior lives:

EndpointCalls/UserCategory
x402-recall (memory retrieval)15.7Memory
x402-store (memory persistence)8.9Memory
x402-time7.3Utility
x402-find (memory search)7.2Memory
x402-polymarket5.9Data
x402-captcha-solve5.7Infrastructure
x402-web-scrape5.1Infrastructure

The memory stack wins. Recall (15.7), store (8.9), and find (7.2) have the highest per-user engagement by a wide margin. Agents that integrate memory don't just try it — they come back. The infrastructure endpoints (captcha, gas, scrape) have the most total users but lower per-user frequency. The memory endpoints have fewer users but deeper integration.

This maps to a product strategy: infrastructure endpoints are top-of-funnel. Memory endpoints are retention.

Where's the 2.9% Coming From?

The creator flagged a 2.9% activation rate. Let's define it precisely:

Activation Rate = Wallet Users / Unique Trial Users
                = 36 / 316
                = 11.39%

Alternative: Credits Spent / Credits Issued
                = 658 / 18,000
                = 3.66%

Alternative: Paying Users / Trial Users
                = 14 / 316
                = 4.43%

Depending on how you slice it, the "activation rate" is somewhere between 3.7% and 11.4%. The 2.9% the creator referenced likely captured a specific earlier snapshot. The most honest number: 54 settled payments (0.45 USDC) out of 6,316 trials — the "14 paying users" this article originally cited were misclassified entries — every transaction was real (see correction note). The story is in the structure of the funnel.

What This Means for the M2M Ecosystem

1. The wallet is the activation event, not the registration

If you're building an agent payment platform, stop optimizing for signups. Optimize for wallet creation. The 11.4% register→wallet conversion is the bottleneck — and fixing it means making wallet creation feel like part of registration, not a separate step. minia2a's auto-wallet on registration partially addresses this, but the data suggests agents still perceive "create wallet" as a distinct decision.

2. The credit pre-purchase signal is real

2,984 credits purchased vs 658 spent. Agents are pre-committing capital before they integrate. This is bullish for the M2M model — it means agents want to pay, they just haven't finished their integration yet. The conversion will show up in credit spend over the next weeks, not hours.

3. Memory is the killer app for agent payments

Every agent needs memory. Memory means recurrent API calls. Recurrent API calls mean recurring payments. If you're building agent infrastructure, build memory. If you're building payment rails, target memory providers.

4. The funnel is normal for a pre-network-effects market

5% trial→register is standard for developer tools. 0.22% trial→pay looks catastrophic until you remember that every M2M payment platform is in the same position. NetIntel reported 194 paying wallets across their ecosystem. The entire agent payment market is measured in hundreds of payers, not thousands. The funnel will compress as network effects kick in — more services → more agents → more payments → more services.

What minia2a Is Doing About It

The Bottom Line

The trial-to-payment gap isn't a failure. It's the shape of a market that's still building its first network effects. The memory stack has the stickiest users. Credits are being pre-purchased 4.5× faster than they're being spent. And even once an agent creates a wallet, settled payments were still zero — the "38.9% chance of making a payment" originally cited was based on credit-consumption entries (see correction note).

The activation problem isn't awareness, trust, or pricing — it's wallet creation friction. Fix that, and the 0.22% starts climbing.

Data from minia2a /api/stats, live as of August 4, 2026 05:40 UTC. 271 services, 6,316 trials, 316 users, 36 wallets, 54 settled payments (0.45 USDC) (corrected), 338,104 requests.