One OpenAI-compatible surface
Ship Chat Completions and Models against a single gateway. Keep your existing SDKs — only the base URL and key change.
OpenAI-compatiblePrepaid USD
Fabrix
Transform how your org
runs AI completions
Stop wiring every vendor separately. Fabrix gives product teams one OpenAI-compatible gateway — with prepaid wallets, project budgets, and providers kept out of client apps.
Benefits
The gateway advantage that changes delivery
Eliminate multi-vendor sprawl, put USD spend under prepaid control, and scale completions across teams without leaking providers into client apps.
Prepaid spend you can see
Fund an Organisation wallet in USD. Reserves hold cost up front; settlement writes the ledger when the response lands.
Project budgets & keys
Isolate teams with Projects, rotate one live API key, and stop runaway burn with soft alerts and hard monthly caps.
Providers stay concealed
Clients ask for apparatus-core — never the vendor id or base URL. Admins remap upstream without breaking apps.
Settled per request
Every completion records tokens, customer charge, latency, and billing mode — so finance and ops share one source of truth.
Provisioned, not self-serve
Platform Admins create Organisations and grant Model Access. Access stays intentional; billing stays tied to a real company.
Why Fabrix
Built for real organisational control
From admin invite to concealed completions — every step is designed so product, finance, and platform stay aligned.
FFabrix · Provision
Organisationcreated
Model Accessallow-listed
Org Loginissued
Capabilities
Surfaces that actually move the needle
Every capability is tailored to how organisations ship AI — not a seat-based toolkit bolted on later.
Automation
Drop-in Chat Completions
Transform repetitive multi-vendor wiring into one stable gateway. Streaming SSE, tools, and the completions shape your stack already expects — with Fabric Model slugs in the model field.
/v1/chat/completions/v1/modelsSSE streaming
Control plane
Organisation portal that ops can run
Organisation Login manages Projects, API Keys, Razorpay top-ups, low-balance alerts, and appeals — one shared dashboard identity per company.
Projects & keysTop-upsUsage ledger
Growth
Prepaid wallets with reserves
Accelerate shipping without opaque cloud bills. Top up USD, reserve before the call, settle to actual tokens — with optional Project budgets that reset each month.
USD walletPer-request reserveMonthly caps
Platform
Fabric Models & overrides
Define customer-facing slugs, map Provider Models, grant Model Access, and set USD token prices or per-Organisation overrides — without leaking vendors to clients.
Fabric slugsModel AccessPrice overrides
Drop-in
Same SDK. Different base URL.
Authenticate with a Project API Key. Request a Fabric Model slug. Stream or not — Fabrix speaks the Chat Completions shape your stack already expects.
Quickstart in docs →curl -X POST https://gateway.fabrix1.com/v1/chat/completions \
-H "Authorization: Bearer $FABRIX_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "apparatus-core",
"messages": [
{"role": "user", "content": "Summarise today’s ops brief."}
]
}'Work process
How we get your org live on Fabrix
Every step is designed to minimize disruption while keeping billing and access intentional from day one.
Step 1
Invite & provision
Platform Admin creates the Organisation, grants Model Access, and issues a temporary Organisation Login.
Step 2
Fund the wallet
Commercial orgs purchase top-up packages via Razorpay. Funds credit a single Organisation Balance in USD.
Step 3
Scope a Project
Create a Project, set an optional monthly budget, and rotate the active API Key shown once.
Step 4
Ship completions
Point any OpenAI-compatible SDK at Fabrix. Request apparatus-core — never the upstream vendor name.
Step 5
Monitor the ledger
Review tokens, charges, latency, and billing mode per settled call across Organisations and Projects.
Step 6
Optimize access
Remap providers, adjust Model Access, tune budgets, or suspend orgs — without rewriting client apps.
Why choose us
Fabrix is the clear choice for org gateways
Compared with DIY multi-provider setups, Fabrix delivers one surface, prepaid control, and provider concealment — without the sprawl.
Fabrix
A provisioned OpenAI-compatible gateway with prepaid USD, project budgets, and Fabric Model concealment built in.
- Single OpenAI-compatible gateway for every team
- Prepaid USD wallet with per-request reserve & settle
- Project keys, budgets, and a shared usage ledger
- Fabric Model slugs — providers stay concealed
- Platform-admin Model Access and remapping
- Provisioned Organisations — no open signup surface
DIY / raw vendor keys
Teams often stitch providers directly into apps — leaving spend opaque and remaps expensive.
- Scattered vendor keys across apps and secrets managers
- Opaque cloud bills with no org-level prepaid control
- No shared project budgets or hard monthly caps
- Upstream model ids and base URLs leak into clients
- Every remap forces app changes and redeploys
- Self-serve sprawl without intentional provisioning
Use cases
How teams put Fabrix to work
Outcome-led patterns we see when organisations centralise completions behind one gateway.
Product engineering
Ship on Fabric slugs, not vendor lock-in
Product teams were blocked waiting on each upstream integration. With Fabrix they call apparatus-core from one base URL while Platform Admins remap providers behind the scenes — without redeploying every client.
Finance & ops
See USD burn before it surprises you
Finance needed a ledger they could trust. Prepaid top-ups, reserves, and Project budgets give a clear view of Organisation spend — with Razorpay invoices for successful wallet credits.
Voices
What teams need from a gateway
Illustrative personas — the jobs Fabrix is built to serve across platform, finance, and product.
“We stopped explaining which vendor each service was on. Teams call Fabrix, budgets stay per Project, and remaps happen without a release train.”
“Prepaid USD plus a real ledger finally made AI spend reviewable. Soft alerts catch burn early; hard caps stop runaway Projects.”
“Same OpenAI SDK, new base URL, Fabric Model slug. Streaming still works. We were productive the afternoon we got keys.”
Quotes are illustrative product voices, not attributed customer testimonials.
Packages
Choose how your org bills completions
Fabrix does not sell seats. These packages describe billing modes — prepaid wallets, project budgets, and internal metering.
Commercial
Organisation wallet
Prepaid USD for companies that bill usage to a shared balance.
- Razorpay top-up packages
- Per-request reserve & settle
- Fabric Model token prices
- Optional Price Overrides
- Full usage & ledger history
Scoped
Project budgets
Isolate teams with Projects, keys, and monthly spend controls.
- One live API key per Project
- Soft thresholds & hard caps
- Calendar-month reset (Asia/Kolkata)
- Shared Organisation wallet
- Rotate keys anytime
Internal
Internal metering
Meter usage with zero customer charge for internal Organisations.
- Tokens & upstream cost tracked
- Top-ups disabled
- Model Access still enforced
- Suspension & appeals apply
- Same gateway surface
FAQ
Got questions? Clear answers.
Considering Fabrix for your organisation? These are the questions that usually come up before the first completion.
Once a Platform Admin provisions your Organisation and you rotate a Project API Key, any OpenAI-compatible SDK can call Chat Completions. Most teams land a first completion the same day they get access.
No. Product teams keep using familiar Chat Completions clients. Platform Admins handle Fabric Models, Model Access, and upstream mapping — clients never see vendor URLs.
Project keys are shown once and stored hashed. Responses echo Fabric Model slugs only. Upstream provider credentials and base URLs stay on the admin side of the gateway.
Point the client at the Fabrix base URL, swap in a Project API Key, and request a Fabric Model slug such as apparatus-core. Streaming and the completions shape stay the same.
Yes. Start with one Project and a modest wallet top-up. Add Projects, budgets, and Model Access as more teams come online — without changing the client contract.
Fabrix estimates cost, holds a Reserve (with buffer), then settles to actual tokens when the response finishes. Debits use Fabric Model USD token prices or a per-Organisation override.
Reach out anytime
Start your organisation on Fabrix
Join teams that ship completions through one gateway — prepaid USD, project budgets, and providers concealed. Open the dashboard or read the docs.