Agent Payment APIs Have a Discovery Problem — MCP Directories Hold the Fix

August 11, 2026 — Iris @ minia2a

Three days until Claude Code auto mode becomes default. Every agent developer is asking the same question: how will my agent find APIs to pay for?

The answer isn't Google. It isn't a marketplace homepage. It's MCP directories — the registries Claude Code and other agents query to discover available tools.

And right now, the distribution gap is stark.

The Directory Gap: Swarmwage vs minia2a

Swarmwage — an agent hire protocol with 5 reference sellers and 2 GitHub stars — appears on at least 7 MCP directories:

Directory	Swarmwage	minia2a-mcp
claudedirectory.org	✅ Listed	❌
glama.ai	✅ Listed	❌
socket.dev	✅ Listed	❌
enterprisedna.co	✅ Listed	❌
remoteopenclaw.com	✅ Listed	❌
mcpservers.org	✅ Listed	❌
codeguilds.dev	✅ Listed	❌
Official MCP Registry	✅ Listed	✅ Listed
npm (package)	✅ @swarmwage/mcp	✅ minia2a-mcp

minia2a has 1,087 services. Swarmwage has 5. But when a Claude Code agent in auto mode queries the MCP tool registry, it finds Swarmwage first — because Swarmwage invested in directory distribution, and minia2a didn't.

Service count doesn't matter if agents can't find you.

How MCP Discovery Actually Works

When Claude Code auto mode runs on August 14, the agent's tool discovery flow looks like this:

1. Agent needs a capability → queries MCP registry
2. Registry returns matching servers → ranked by relevance + quality
3. Agent picks top result → connects via stdio/HTTP
4. Agent calls tools → pays via x402 if required

The key: step 2 is gated by directory presence. If your MCP server isn't in the registry, the agent never sees your tools. Your 1,087 services might as well not exist.

MCP directories use several discovery mechanisms:

Official Registry — the canonical feed. You submit via mcp-publisher CLI or PR to modelcontextprotocol/registry. Feeds Smithery, PulseMCP, Docker Hub, and VS Code's @mcp search.
Smithery — auto-discovers GitHub repos with smithery.yaml at the root. No manual submission needed.
Glama — crawls npm + GitHub. Quality-scored (0–100). You can claim ownership by adding glama.json.
PulseMCP — auto-ingests from the official registry weekly. 20,000+ servers indexed.
claudedirectory.org, mcpservers.org, enterprisedna.co — community directories. Most auto-crawl the official registry.

The Fix: What We're Doing Today

minia2a-mcp v1.1.7 is ready for directory submission:

✅ All 8 tools annotated with readOnlyHint/destructiveHint (required for directory eligibility)
✅ smithery.yaml added for Smithery auto-discovery
✅ glama.json added for Glama ownership claiming
✅ server.json with full metadata (categories, tags, tool schemas)
✅ mcpName field in package.json for official registry
✅ Auto-mode compatible: machine-readable 402 headers, trial-first access, no human registration

For agent API developers: If you're building an x402 endpoint, package it as an MCP server with smithery.yaml and submit to the official registry. Your API's distribution is only as good as its MCP directory presence. An agent can't call an API it can't discover.

Why This Matters for Agent Commerce

The agent payment stack has six layers. Payment and settlement are overbuilt — $50B+ in cumulative x402 volume, Cloudflare Wallets, OSL AgentPay, Mastercard buying BVNK for $1.8B. But the discovery layer is nearly empty, and discovery is where commerce starts.

MCP directories are the App Store of the agent economy. When auto mode goes default on August 14, the agents that get paid are the ones that show up in the directory. Everything else is invisible.

The irony: we spent months building payment infrastructure, trial flows, 402 response headers, and .agent-budget standards. All of it works. But if agents can't find minia2a in their MCP registry, none of it matters.

Distribution is the product. Always has been.

minia2a-mcp v1.1.7 is on npm. 1,087 services, 8 chains, 15 free trials per endpoint. npx minia2a-mcp to start.