BYOK vs Platform Keys | 0xClaw

The API Key Dilemma

When you set up AI infrastructure, one of the first decisions you'll make is how to handle API keys. Do you use your own keys from providers like OpenAI and Anthropic? Or do you use platform-provided keys with a bundled credit system?

This goes beyond billing. It affects your security posture, cost structure, and operational flexibility.

What is BYOK?

Bring Your Own Key (BYOK) means you create API keys directly with AI providers (OpenAI, Anthropic, Google, and others) and plug them into your infrastructure. The platform routes your requests through these keys without markup.

How BYOK Works on 0xClaw

1. Create an API key at platform.openai.com or console.anthropic.com
2. Add the key to your 0xClaw dashboard
3. All API calls route through your key, and 0xClaw charges $0 markup

Your App → 0xClaw Gateway → OpenAI API (your key)
                ↓
        Zero platform fee

What Are Platform-Provided Keys?

Platform-provided keys are pre-configured API keys managed by the platform. You do not need to create accounts with individual AI providers. Instead, you get a unified credit system.

How Platform Keys Work on 0xClaw

1. Subscribe to the current Pro plan listed on the pricing page
2. Receive the current monthly credit allocation shown on the pricing page
3. Each API call deducts credits based on the model and token usage
4. Top up with credit packs if needed

Head-to-Head Comparison

| Factor | BYOK (Lite Plan) | Platform Keys (Pro Plan) | |--------|-------------------|--------------------------| | Monthly Cost | Current Starter plan + actual API usage | Current Pro plan with included credits | | API Markup | 0% | Credits cover API costs | | Setup Complexity | Manage keys per provider | Zero key management | | Provider Access | Any provider you have keys for | All supported models included | | Billing | Separate bills per provider + 0xClaw | Single unified bill | | Best For | High-volume, cost-conscious teams | Teams wanting simplicity |

When to Choose BYOK

BYOK makes sense when:

• You're already paying for API keys and don't want double billing
• You have negotiated enterprise rates with AI providers
• You need strict API key rotation policies for compliance
• Your usage is high volume — at scale, direct provider pricing wins
• You want maximum transparency in per-call costs

When to Choose Platform Keys

Platform keys make sense when:

• You're getting started and don't want to manage multiple provider accounts
• Your team is small and operational simplicity matters more than marginal savings
• You want predictable costs — credits make budgeting straightforward
• You use multiple models frequently — one credit system vs. multiple invoices

The Math: A Real-World Example

Let's say you make 10,000 API calls per month using GPT-4o and Claude 3.5 Sonnet:

BYOK Route

• 0xClaw Starter: see current pricing page
• OpenAI API costs: ~$8/month (direct pricing)
• Anthropic API costs: ~$6/month (direct pricing)
• Total: current platform subscription plus direct provider costs

Platform Keys Route

• 0xClaw Pro: see current pricing page (includes the current monthly credit allocation)
• API costs: covered by credits
• Total: current platform subscription

At this usage level, the costs are nearly identical. As usage scales up, BYOK's zero-markup advantage usually becomes more noticeable.

The Bottom Line

There is no universally "better" option. Choose based on your stage:

• Starting out? Go with the current bundled-credit plan for simplicity
• Scaling up? Switch to BYOK plus the lower-overhead plan for cost optimization
• Enterprise? BYOK with negotiated provider rates

0xClaw supports both models, and you can switch anytime without re-deploying your infrastructure.

One extra security lesson is worth adding: secret ownership affects blast radius. If an AI agent can read provider keys, repository tokens, or cloud credentials, outbound control and audit visibility matter just as much as price. The recent Claude Code sandbox bypass analysis is a good reminder that runtime guardrails should not be the only thing protecting credential-bearing workflows.

Compare plans and find your fit at www.0xclaw.dev/pricing.