Squiid vs OpenRouter
OpenRouter answers which model a request should go to. Squiid answers what the app needs to exist: database, hosting, email, SMS, storage, auth and payments, plus the models. Both sell prepaid credits with no markup.
Short answer. If you only need models, use OpenRouter. Larger catalogue, cross-provider routing, lower fee. If your project also needs a database, hosting, email, auth and storage, Squiid covers all of it on one key and one bill, using the same no-markup credit model.
Squiid is often described as OpenRouter for everything. That is fair, and the pricing shape is borrowed on purpose.
Feature by feature
| OpenRouter | Squiid | |
|---|---|---|
| What it covers | Inference only. 500+ models from 80+ providers, with automatic routing and fallback. | The whole stack: models, database, auth, storage, email, search, cache, SMS, payments and source control. |
| Markup on provider prices | None. You pay the provider inference price. | None. $1 of credit is $1 at the provider. |
| How they make money | A platform fee at credit purchase: 5.5% Standard, 8% Business, negotiated on Enterprise. Crypto payments carry a separate fee. | A monthly plan plus a fee at top-up: Free $0/mo + 15% ($50 minimum), Solo $19.97/mo from 8% falling to 3.5% with spend, Team from $29.97/seat/mo one point lower, Custom + 3% or less. |
| Credits | Prepaid, denominated in USD. Credits may expire after one year. | Prepaid, denominated in USD. Broadly the same model. |
| Refunds | Unused credits refundable within 24 hours of purchase; the platform fee is not refundable. | Unused credits refundable within 24 hours; the fee is not refundable. Deliberately the same. |
| Bring your own key | Supported. Free up to $25,000 a month of list-price inference, then 5% of what that usage would have cost. | Not the primary model. Squiid provisions and holds the upstream key, so there is no account to bring. Connect integrations cover services you already own. |
| Spend controls | Auto top-up at a threshold, per-key credit limits, and an in-flight budget that pre-authorises each request and rejects with HTTP 402 if it will not fit. | Auto top-up with a monthly cap, alerts at 75, 90 and 100%, and pause-on-zero across every service, not models alone. |
| Free tier | 50 requests per day on free models. | No free inference tier. Plans start at $9.97 a month. |
| Model routing and fallback | Yes, the core product. Automatic failover across providers for the same model. | No cross-provider model routing. You call a named provider through its gateway path. |
| Provisioning non-API services | Not applicable. Databases, hosting, email and auth are outside its scope. | Yes. Squiid creates the upstream account or project for you and holds the credential. |
| Invoicing for accounting | Credit purchase receipts for inference spend. | One monthly PDF covering credits, plan and pass-through subscriptions, forwardable to accounting. |
| Key custody | One OpenRouter key for models. Your database, hosting and email keys stay wherever they were. | One Squiid key for everything. Provider credentials live in Squiid, not in your repository. |
When to pick OpenRouter
Pick OpenRouter when inference is the whole problem. If your app calls models and nothing else, or you want one request routed across providers of the same model with automatic failover, that is what it is built for. The 5.5% Standard fee with no monthly minimum is cheaper at low volume, and 50 free requests a day is useful for experiments.
It is also the better fit if you already hold provider accounts and want to keep them: bring your own key free up to $25,000 a month of list-price inference, then 5% of what that usage would have cost.
When to pick Squiid
Pick Squiid when the list has stopped being a list of models. A typical vibe-coded app reaches production with a database, a host, an email sender, auth, storage, error tracking and payments, plus a model provider or two: eight signups, dashboards, credentials and invoices. Squiid makes it one of each.
The second reason is key custody. OpenRouter holds your model credential; Squiid holds all of them, so a leak is one click to rotate rather than an afternoon finding every place a database URL was pasted.
Use both
These are not mutually exclusive. OpenRouter for model traffic, where its routing and catalogue are genuinely better, and Squiid for the rest of the stack. Or route models through Squiid too, if you would rather have one invoice than the best routing.
Questions people ask
Is Squiid a fork of OpenRouter?
No. Squiid borrows a pricing model OpenRouter proved works: prepaid credits at par, one fee at top-up, spend that pauses instead of overdrawing. OpenRouter does inference; Squiid does the whole stack.
Which is cheaper for pure model calls?
For inference alone, OpenRouter Standard at 5.5% is a lower fee than Squiid: 15% on our free plan, or 8% plus $19.97 a month on Solo until your trailing 30-day spend passes $500, where Solo drops to 5% and then 3.5% above $2,000. If models are all you buy, OpenRouter is cheaper at most volumes and we would rather say so.
When does Squiid come out ahead?
When your project needs more than models. If you also pay for a database, hosting, an email API and auth, Squiid replaces four more signups, keys and invoices.
Can I use both?
Yes, and plenty of people should. Route model traffic through OpenRouter for its catalogue and cross-provider fallback, and use Squiid for the database, hosting, email, storage and auth it does not cover.
Does OpenRouter mark up model prices?
No. Per their FAQ and pricing page as of 2026-09-18, inference passes through at provider prices and the fee is charged when you buy credits. Squiid uses the same structure.
Does either one expire my credits?
OpenRouter states credits may expire after one year. Squiid uses a twelve month expiry too, with unused credits refundable within 24 hours and the fee non-refundable.
Models are one of sixteen
categories you need.
Squiid covers the whole stack on one account, one key and one bill. No markup on provider prices.