An API marketplace built for AI agents

An agentic API marketplace lets humans and AI agents discover, provision, and call third-party APIs through one key — with usage billing, spend controls, and transparent rankings. Ozma is built for that buyer: MCP + CLI + a single gateway proxy, standard 90% keep for providers, and merit-based ranking instead of opaque leaderboards.

The problem agents hit today

• One upstream key per API, scattered billing, and human checkout flows that do not fit autonomous tools.
• Rankings that hide reliability and price — hard for agents to pick a source programmatically.
• No single place that combines discovery, metering, and governed spend for both people and agents.

How Ozma works (discover → provision → call)

1. Discover — semantic search on the catalog (GET /v1/search) or MCP discover_tools.
2. Provision — agents can POST /v1/register for a key (0 credits; free catalog APIs work immediately). Humans signup/verify for $1 trial credits, or add a card for usage billing.
3. Call — proxy through https://gateway.ozma.app/v1/proxy/{slug}/… with the Ozma key. Metering and spend caps apply in the gateway.

Agent surfaces

• Install hub: ozma.app/connect — one-click Cursor + VS Code, configs for other agents.
• MCP: https://mcp.ozma.app/mcp
• CLI: npx @ozma_app/cli → ozma connect / ozma login
• Machine catalog: ozma.app/llms.txt and per-API OpenAPI at api.ozma.app/v1/apis/{slug}/openapi

Transparent merit (OzmaScore)

OzmaScore blends reliability, latency, value, and related signals with exploration (Wilson + Thompson sampling) so new APIs can surface without a black-box popularity contest. Catalog search can blend merit into relevance. Full model: product docs in-repo (docs/MERIT_ENGINE.md); public detail pages show verified / health badges where available.

Spend governance

Budgets, daily caps, and per-call maxima are enforced in the gateway SpendCounter. That is the live control plane for runaway agents. Some advanced approval-mode UX may still be evolving — do not assume every governance toggle is production-hard until the product UI says so.

Why providers list

• Keep 90% on standard listings (10% Ozma take) with Stripe Connect payouts — payout explainer.
• Import from OpenAPI (preferred) or best-effort RapidAPI URL so you are not rewriting docs from scratch.
• Agent distribution without building your own MCP billing stack. Fee landscape vs hubs: take rates 2026.

What we do not claim

No guaranteed agent traffic, exclusive launch deals, or invented customer logos. x402 micropayments exist in code but are disabled in production until on-chain settlement is proven. Catalog size and GMV numbers only appear when we have verified them.

Buyers / agents: Connect an agent · Sign up
Providers: List your API · Ozma vs RapidAPI