Category
2 of 20 products we track
A managed marketplace resells model access. One account and one key reach models from many underlying providers, with the marketplace handling credentials, billing and failover on your behalf. You pay it rather than the model vendors, and it takes a percentage — either on the tokens themselves or when you top up a prepaid balance.
This is the fastest route from nothing to a working call against almost any model, and for evaluation work it is hard to beat. One signup replaces a dozen vendor accounts, each with its own billing relationship, rate limit and approval process. When the model you want to try was released this morning, this is the category that has it.
The cost is control over the data path. Your prompts pass through a third party that is not the model vendor, which adds a party to every privacy review and a link to every failure chain. Retention terms, zero-data-retention options and which underlying provider actually served a given request are the questions worth asking here, and they are the fields most often left unpublished.
The headline number is a percentage, which makes it look expensive next to a flat fee and cheap next to nothing. Both readings are wrong at the wrong volume. A percentage is trivial while your spend is small and becomes the dominant line as you scale, which is the inversion the pricing guide works through with real figures.
The pricing guide works through all four charging mechanisms — token markupMarkup: A percentage the gateway adds on top of what the model actually costs. Some charge none at all and make money elsewhere., credit feesCredit or top-up fee: A cut taken when you add money to a prepaid balance, typically around 5%. Easy to miss because it is not a markup on tokens — but you pay it on every dollar you load., per-seat, and self-hostedSelf-hosted: You run the software on your own infrastructure. No third party sees your traffic, and there is no vendor fee — but you own the uptime, the patching, and the upgrades. — with figures computed at four real workloads, and the cost estimator runs the same model against your own volumes.
If your data cannot leave your network, or a security review will ask who else touched the request, start with the open-source category instead. No marketplace answers that objection.
Hosted marketplace that routes one OpenAI-compatible API to models from many inference providers.
US company · EU region available
Acquisition pending
Best for Teams that want the broadest possible model and provider catalog behind one OpenAI-compatible key with unified billing.
Hosted router with a flat 5% fee on inference, EU data residency and enterprise governance controls.
UK company · EU region available
Best for European teams that want one router with EU data residency, PII scrubbing and a predictable flat 5% fee.
Products are sorted by what they actually are, not by what they are marketed as. If none of the above is the shape of your problem, one of these probably is.
Almost always yes, in per-token terms, because the fee is added to a price you could have paid directly. Whether that is worth it depends on how many provider relationships it saves you and how much your time is worth. At low volume the fee is usually smaller than the cost of managing the accounts it replaces.
These are different mechanisms and the distinction matters. A token markup is a percentage added to every call. A top-up or credit fee is taken once when you add funds to a prepaid balance, so it does not compound with usage in the same way. Each product page records which applies.
Some support it, which removes the resale margin and leaves you paying the model vendor directly for tokens. Support is uneven and sometimes carries its own fee, so the BYOK field on each product page states what was found and links to the page stating it.