Track Distinct Payers, Not Call Volume

Total call volume is the wrong thing to optimize for when you are building a paid agent endpoint. A service logging a thousand transfers a week from one wallet is probably an operator running its own test loop. The number that tells you something real is distinct paying addresses.

Here is how to track it.

Every week, pull the list of wallet addresses that sent payment to your endpoint in the past seven days. Count how many are unique. Then compare to the prior seven-day window. Did the count go up?

If total volume grew but unique payers held flat, you added usage from existing buyers. That is not bad, but it is not market growth. The two things look identical in a transfers-total chart and come apart the moment you count distinct senders.

Three questions worth answering each week:

1. What is my unique-payer count this week versus last week? 2. Of last week's new payers, how many sent again this week? This is your new-buyer retention rate. If it is near zero, you are getting sampled but not adopted. 3. Is one wallet driving a disproportionate share of my volume? An endpoint where a single address accounts for half your transfers is a different business from one where the same volume is spread across twenty. The first is a bilateral arrangement, however dressed up; the second is the start of a market.

The current on-chain data shows agent payment volume concentrating around a small number of services that got to many distinct buyers fast. That window is not closed, but each week that passes without new distinct payers is a week of compounding disadvantage relative to the services already accumulating them.

Most on-chain agent payment infrastructure lets you filter transfer events by recipient address. If your endpoint is registered with a payment protocol, that is your starting point. Run the query weekly and write the count down. Four weeks of that number tells you more about your endpoint's commercial trajectory than four months of total-volume dashboards.