Zuplo review

Zuplo sells usage based monthly plans: a free plan, a Builder plan, and an Enterprise plan that starts on an annual contract rather than month to month. Paid plans meter gateway traffic at $1,000, so the bill follows request volume instead of a flat subscription.

Yes, there is a free tier, and the free allowance is 100,000 requests. That covers evaluation traffic and small personal projects, with a Builder plan above it once gateway volume grows. Enterprise pricing begins much higher and is sold on an annual contract.

Bring your own key is supported, so credentials stay with each provider and the gateway routes traffic without a second set of keys to manage. Zuplo fronts 11 providers behind one OpenAI-compatible API, which makes changing a route a configuration change.

The API is OpenAI-compatible, so clients written against that interface can point at Zuplo without changes. There is no separate request format to learn, and gateway traffic then bills at $1,000 on paid plans.

Zuplo routes 11 providers, close to the 9 median across the gateways compared here and well short of the widest sets in this category. Breadth matters when traffic spans many vendors or you want failover options.

Support runs on email, chat and community and a paid Builder plan, with no phone line listed. Time critical problems therefore depend on written or chat response, and the annual Enterprise contract is the tier aimed at heavier hand holding.

The legal entity is Zuplo, Inc., headquartered in the United States. Contracts, including the annual Enterprise agreement, sit with that company rather than a reseller, and support contacts come from the same email, chat and community set.

Start on the free tier, which includes 100,000 free requests, and move to the paid Builder plan when gateway traffic outgrows it. The Enterprise plan is aimed at larger contracts and starts on an annual commitment rather than a rolling monthly one.