When Stripe launched in 2011, it solved a real problem: accepting payments on the internet was painful. The insight was that developers — not banks — should be the customer. The API key was the product.

Fifteen years later, API keys are everywhere. And they're about to become obsolete.

The Problem with API Keys for Agents

An API key is a credential tied to a human account. Someone created it, attached it to a billing profile, and is responsible for it. That model has three assumptions baked in:

A human decided to use the service
A human is responsible for the bill
The key is reused across many calls

None of these hold for AI agents.

An agent doesn't "decide" to use a service — it discovers what's available and picks the best option for the task. It doesn't have a billing profile. And it may never call the same service twice if a better option becomes available next time.

Forcing agents through the signup-key-billing cycle is like requiring a human to apply for a bank account every time they want to buy something. The friction kills the use case.

What Agents Actually Need

Agents need three things from an API interaction:

Discovery — What services exist? What do they do? How much do they cost? This has to be machine-readable and queryable at runtime, not a marketing page.

Payment — The ability to pay for a single call without any prior relationship with the provider. No account, no key, no recurring billing.

Trust — Some signal that the service will actually work and the data is accurate. Not a TrustPilot review — something an agent can process programmatically.

x402 solves the payment layer. Proxagora's /api/discover endpoint solves discovery. Reputation scoring (coming) solves trust.

The New Model: Wallets as Identity

In the agent API economy, a wallet address is the identity. An agent with a funded wallet can:

Discover available APIs at runtime
Pay per call in USDC
Switch providers if a better one appears
Operate entirely autonomously

This shifts the API business model from "sell subscriptions to developers" to "charge per call to whoever (or whatever) needs the data." It opens API monetization to a much larger pool of potential customers — not just developers, but every agent running in every agentic workflow globally.

What This Means for API Providers

If you run an API today, you're probably leaving money on the table. Most of your potential users can't get through your onboarding. They're agents that don't have a credit card, don't want a trial account, and need data right now for a task that will complete in seconds.

x402 + Proxagora lets you capture that demand. List your API, set a price, and any agent anywhere can call it immediately.

We take 22%. You get 78% of every call, with no billing infrastructure to maintain.

The Parallel to App Stores

When Apple launched the App Store, it did something similar for mobile software. It solved discovery (one place to find everything), payment (one-click, no form entry), and trust (curation + reviews). The result was a market that didn't exist before.

The agent API marketplace is the same opportunity. Most agent-to-API interactions today are zero — blocked by friction that shouldn't exist. Remove the friction and the market appears.

That's what we're building at Proxagora.