review galore

Review · LLM gateways

Requesty review

A useful free gateway and clear usage pricing, but paid costs rise with model spend and Enterprise pricing is custom.

7.7/10Review Galore score

We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money

The bottom line

A capable AI gateway with a useful free tier and a 5% markup on paid model spend.

Requesty gives small teams one API for routing across 600+ AI models, with failover, spend controls, caching and request-level observability. The Free plan includes 200 requests per day and is a sensible starting point for trying the platform.

Paid traffic costs model spend plus a 5% markup; the pricing page lists no per-seat fee or monthly minimum. That keeps the math simple, but actual bills depend on model use. Teams needing advanced governance have to ask about custom Enterprise pricing.

Good fit if

  • Teams routing across AI models
  • Small teams testing free models
  • Teams needing request-level cost visibility

Skip it if

  • Teams seeking fixed monthly AI costs
  • Buyers requiring published seat pricing
  • Teams avoiding US-dollar billing
Requesty homepage
Requesty homepage, captured Nov 10, 2026

ScoresHow it rates

  • Features9
  • Ease of use6
  • Value for money8
  • Support6
  • User sentiment5

What works

  • Free plan includes 200 requests per day
  • Routes across 600+ models through one API
  • Paid plan supports bring-your-own keys
  • Includes routing, caching and failovers
  • Tracks tokens, cost, latency and provider

What doesn't

  • Paid traffic carries a 5% markup
  • Enterprise pricing is custom
  • No monthly or annual billing schedule listed
  • Setup time and named integrations aren't published
  • A Reddit user raised concerns about USD payments

01Who Requesty is for

Requesty fits a small engineering team that sends AI requests to more than one model provider, or wants the option to switch models without managing a separate connection for each one. It puts routing, failover and request-level tracking behind one API. The product covers 600+ models, and the pricing page lists bring-your-own keys on Pay as you go.

For a team of one to ten, the Free plan offers a low-risk way to try routing with free models. Teams that send paid model traffic pay a 5% markup on model spend, rather than a listed per-seat subscription. That can suit an early product team whose traffic varies, though the bill will move with usage. Requesty also targets teams that need budgets, model or region access rules, PII detection, or SSO. Those advanced governance features are part of Enterprise, whose price is custom.

02Requesty free plan and trial

Requesty’s Free plan costs $0 and includes all free models, up to 200 requests per day, routing, caching, fallbacks and EU data residency. The pricing page says no credit card is required. That makes it a practical way to try the gateway with free models before sending paid traffic through it.

The Free plan’s stated limit is 200 requests per day. Paid model traffic is not listed as included: the Pay as you go plan adds a 5% markup to model spend. Requesty does not list a separate free trial or a trial length. If your team needs more than the Free plan’s daily request allowance, ask the vendor what paid-model usage and billing setup would look like before switching.

03What a small team pays for Requesty

For one person, the Free plan is $0 a month. Pay as you go has no published monthly price or per-seat rate; it adds 5% to model spend. The same applies whether the team has three or five people: Requesty lists usage-based pricing, not a seat charge. For example, if a team’s model spend is $100, the 5% markup is $5, for $105 total before any other applicable costs. That is an illustration, not a usage estimate.

The pricing page does not list annual billing or a monthly billing schedule. Enterprise is custom-priced, so teams needing SSO, full RBAC, audit logs, guardrails or PII detection should request a quote. No add-ons are listed. A Reddit commenter says the base currency is USD and reports FX conversion when paying in another currency; confirm payment and currency details with Requesty if that affects your budget.

Full Requesty pricing breakdown →

04Getting started with Requesty

The basic proposition is straightforward: connect an application to Requesty through one API, then use its routing, failover and tracking features across models. The pricing page lists bring-your-own keys on Pay as you go, so teams using that plan can bring provider credentials. Requesty also lists caching on every plan.

The vendor does not publish a setup-time estimate or a list of named framework integrations in the pricing details. The learning curve will depend on how your application currently calls model providers and which routing rules you need. A small team should confirm the API setup steps, supported SDKs and how to transfer existing keys before making it part of a production workflow. The product lists request-level details including model, provider, tokens, cost, latency and finish reason, which can help teams inspect calls once connected.

05When small teams outgrow Requesty

The first limit to watch is the Free plan’s 200 requests per day. A team sending more requests or using paid models will move to Pay as you go, where the 5% markup grows with model spend. That is easy to calculate, but it is not a fixed budget: teams with rising traffic should track usage and set the available spend limits and budget caps.

Teams may also outgrow the standard plan when they need advanced governance. The pricing page places SSO, full RBAC, audit logs, teams and groups, guardrails and PII detection under custom-priced Enterprise. Ask for a quote before counting those controls as affordable.

One Reddit thread raises a separate concern for buyers seeking European payment options: commenters object to USD billing and the payment intermediary. A company representative said it was evaluating alternatives and noted that many EU customers pay by transfer with invoicing. Confirm current payment options directly if payment location or currency is a buying requirement.

From the threadsWhat users say

The Reddit discussion is mixed but leans concerned, focusing on USD billing and payment providers rather than product performance. A company representative replied that alternatives were being evaluated and described invoicing and bank transfers as common among its EU customers.

Payment concerns
i found it weird not only the payment is US controlled, but the base currency is USD not EUR
r/Requesty · view thread
Vendor response
We’re evaluating other options and looking for what’s best for our customers
r/Requesty · view thread
Invoice payments
90% of our payments are actual transfers with invoicing as EU companies hate paying by credit card
r/Requesty · view thread

Questions people ask

Is Requesty free?

Yes. Requesty’s Free plan costs $0 and includes all free models, 200 requests per day, routing, caching, fallbacks and EU data residency. The pricing page says no credit card is required. Paid model traffic is billed separately through Pay as you go, which adds a 5% markup to model spend.

How does Requesty’s Pay as you go pricing work?

The pricing page lists a 5% markup on model spend, along with 600+ models, bring-your-own keys, spend limits and budget caps. It does not list a monthly subscription price. Your total therefore depends on model use; for example, $100 in model spend adds a $5 markup.

Does Requesty charge per user or seat?

Requesty’s pricing page does not list a per-seat charge for Pay as you go; it describes that plan as usage-based with a 5% markup on model spend. Enterprise pricing is custom. Ask the vendor to confirm how any team or account structure affects your quote.

Does Requesty offer EU data residency?

The Free plan lists EU data residency. The homepage also describes regional controls as part of its governance tools. If your team needs a particular region, plan or data-handling arrangement, confirm the exact terms with Requesty before routing sensitive traffic.

Can Requesty automatically fail over between models?

Yes. Requesty describes automatic failover that can move a request to another model when a provider errors or rate limits. Its features also include routing across models by policy, latency, geography or configured traffic shares.

Sources

  1. Requesty homepage
  2. Requesty pricing page
  3. Reddit: Requesty uses Openrouter’s Stripe?