We're taking a moment to make VibeKey even better.
Top-ups and new purchases are paused during this quick pit stop — your existing balance is still ready to go. We'll be back before you know it.
Use your VibeKey as an OpenAI-compatible endpoint. The production base URL is https://www.usevibekey.com/v1. For local development, use http://localhost:3000/v1.
When you set a model, you are picking a lane — not a specific model. VibeKey routes to the best available provider behind the scenes.
Auto routes are not fixed model guarantees. VibeKey may update the underlying models as provider pricing, reliability, availability, and quality change. The dashboard shows the actual provider and model used for each request.
Usage costs vary per request. Actual cost depends on the model, tokens, and routing. Provider pricing may change. Spend caps and prepaid balance are your primary protection against unexpected usage.
Comparable model options
VibeKey is not tied to one provider. Each lane can use comparable models based on your project settings, provider availability, pricing, and safety controls.
Lower-cost lane:
Balanced lane:
Premium lane:
Best lane:
New providers and newly released models launch as opt-in first. They are not added to auto-routing until production behavior, pricing, billing, and Sensitive Mode behavior are verified.
Your usage dashboard shows the actual provider and model used for every request.
VibeKey applies different rate limits based on how traffic is classified. IDE-classified clients (Cursor, OpenClaw, Hermes-compatible tools) get higher burst allowances.
Default traffic
300 req/min
Baseline rate for all API keys. Applies to general-purpose clients, SDK calls, curl, and non-IDE integrations.
IDE-classified traffic
1,200 req/min
Higher burst allowance for IDEs and coding agents (Cursor, OpenClaw, Hermes). Detection happens via the User-Agent header and the optional x-vibekey-source header.
Override default limits via environment variables: VIBEKEY_RATE_LIMIT_DEFAULT_RPM and VIBEKEY_RATE_LIMIT_IDE_RPM. Limits apply per API key and reset on a sliding 60-second window. Rate-limited requests include standard Retry-After and X-RateLimit-* headers.
VibeKey does not store raw prompts by default. Requests are transmitted to third-party model providers according to your selected model and project settings.