Tool Integrations
Latest articles in Tool Integrations.
Flatkey Integration Starter: From One Key to Multi-Model Testing
Connect Flatkey to the quickest useful workflow: make a first API call, add Cherry Studio or CC Switch, compare models, and plan the team handoff.
Seedance API for text-to-video product teams
Verify Flatkey auth, base URL, and usage logs with one quickstart request, then swap to the approved Seedance route for async text-to-video evaluation.
Gemini API integration checklist for production apps
A production-ready Gemini API checklist for teams using CC Switch or NewAPI-style clients and one upstream gateway instead of separate Gemini credentials.
OpenAI API access guide for multi-model products: Cherry Studio setup with one key
Set up Cherry Studio with one OpenAI-compatible gateway so your team can use one key and one base URL instead of separate provider credentials.
CrewAI OpenAI-Compatible Router: One Key for Multi-Agent Workflows
Configure CrewAI with an OpenAI-compatible router through Flatkey, then verify base_url, model routes, tools, logs, costs, and rollback.
LangGraph Multi-Model Routing: Gateway Checks for Agent Workflows
Route LangGraph agent nodes across models through Flatkey, with gateway checks for budgets, tools, retries, logs, and rollback.
OpenCode OpenAI compatible provider setup: Route coding-agent models through Flatkey
Configure OpenCode with a custom OpenAI-compatible provider through Flatkey, then verify the base URL, model selection, logs, and rollback path.
Windsurf OpenAI compatible API setup: Route coding-agent traffic through one key
Route OpenAI-compatible app and SDK calls from Windsurf-driven projects through Flatkey without assuming a native Windsurf provider screen.
Cursor OpenAI Compatible API Setup: Base URL, Model Names, and Usage Logs
Set up a Cursor OpenAI compatible API path carefully: verify base URL support, model names, usage logs, BYOK policy, and rollback before routing traffic.
Vercel AI SDK custom provider base URL: Flatkey Setup Notes
Set a Vercel AI SDK custom provider base URL for Flatkey with provider setup, model aliases, streaming checks, tool checks, usage proof, and rollback.
Open WebUI OpenAI API base URL: Flatkey Setup Guide
Configure Open WebUI with Flatkey as an OpenAI-compatible router: base URL, API key, model filters, curl preflights, streaming checks, and usage review.
Continue.dev OpenAI compatible provider: Flatkey Setup Guide
Set up Continue.dev with Flatkey as an OpenAI-compatible provider: config.yaml, apiBase, model aliases, roles, tool-use checks, endpoint fallback, and usage review.
Roo Code OpenAI compatible API: Flatkey Setup Guide
If you still maintain Roo Code installs, the Roo Code OpenAI compatible API route is mostly a configuration surface: provider type, Base URL, API key, and Model ID. The production risk is the part that is easy to miss. Roo Code's provider docs require native O
Claude Code API Router Setup: Base URL, Models, and Usage Logs
A Claude Code API router setup is not the same as changing an OpenAI SDK base URL. Claude Code speaks the Anthropic Messages gateway shape, so the important checks are the router root, the credential header, the model name Claude Code will send, and the usage records that prove requests are reaching
Cline OpenAI compatible API: Flatkey Setup Guide
If you are setting up the Cline OpenAI compatible API provider, the visible fields are simple: Base URL, API key, and model ID. The production risk is less obvious. A wrong path, stale model alias, unchecked model capability, or unowned key can make Cline fail only after a developer starts relying o
CC Switch Claude Code Setup With Flatkey and NewAPI
Set up CC Switch Claude Code routing with Flatkey and NewAPI: choose app, key field, base URL, model fetch, usage-log check, and troubleshooting.
Build faster with one AI gateway.
Use flatkey.ai to manage models, keys, billing, and observability from one API platform.
Get started