Architecture Updated April 2026

BYOK vs Shared AI Credits

When evaluating enterprise AI tools, one of the most consequential decisions is whether to connect your own OpenAI API key or rely on the vendor's pooled credits. The choice affects cost transparency, data isolation, and how quickly you can revoke access.

ChatGridAI supports BYOK on every plan All guides
Cost transparencyBYOK: pay OpenAI at cost with full usage visibility; shared credits: pay vendor markup, less granular data
Revocation controlBYOK: revoke your key instantly from OpenAI; shared credits: cancel the whole subscription
Billing isolationBYOK: your key, your account, separate from all other customers; shared: vendor account pools all customers
Procurement comfortBYOK: direct OpenAI relationship, no vendor middle layer for token billing; shared: vendor controls spend
How Each Model Works

BYOK and shared credits, explained plainly

BYOK: Bring Your Own Key

You create an account directly with OpenAI (or Azure OpenAI), generate an API key, and enter it into the AI tool's admin settings. Every time an employee sends a message, the tool makes the API call using your key. OpenAI sees your account as the caller and bills you directly. The tool vendor receives a platform fee only - typically a flat per-seat price - and has no markup on token usage.

Your OpenAI account is yours. You can see token usage in the OpenAI dashboard, set spend limits, rotate the key, or revoke it entirely - at any time, independently of the AI tool vendor.

Shared AI Credits

The vendor maintains their own OpenAI account and provisions access to customers from their shared key infrastructure. You pay the vendor a per-seat price that includes bundled token usage. The vendor pays OpenAI based on their total consumption across all customers and marks up the token cost in your seat price.

You typically see usage data only through the vendor's own analytics - not the raw OpenAI billing dashboard. Revoking access means canceling your subscription with the vendor, not rotating a key on your own account.

Side-by-Side Comparison

BYOK vs shared credits - what actually differs

Dimension BYOK Shared Credits
Token billingDirect to OpenAI at costVia vendor at markup
Token cost visibilityFull OpenAI dashboard accessVendor analytics only
Revocation methodRotate/delete key in OpenAICancel vendor subscription
Revocation speedInstantContract-dependent
Billing isolation from other customersComplete - separate accountVendor pools all customers
Direct OpenAI procurement relationshipYesNo - vendor is the account holder
Rate limiting controlSet directly in OpenAIVendor-enforced limits
Vendor dependency for tokensNoneHigh - vendor controls token access
Setup complexityOne-time key entry in adminNone - handled by vendor
When to Use Each

Choosing the right model for your organization

Choose BYOK when...

Your company has an existing OpenAI procurement relationship. Your security team requires direct billing visibility. You need instant revocation without contract negotiation. Your compliance process requires knowing exactly where API calls originate. You want to avoid vendor markup on token costs.

Shared credits work when...

You are a small team without an existing OpenAI account and prefer a single vendor bill. Predictable flat-rate pricing matters more than cost transparency. You trust the vendor's infrastructure deeply and are comfortable with them holding the billing relationship with OpenAI on your behalf.

Important distinction

BYOK means your token billing goes directly to your OpenAI account. It does not mean your data bypasses the vendor's application servers. Your prompts and retrieved documents still flow through the vendor's app layer for auth, RAG, and response handling. If you need your data to bypass a vendor's servers entirely, you need a self-hosted deployment - which is a different architecture altogether.

FAQ

BYOK vs shared credits - common questions

BYOK stands for Bring Your Own Key. In enterprise AI, it means you create your own OpenAI account, generate an API key, and connect it to the AI tool. All model calls go through your key and are billed directly to your account. The AI tool charges a platform fee only with no token markup.
With shared AI credits, the AI tool vendor maintains their own model provider account and resells access to customers. You pay a per-seat fee that covers token usage. The vendor pays OpenAI on your behalf at their aggregate rate and builds the markup into your seat price. You typically do not have a direct billing relationship with OpenAI.
BYOK provides stronger isolation at the billing and revocation level. Your API key is separate from other customers, you can revoke it instantly, and a compromise at the vendor does not affect your OpenAI account. However, BYOK does not mean your data bypasses the vendor's application servers - it still flows through their app for auth and RAG. The main security advantage is billing isolation and revocation control.
Most vendors using shared credits do not publish their markup percentage - it is bundled into the per-seat price. At normal business usage (5 to 15 queries per employee per day), raw OpenAI API costs are typically $1 to $3 per user per month. Vendors bundling this into a $25/seat product are capturing $22 to $24 in margin. With BYOK you pay the $1 to $3 directly to OpenAI plus the platform fee only.

ChatGridAI supports BYOK on every plan.

Connect your OpenAI key in the admin dashboard. Pay OpenAI directly. No token markup.

Start Free Trial More guides

$5/seat/month - 14-day free trial - no credit card required