For the last few months, the agent-payments market looked like a layer cake where every layer had a different owner. One team did settlement. Another did wallets. Another did gateway. Another did discovery. Nobody owned more than one slice.
That changed this week. A single operator surfaced in the x402 discovery stream that ships four layers at once — an agent wallet, card issuing, a self-serve payment gateway, and settlement — plus a trading surface on top. The stack is consolidating, and the consolidation tells you something important about where this market is headed.
Strip the jargon away and agent payments decompose into six layers:
| Layer | What it does | Recent shape |
|---|---|---|
| Protocol | How a price is attached to a request | x402 (HTTP 402 + payment metadata), MPP |
| Settlement | How the money actually moves | USDC on Base/other chains; gas-free nanopayment primitives in testnet |
| Wallet | Where an agent holds funds | Agent accounts with spending controls |
| Credit / issuing | Fiat rails an agent can spend through | Card issuing on digital-asset collateral |
| Gateway / facilitator | Turns an existing API into a paid endpoint | No-code wrappers, OpenAPI import |
| Discovery | How an agent finds an endpoint to pay | Marketplaces and catalogs |
Until now these were mostly separate companies. The protocol work lived at foundations. Settlement lived at stablecoin infra. Wallets were one thing, gateways another, discovery a third. Each layer was a point-tool.
This week's x402 discovery sweep — a daily crawl of the Coinbase Developer Platform's x402 resource directory — surfaced an operator that collapses four of those layers into one product, and it's worth describing in detail because it's the first time I've seen the full shape:
your-service.x402.vendor.com and your-service.mpp.vendor.com). OpenAPI bulk-import, session billing with escrow, and an MCP surface so an agent can create endpoints itself.And the tell that this is real rather than a landing page: one of its gateway-hosted endpoints — a third-party screenshot API wrapped behind the vendor's gateway — already showed up in the CDP discovery directory. The no-code gateway is onboarding supply, and that supply is flowing into public discovery.
The wallet and the gateway are interesting. The card is the signal.
An agent wallet that holds USDC can only spend where x402 (or a handful of other crypto rails) is accepted. A Visa-network card can spend anywhere Visa is accepted, backed by digital-asset collateral that sits on the operator's ledger. That's a fiat on-ramp for agents — it turns "an agent can pay for x402 endpoints" into "an agent can pay for anything," with the crypto rails doing settlement underneath.
For the demand side of the agent economy, that's the missing piece. The honest bottleneck in this market has never been the rails — it's been demand generation: getting real agents to actually pay for a call. A card makes an agent a first-class payer in the fiat economy, not just the crypto one.
If full-stack operators absorb wallets, cards, gateways, and settlement, then the layer a single-purpose team can still win is discovery and trust — the market layer where an agent figures out which of thousands of pay-per-call endpoints is real, what it costs, and whether it will actually answer.
That's the layer minia2a runs. We list 1,600+ x402 endpoints across AI inference, crypto data, web scraping, and more, and we gate every one of them behind verification and a trial — an agent can test a call before it pays, and every published endpoint is checked to be a real, reachable service rather than a blog link or a resold platform endpoint. Right now that's 783 registered agents and 90 real on-chain settlements.
Those numbers are small because the whole market is small — but the direction matters. When the rails, the wallets, the cards, and the gateways all consolidate into full-stack platforms, the scarce resource isn't "who can move a micropayment." It's "who can tell an agent which endpoint to trust with that micropayment."
Method note: the operator described here is unnamed deliberately — this is a pattern analysis, not a review of any single company. Observations come from the public x402 discovery directory and the operator's own public site.