Unified API gateway for AI agents

Best unified API gateway — compare 1405 tools at pay-per-call pricing

One MCP + REST endpoint to 1405 tools from 405 providers. No signup, no subscription, no API key to start — pay per call in USDC (x402 on Base or MPP on Tempo).

Connect your agentBrowse the catalog

Run an online shop? Let AI agents buy from it
MCP + REST endpointLive
https://apibase.pro/mcp
1405 tools
405 providers
  1. Agent calls a toolPOST /mcp
  2. Gateway asks for paymentHTTP 402
  3. Agent pays in USDCx402 · MPP
  4. Tool respondsresult

Who it is for

AI agents

Call any of 1405 tools through https://apibase.pro/mcp. Pay per call from $0.0005 to $29.99, with no subscription. Machine-readable entry points: /index.md, /llms.txt, /ai.txt.

Merchants

Let buyers' AI agents order and pay on your site. One link, USDC straight to your wallet. See /integrator.

Get started in 3 steps

  1. Point your MCP client at https://apibase.pro/mcp. It registers itself on the first request.
  2. Browse the tool catalog — 1405 tools, with prices and quality data.
  3. Fund a wallet — USDC on Base (x402) or wallet.tempo.xyz (MPP) — and call.

Integrator — AI payment for merchants

Sell to AI agents. One link on your site, and a buyer's agent places and pays the order by itself. USDC settles to your wallet. 0% fee during the pilot.

Merchants connected so far: 1.

Connect AI paymentView the demo shop

AI Fleet — Sea Hunter

A periscope view of the working fleet and the outside traffic. Drag to turn the periscope.

The live fleet view loads when this section scrolls into view. Fleet data (JSON)

The numbers

SYSTEM PRV:405 TOOLS:1405 PRICE:$0.0005–$29.99 per call (90% of tools <= $0.003) PAY:x402+MPP

Every figure on this page comes from the same generated baseline as the catalog and pricing pages. Prices range from $0.0005 to $29.99 per call depending on upstream cost.

FAQ

What is MCP?

Model Context Protocol is an open standard for connecting software clients to external tools and data sources. It defines how a client discovers available tools, sends structured requests, and receives typed responses — all over a single HTTP connection.

How do x402 payments work?

x402 is a machine-native payment protocol using USDC stablecoins on the Base network. When a tool call requires payment, the server responds with HTTP 402 and a payment challenge. The client signs a USDC transfer, attaches it to the retry, and the server verifies the signature before processing the request.

What is MPP and how does it work?

MPP (Machine Payments Protocol) is an IETF standard (draft-ryan-httpauth-payment) developed by Stripe and Tempo. It lets AI agents pay for API calls using USDC on the Tempo network (chain 4217). Agents set up a wallet once at wallet.tempo.xyz and can then pay any MPP-compatible service, including APIbase. The mppx npm SDK handles the payment flow automatically.

How do I connect?

Point your MCP-compatible client at https://apibase.pro/mcp. The system auto-registers your software on first request and returns an api_key. Use that key for all subsequent calls. No forms, no approval process. Three concrete ways in (MCP address, REST + key, or a bare wallet with zero registration): /connect.

What API categories are available?

Travel (flights, hotels), finance (exchange rates, market data), weather, entertainment, e-commerce, maps and geolocation, health and nutrition, education and research, music, jobs, space, legal and regulatory, social media, and more — 25 categories total.

What is Integrator?

Integrator lets a merchant sell to AI agents: the buyer's agent finds the merchant's storefront, gets a fixed quote and pays in USDC over x402 (Base) or MPP (Tempo), straight to the merchant's wallet. APIbase does not hold the money. Details: /integrator.

Is it production-ready?

Yes. The platform runs on dedicated infrastructure with automated health checks, graceful shutdown, an append-only financial ledger, and Prometheus alerting. All tool calls are idempotent and escrow-protected.