VibeAround

Supported AI Providers

Built-in provider profile targets, OpenAI-compatible providers, Anthropic-compatible providers, Gemini-compatible providers, and custom endpoint support.

Documentation notice: these docs are currently generated with Codex and are being actively reviewed, expanded, and refined.

VibeAround provider presets cover common official and compatible APIs. Custom endpoints are available when a provider speaks a supported API shape.

Provider Matrix

ProviderNotes
DeepSeekOpenAI-compatible and bridge routes, model aliases, Claude suffix normalization.
Alibaba DashScopeCoding Plan and Token Plan endpoints.
Moonshot / KimiOpenAI-compatible and Anthropic-style bridge flows.
MiniMaxOpenAI-compatible and Anthropic-style bridge flows.
Xiaomi MiMoToken Plan and regional endpoints with provider quirks handled.
xAI / GrokResponses and Chat variants.
NVIDIA NIMOpenAI-compatible Chat Completions.
Z.AI / GLMBuilt-in compatible endpoint.
Google GeminiNative Gemini API profile.
OpenRouterOpenAI-compatible profile.
Azure OpenAIResponses and Chat deployment routing.
VolcEngineProvider profile support for compatible routes.
Custom endpointBring your own base URL, headers, models, and API kind.

What To Verify Per Provider

For each provider, verify:

  • Base URL.
  • Authentication field.
  • Supported API shape.
  • Model name and aliases.
  • Streaming behavior.
  • Tool or media capability support.
  • Regional endpoint requirements.
  • Error response format.
  • Rate limit behavior.

Choosing A Provider

Choose based on the job:

  • Use a low-cost profile for exploration and small edits.
  • Use a stronger coding model for large refactors or architecture work.
  • Use a provider with predictable regional access for team environments.
  • Use separate profiles for experimental endpoints so stable workflows remain unchanged.

On this page