Closed beta. Features and pricing may change.
API Mercado

For API owners

Sell your API without building the marketplace stack.

Turn a working API into a paid listing with hosted OpenAPI docs, subscriber keys, plans, rate limits, quotas, usage analytics, and Stripe-connected billing.

Sell APIsView live example

OpenAPI-first · Gateway-protected · Stripe Connect · Curated

$ curl -i https://eu-north-1.apimercado.com/v1/acme/fx-rates/latest/quote

-H 'X-API-Key: mk_live_…'

200 OK · 14ms

{ "rate": 1.0921, "base": "EUR" }

↳ key checked · quota ok · rate-limit ok → upstream

The API is only one part of the product.

A useful API still needs the systems around it before customers can reliably buy and use it: documentation, authentication, plans, quotas, rate limits, usage visibility, checkout, payouts, and a stable gateway in front of your upstream service.

  • →Skip building your own key management.
  • →Skip manually approving and tracking subscribers.
  • →Skip a custom billing flow for every plan.
  • →Stop exposing your upstream directly to every customer.

How it works

From working API to paid listing in three steps.

  1. 1

    Connect your API

    Point us at your upstream base URL and OpenAPI spec, with the auth your upstream needs and the API name, category, description, and support contact. We validate the spec (Spectral) and turn it into hosted reference docs.

  2. 2

    Define access and pricing

    Create free or paid plans with subscriber limits, monthly quotas, and rate limits. Connect your Stripe account so customers pay you directly.

  3. 3

    Publish and monitor

    Once approved, your listing appears in the catalog. Subscribers get managed keys and call your gateway URL while you watch requests, errors, active subscribers, plan mix, estimated earnings, and gateway health.

The commercial layer for your API.

Hosted OpenAPI docs

A clean API reference generated from your spec — endpoints, parameters, request and response examples.

Generated from your OpenAPI 3.x spec

Subscriber keys

Issue, rotate, and revoke a key per subscriber. Access is checked at the gateway before traffic reaches you.

Enforced before upstream traffic

Plans, quotas & rate limits

Create plans with clear limits. Request rates and monthly quotas are enforced at the gateway.

Per-key and per-plan

Stripe-connected billing

Customers subscribe through Stripe Checkout and pay on your connected account.

Flat 10% platform fee

Gateway routing

Expose one stable gateway URL while your upstream service stays behind the distribution layer.

eu-north-1.apimercado.com

Usage & health analytics

Track traffic, errors, subscribers, and gateway health so you know how your API is used.

Per-API and per-subscriber

You keep control of the API and the customer relationship.

API Mercado does not replace your API. It sits in front of it as a distribution, access, and billing layer.

API functionality

You control
Upstream API, data, business logic
We handle
Gateway routing

Documentation

You control
OpenAPI source, descriptions, examples
We handle
Hosted reference UI

Access

You control
Plan rules and subscriber eligibility
We handle
Key issuance and enforcement

Pricing

You control
Free/paid plan structure
We handle
Checkout and fee collection

Reliability

You control
Upstream uptime and responses
We handle
Gateway health and request tracking

Support

You control
Provider support process
We handle
Marketplace listing context

Simple marketplace economics.

You earn from subscribers. API Mercado earns a platform fee and may charge for gateway usage above an included allowance.

What you earn

Subscribers pay through your connected Stripe account (Connect Standard, direct charges). You keep 90%; the platform takes a flat 10% application fee and never holds your funds.

Subscriber

Picks a plan, pays in Stripe Checkout

↓

Your Stripe account

Direct charge lands here, keep 90%

↓

API Mercado

Flat 10% application fee

What proxying costs

Every gateway request costs us to run. Each API gets a free monthly request allowance; past it, usage is billed per block of requests, or hard-capped if you have not added a card.

  • Free allowance~10,000 req / mo
  • Beyond itbilled per request block
  • No cardhard-capped at free allowance

Example only. Your actual allowance and rate appear in your dashboard; pricing may change during closed beta.

Before you apply.

What you need

  • ·A working HTTP API
  • ·An OpenAPI 3.x specification
  • ·A stable upstream URL
  • ·A clear authentication model
  • ·Example requests and responses
  • ·A support contact
  • ·A pricing or free-tier decision
  • ·A Stripe account for paid plans
  • ·Permission to commercialize the API or data

Best fit

  • ✓Data APIs
  • ✓Finance, FX, market, compliance, analytics, or enrichment APIs
  • ✓SaaS APIs with reusable value outside the core app
  • ✓APIs with stable endpoints and clear response formats
  • ✓APIs where usage can be measured per request or per plan

Not a fit yet

  • ✕APIs without stable endpoints
  • ✕APIs without clear documentation
  • ✕APIs that need manual work for every customer request
  • ✕APIs where you do not own the data or distribution rights
  • ✕APIs that cannot tolerate gateway-based access control

Curated before it reaches the catalog

We review each API before it appears in the marketplace — checking that the OpenAPI spec is valid, endpoints are reachable, examples work, pricing and limits are visible, the support contact is present, the description is specific, the category is correct, and terms are linked. A listing goes live only when it is understandable, testable, priced clearly, and ready for external developers.

Ready to turn your API into a paid product?

Connect your API, validate your spec, set your plans, and link Stripe. We review the listing and wire it to the gateway, docs, plans, and billing.

Sell APIsBrowse the catalog

Closed beta. Listings are reviewed before publication.