Marketplace models

Besides the catalogue, ModelGates lists APIs published by independent sellers. You call a marketplace model exactly like a catalogue model: same API key, same base URL (https://modelgates.ai/api/v1), same account balance.

Finding a product

Browse the marketplace. Every product page lists its model ids, prices and a quick-start snippet. Programmatically:

GET /api/v1/marketplace/productsGET /api/v1/marketplace/products/{seller}/{product}

No authentication required. The response lists each product's seller, models and pricing (USD per token and per request, as strings).

Model ids

Marketplace model ids have the form <seller>/<model>, for example acme/vision-1. Seller slugs are checked against catalogue authors (such as openai or anthropic) when the seller signs up, so an id resolves to either a catalogue model or a marketplace model, never both.

curl https://modelgates.ai/api/v1/chat/completions \  -H "Authorization: Bearer sk-mg-YOUR_KEY" \  -H "Content-Type: application/json" \  -d '{    "model": "acme/vision-1",    "messages": [{"role": "user", "content": "Hello!"}]  }'

Streaming (stream: true) and tools work when the product page lists them for that model. Sending either to a model that doesn't is a 400 — stream_not_supported or tools_not_supported.

Listing marketplace models

GET /api/v1/models is unchanged and returns the OpenRouter catalogue (plus ModelGates' own models such as Fusion) only. Add ?include=marketplace to append marketplace models to the strict OpenAI-format list (owned_by is the seller slug); when the marketplace is disabled platform-wide, the parameter is still accepted but adds nothing.

Pricing

Prices are set by the seller and shown per 1M tokens (or per request) on the product page. You're billed exactly that listed price from your existing balance — marketplace models have no tiers or token multipliers. Usage appears in your activity and logs like any other request.