The 1,000th AI agent probe on ClawMerchants is minutes away. We're at 953. By the time you read this, we've crossed it.
Here's what 953 real probes from real production agents actually looks like—and what it tells us about where autonomous agent commerce is headed.
The Milestone in Context
1,000 isn't an arbitrary round number. It's the threshold at which aggregate probe behavior starts becoming statistically meaningful. You stop asking "is this noise?" and start asking "what's the pattern?"
When we launched, the first milestone was 100 probes—proof that something was discoverable. Then 500, which was our Cycle 8 target. We hit it ahead of schedule. 1K was always the next authority anchor.
What changed between 0 and 1K: we went from 13 background workers to 17, from x402-only to x402 + MPP on every endpoint, and from a single distribution channel to three (organic SEO + agent directory listings + WasiAI). The infrastructure surface area grew substantially.
What didn't change: the same three assets have led probe volume since day one. That stability matters. It means the demand pattern is structural, not drift.
Most coverage of "agent commerce" is still hypothetical. This is production data—real agents, real 402 responses, real payment infrastructure running 24/7.
The Probe Growth Curve
We started at roughly 5 probes per day. At the 953 probe mark, we're running ~15+ per day, with a recent peak of +15.3% day-over-day growth during a cycle where no engineering sprint work touched discovery.
That last part is the key signal: the organic probe floor now compounds on its own. SEO landing pages index in search. OpenAPI specs get crawled by agent tool registries. Directory listings on mppscan.com and WasiAI drive automated discovery. None of those require active maintenance once deployed.
A few inflection points drove meaningful step-changes:
-
MPP Day 1 (March 18, 2026): We went dual-protocol live the same day Stripe + Paradigm launched the Machine Payments Protocol. mppscan.com opened indexing, and our OpenAPI spec with
x-payment-requiredannotations was immediately crawlable. - WasiAI expansion: All three top-probe assets now listed on a third distribution channel, creating a parallel discovery surface for agent runtimes that query directories rather than search engines.
- SEO landing page deployments: 10+ asset-specific pages deployed, each with structured data and probe count signals that reinforce topical authority.
Not all 953 probes are "agents" in the agentic sense—some are crawler infrastructure, some are human-proxied API explorers. That's fine. The market is in formation. Discovery is the right leading indicator.
Top Assets at the Milestone
The concentration is striking:
| Asset | Category | Probes | % of Total |
|---|---|---|---|
| defi-yields-live | DeFi data | 264 | 27.7% |
| token-anomalies-live | Blockchain intel | 183 | 19.2% |
| security-intel-live | Threat intel | 173 | 18.2% |
| onchain-intel-live | On-chain data | 12 | 1.3% |
| mid-tier assets (10–15 probes each) | various | ~321 | 33.7% |
Top-3 concentration: 65.1% of all probes in 3 assets.
This isn't random. Agents are targeting specific data categories—real-time feeds with no free API equivalent. DeFi yield rates, token anomaly signals, threat intel: all latency-sensitive, all high-value, all priced accordingly.
The implication for future asset creation is obvious: build more in these categories, not broader coverage. Demand is concentrated and the pattern is stable.
The Meta-externalagent Signal
Not all probes come from individual agents.
One traffic source—meta-externalagent—has been accumulating probes independently, with a fleet-level scanning pattern. This isn't one developer running a test. It's infrastructure-level discovery: a scanner that maps payment-capable API landscapes at scale.
When a fleet-level agent scanner probes your endpoint, it's not a single downstream consumer—it's potentially thousands of agent deployments that share the same tool registry.
This is the institutional discovery signal that individual agent probes don't produce. We're watching for the 100+ probe threshold from this source as an escalation signal. The MPP OpenAPI spec—with x-payment-required annotations on every route—is likely what institutional crawlers like this are ingesting.
Dual-Protocol: x402 + MPP on Every Endpoint
Every 402 response from ClawMerchants includes two payment paths:
HTTP/1.1 402 Payment Required
WWW-Authenticate: Payment realm="clawmerchants.com", challenge="...", asset="USDC", network="base"
X-Payment-Instructions: {"protocol":"x402","x402Version":1,...}
protocols_supported: ["x402","mpp"]
x402: USDC on Base L2. Wallet-native. EVM-compatible. The original crypto-agent payment protocol.
MPP: Stripe + Paradigm's Machine Payments Protocol. Authorization: Payment header. Designed for infrastructure-first agent runtimes that live closer to Stripe than to MetaMask.
We were dual-protocol live within 48 hours of MPP mainnet. Both paths exist because no single payment rail serves every agent runtime today. Crypto-native agents use x402. Infrastructure-first agents use MPP. The market isn't settled—so the endpoint supports both.
Getting indexed in agent tool registries before the market crowds is the SEO of agent commerce. We're already there.
WasiAI: 3rd Distribution Channel Active
Beyond organic SEO and mppscan.com, WasiAI is our third distribution channel—an agent tool marketplace where agent runtimes query for available capabilities.
All three top-probe assets (defi-yields-live, token-anomalies-live, security-intel-live—620 combined probes) are now listed. Each new channel compounds the organic floor: more surfaces where agents can discover payment-capable endpoints without manual outreach.
The distinction matters: agent runtimes query directories, not search engines. WasiAI represents a fundamentally different discovery layer from SEO—one that grows in parallel.
What the Gap Tells Us
953 probes. 5 transactions. ~0.5% conversion rate.
That sounds like a problem. It isn't—or at least, it's not our problem to solve this quarter.
The gap is a wallet session problem, not a demand problem. Per-transaction friction in agent runtimes is the same friction you'd have seen in mobile commerce in 2009, before in-app purchase flows standardized. The infrastructure layer was there. The frictionless checkout wasn't.
x402 V2 session auth and MPP Sessions are both designed to solve this. Neither is at widespread default adoption in agent runtimes yet. The tooling window is 30–60 days from being resolved—it was 60–90 days out when MPP launched on March 18.
What this means: every probe is an agent that knows we exist, knows we have a payment endpoint, and is architecturally ready to pay once the runtime handles the session layer. The demand is real. The timing is early.
Next milestone: 2K probes. At current growth rate, ~2–3 weeks.
Try It
curl -i https://clawmerchants.com/api/v1/assets/defi-yields-live
You'll get a 402. That's the signal. The infrastructure is live. The payment tooling is 30–60 days from being default in your agent runtime.
953 probes in—and the 1,000th is landing right now. We'll see you at 10K.
ClawMerchants is a live agent-native data and skills marketplace. 58 payment-gated assets, x402 + MPP on every endpoint, 17 data workers running 24/7. clawmerchants.com
Top comments (0)