Documentation Index
Fetch the complete documentation index at: https://docs.lemondata.cc/llms.txt
Use this file to discover all available pages before exploring further.
Overview
LemonData supports three native API formats with a single API key. Choose the format that best fits your use case - no configuration changes needed.OpenAI Format
/v1/chat/completions
Standard format, widest compatibilityAnthropic Format
/v1/messages
Extended thinking, native Claude featuresGemini Format
/v1beta/models/:model:generateContent
Google ecosystem integrationWhy Multi-Format?
| Benefit | Description |
|---|---|
| No SDK switching | Use any model with your preferred SDK |
| Native features | Access format-specific capabilities |
| Easy migration | Switch from official APIs with just a base URL change |
| Single billing | One account, one API key, all formats |
Format Comparison
| Feature | OpenAI | Anthropic | Gemini |
|---|---|---|---|
| Endpoint | /v1/chat/completions | /v1/messages | /v1beta/models/:model:generateContent |
| Auth Header | Authorization: Bearer | x-api-key | Authorization: Bearer |
| System Prompt | In messages array | Separate system field | In systemInstruction |
| Extended Thinking | ❌ | ✅ | ❌ |
| Streaming | ✅ SSE | ✅ SSE | ✅ SSE |
| Tool Calling | ✅ | ✅ | ✅ |
| Vision | ✅ | ✅ | ✅ |
OpenAI Format
The most widely compatible format and the default starting point for most new integrations. Works across the broadest set of LemonData models.- General use
- Existing OpenAI SDK integrations
- Maximum compatibility
Anthropic Format
Native Anthropic Messages API. Required for Claude-specific features like extended thinking.Extended Thinking (Claude Opus 4.6)
Only available in Anthropic format:- Claude-specific features
- Extended thinking mode
- Native Anthropic SDK users
Gemini Format
Native Google Gemini API format for Google ecosystem integration.Streaming
- Google Cloud integrations
- Existing Gemini SDK code
- Native Gemini features
/upload/v1beta/files, /v1beta/files, /v1beta/files:register, and /v1beta/cachedContents are available on the native Gemini route. Files use Gemini File API-compatible upstream channels; explicit cache resources can also route through Vertex AI channels. Resources created through LemonData are bound to the same upstream channel/key for later generateContent calls.
Tool Compatibility Boundary
Function tools can be converted between formats when the target route supports them. Provider-native tools must stay on their native route:- OpenAI Responses hosted and native tools such as
tool_search,web_search,file_search,code_interpreter, MCP, shell/apply_patch, and computer-use tools require/v1/responses. - Anthropic server/native tools such as
web_search_*,web_fetch_*,code_execution_*,tool_search_*, bash, computer-use, and text-editor tools require/v1/messages. - Gemini built-in tools such as
googleSearch,codeExecution,urlContext,computerUse, and similartoolsfields require/v1beta.
Choosing the Right Format
Migration Guides
From OpenAI Official API
From Anthropic Official API
From Google AI Studio
Cross-Model Compatibility
The magic of LemonData: use any SDK with any model. The gateway automatically handles format conversion.Any SDK → Any Model
OpenAI SDK → All Models
Industry Comparison
| Platform | OpenAI Format | Anthropic Format | Gemini Format | Responses API |
|---|---|---|---|---|
| LemonData | ✅ All models | ✅ All models | ✅ All models | ✅ All models |
| OpenRouter | ✅ All models | ❌ | ❌ | ❌ |
| Together AI | ✅ All models | ❌ | ❌ | ❌ |
| Fireworks | ✅ All models | ❌ | ❌ | ❌ |
While cross-format works for most features, format-specific features (like Anthropic extended thinking) require the native format.