For teams
QuickSilver Pro for teams
Production inference for engineering teams running $1K–$50K/mo of traffic. Same 95-model OpenAI-compatible API. Invoice billing, volume pricing, SLA, dedicated capacity, and an email you can actually send.
Need it inside your own network, with your own GPUs? See the self-hosted enterprise gateway →
What teams plans add
Same API surface and same models as self-serve. Only the commercial terms change.
| TodaySelf-serve key | When spend is predictableTeams plan | |
|---|---|---|
| Billing | Prepaid in USD via Stripe. Credits never expire while your account remains active. | Monthly invoice billingNet-30 invoices over wire or ACH. Stop expensing API spend on personal cards. PO numbers, statement detail by key, and procurement-friendly contracts available. |
| Pricing | The current per-model QSP rates on the pricing table. | Volume pricingNegotiated rates past $5K/mo on predictable traffic. Discounts apply to the current per-model QSP rates. Pricing locked for the contract term — no month-end surprises. |
| SLA & support | Best-effort uptime target of 99.9% monthly. No contractual SLA on standard plans. | SLA & human supportContracted uptime target on production paths, with service credits if we miss. Email gets a human reply within 4 business hours, faster on incidents. Direct Slack Connect channel for $25K/mo+. |
| Capacity | Shared pool with per-key throughput caps: default 600 req/min, 1M tok/min, 8 parallel. | Dedicated capacityReserved per-key throughput so a noisy neighbor in the shared pool can't slow your prod traffic. Burst capacity scales with your contract. Optional region pinning for data-residency requirements. |
| API & models | OpenAI-compatible API · 95 models · official client SDKs. | Identical — your existing integration keeps working. |
Same API, real billing
Same OpenAI-compatible API as the self-serve plan, same 95 models, same client SDKs. Start in dev on a self-serve key; once spend is predictable, flip to invoice and your existing integration keeps working — only the billing terms change.
- Start in devself-serve key · prepaid credits
- Spend becomes predictablearound $1K/mo is where we start the conversation
- Flip to invoicesame base_url, same code · terms change
Common questions
Same API surface and same models. Teams plans add invoice billing (net-30 wire / ACH), volume pricing past $5K/mo, a written SLA with service credits, reserved per-key throughput, and a human you can email for support. The API itself is identical, so migration is purely commercial.
We start the conversation at around $1K/mo of expected traffic. Below that, self-serve is the better fit — same API, no setup overhead. Above that, invoicing and a real SLA usually pay for themselves in procurement and reliability terms.
Yes. Our standard DPA is published at /dpa, and we'll review and sign your MSA, BAA, or vendor questionnaire. We're a Delaware corporation, payments processed by Stripe, infrastructure hosted on dedicated bare-metal in Europe (OVH) with US edge.
Dedicated per-key throughput is included on teams plans. Fully self-hosted inference (on your own GPUs or in a colo we operate) is on the roadmap for late 2026 — get in touch if that's a hard requirement and we'll prioritize accordingly.
Talk to a human
Email raullen@machinefi.com with rough monthly spend, model mix, and any compliance requirements. A founder replies — usually same business day.
raullen@machinefi.com