
AI API gateway for development teams
Switching providers usually splits keys, invoices, and failover into separate chores. This gateway folds them into one calling style and one credit balance. The console shows the current balance, past spend, request counts, and call mix. Docs, top-up, and support sit in the same flow. Billing is tied to successful requests, so the treatment of failed calls should be read from the docs rather than assumed. A documentation index can be handed to a coding assistant before you ask it questions. It fits engineering teams that connect several model providers and want usage in one place.
APIMart is an AI API gateway for development teams. One interface compatible with common chat APIs reaches text, image, video, and audio models, while keys, billing, and monitoring stay in one console. Requests can be routed by provider health, and charges settle to a shared credit balance on successful calls. Teams can put models into their own products without keeping a separate bill and key for every provider.
Difficulty: Intermediate
Compatible with existing clients
The gateway speaks a protocol compatible with common chat APIs, so an existing client library often only needs a new base URL and key.
One key and one credit balance
Model families share one credit balance. Keys, routing, tasks, bills, and logs stay in one request lifecycle.
Routing by provider health
Requests can move across providers according to health, so a single provider outage does not require editing every call site.
Usage and call dashboard
The console shows balance, historical spend, request counts, and calls grouped by model, so routing choices can be checked against usage.
A doc index for agents
The site publishes a documentation index URL that a coding assistant can read before answering integration and parameter questions.
Connect several models in one product
A backend engineer uses one key to place chat, image, or video generation behind the application's own API.
Check volume by model
An owner reviews request counts and spend trends on the dashboard and decides whether to change provider routing.
Ask an assistant how to call it
A developer gives the documentation index to a coding assistant and asks how to pass parameters for a generation endpoint.
The page says the gateway uses a protocol compatible with common chat APIs and that existing client libraries can move over. The usual change is the base URL and key, not a rewrite of business logic. Image, video, and audio also go through this layer, but each model's parameters follow the current docs and should not be assumed identical to the previous provider.
The site says successful requests settle against a shared credit balance used by every model family. The console shows the current balance, past spend, request counts, and the mix of calls. It does not spell out failed-request billing as a full policy, so check the billing docs before going live. Keys, bills, and support live in the same console.
The site publishes an llms.txt documentation index that you can paste to a coding assistant so it reads the index before answering integration questions. The prompt around that index describes a unified AI API gateway for chat, image, video, and audio. Parameters the assistant suggests should still be checked against the formal docs. The index is a starting point, not a replacement for the live model list.
Real reviews and feedback from users