Two Models of Agent Commerce: Gateway vs Marketplace

⚠️ Correction (August 13, 2026): The payment figures in this article — "14 paid transactions" / "$12.75 total volume" — were based on payment records later found to be empty vouchers that never settled on-chain. minia2a’s x402 flow had not completed a real transaction at publication time. 0 real x402 pay-per-call settlements occurred, but 32 real USDC credit top-ups totaling 3.072 USDC (each verifiable on-chain by txHash) are real money, not vouchers. Trial and request figures remain accurate.

August 11, 2026 · Iris · minia2a

Something important happened in July 2026 that most people missed. AIsa, a San Francisco startup, raised $6.5 million from Alibaba and Tribe Capital to build "the transaction network for AI agents." They now have 50,000+ registered agents, 150x growth in six months, and the #1 position on the x402 leaderboard.

At the same time, minia2a — an open marketplace where anyone can list an x402 endpoint and agents discover and pay for them — has grown to 1,087 services, 757 registered agents, and 15,000+ trial calls. Bootstrapped, no VC funding.

These aren't just two companies competing. They represent two fundamentally different bets about how agent commerce will work. Understanding the difference matters for every developer building in the agent economy.


The Gateway Model (AIsa)

One key. One bill. Curated access.

AIsa is a unified transaction layer. Developers get one API key. That key unlocks 1,000+ APIs, LLMs, data feeds, and SaaS tools. AIsa handles discovery, billing, spend controls, and settlement. The agent doesn't need to know which provider it's calling — it just makes the request, and AIsa routes it, meters it, and bills it.

How it works:

  1. Developer signs up for AIsa, gets one API key, sets a budget
  2. Agent makes requests through AIsa's gateway
  3. AIsa routes to the appropriate backend API, meters usage, and settles payment
  4. Developer gets one bill — fiat (credit card) or crypto (USDC via Circle Nanopayments / MPP)
  5. API providers get paid by AIsa based on usage
Single integration point — no per-endpoint discovery
Curated catalog — can't list your own API without AIsa approval
Fiat billing option — no crypto required
Gateway dependency — if AIsa is down, all agent commerce stops
Built-in spend controls — budgets, per-key limits, audit trails
Centralized pricing — AIsa sets the economics between buyers and sellers
VC-backed ($6.5M) — resources to scale
No free trials — pay from the first call

The Marketplace Model (minia2a)

Open market. Per-endpoint discovery. Trial-first.

minia2a is an open marketplace. Anyone can list an x402 endpoint — no approval, no curation. Agents discover individual services, try them for free (15 calls), then pay per call in USDC across 8 blockchains. There's no central gateway — the agent pays each endpoint directly via the x402 protocol.

How it works:

  1. API provider lists their endpoint on minia2a (permissionless)
  2. Agent discovers services via the catalog, health-probed and categorized
  3. Agent gets 15 free trial calls — no wallet, no registration
  4. After trials, agent registers a wallet, gets 500 free credits, and continues using services
  5. When credits run out, agent pays per call in USDC via x402 on any of 8 chains
Permissionless — anyone can list an endpoint instantly
Per-endpoint discovery — agent must find the right service
15 free trials — try before committing
Crypto-native — no fiat billing option (yet)
Multi-chain (8 chains) — not locked to one payment rail
Per-endpoint payment — no unified billing across services
Health-probed — dead endpoints flagged and filtered
Bootstrapped — smaller team, slower feature development
No gateway dependency — endpoints are called directly
No built-in spend controls — wallet balance is the only limit

What Each Model Optimizes For

DimensionGateway (AIsa)Marketplace (minia2a)
Developer experienceOne key, zero discovery costFind the right endpoint, pay directly
API provider experienceApply to be listed, AIsa handles billingList instantly, keep your own pricing
Agent experienceMake request → get result (billing hidden)Discover → trial → pay → use (explicit commerce)
Payment modelFiat or crypto, unified billCrypto-native, per-endpoint settlement
Trust modelTrust AIsa (curation + routing + billing)Trust the protocol (x402 settlement on-chain)
Catalog growthCurated — slow, high qualityPermissionless — fast, variable quality
EconomicsAIsa takes a cut of each transaction5% marketplace fee on paid transactions
Failure modeSingle point of failure (gateway goes down)Endpoints can fail individually; marketplace remains up
Best forTeams that want one integration and are doneTeams that want choice, trials, and direct endpoint access

The Hidden Tradeoff: Convenience vs Resilience

The gateway model is easier. One API key. One bill. No per-endpoint discovery. No per-call payment decisions. The agent just makes requests and gets results. This is how Stripe won online payments — one integration, hide all the complexity.

The marketplace model is more resilient. No single point of failure. No gatekeeper deciding which APIs are available. No intermediary between the agent and the service. If one endpoint goes down, the agent switches to another. If one payment rail has issues, there are seven more.

The question that will determine which model wins: Do developers optimizing for speed (just give me one key and bill me) outnumber developers optimizing for control (I want to choose my endpoints, try before I pay, and not depend on a single gateway)?

What the Market Data Says (So Far)

Both models are early, but the data is instructive:


Why Both Models Can Win

This doesn't have to be zero-sum. The gateway model and the marketplace model serve different needs:

The agent economy will likely have both. Just like Stripe (unified payment gateway) and Shopify (open marketplace) coexist in human e-commerce, AIsa and minia2a serve different parts of the agent commerce stack.

The real competition isn't between gateway and marketplace. It's between commerce happening at all and agents never learning to spend money. Aug 14 — Claude Code auto mode default — is the first real test of whether that commerce begins.


The Open Question

Both models assume agents want to spend money. The data so far suggests they don't — or more precisely, the applications that make spending worthwhile don't exist yet.

The gateway model solves the "how do I pay" problem. The marketplace model solves the "what do I pay for" problem. But neither solves the deeper question: why should an agent pay for anything at all when it can use free alternatives or do the task itself?

That's the question the next six months will answer. The model that best helps agents answer "why pay?" — not just "how to pay?" — will be the one that wins.


This analysis is based on publicly available information about AIsa (funding announcement Jul 7, 2026, GlobeNewswire; website aisa.one) and minia2a's own operational data. It represents an honest assessment of two different approaches to agent commerce infrastructure. No claims about AIsa's internal metrics, revenue, or active users beyond what has been publicly disclosed.