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 is easiest to integrate by matching the SDK to the behavior you need:- official Anthropic SDKs for Claude-native
/v1/messagesbehavior - official Gemini / Google AI tooling for Gemini-native request shapes
- official OpenAI SDKs for OpenAI-compatible
/v1routes and Responses-style usage
Recommended SDKs
OpenAI Python
pip install openaiOpenAI Node
npm install openaiOpenAI Go
go get github.com/openai/openai-go/v3Anthropic SDK
Native Claude Messages API support
OpenAI SDK Example
Use this when you are migrating an existing OpenAI-compatible client or want the/v1 compatibility path. For Claude-native or Gemini-native features, use the matching native SDK instead.
OpenAI Go Example
Anthropic SDK Example
Which SDK Should You Use?
| Goal | Recommended path |
|---|---|
| Provider-native behavior | Native provider SDK or route |
| Existing OpenAI-compatible client | OpenAI SDK on LemonData /v1 |
| Portable chat / embeddings | OpenAI-compatible /v1 routes |
| Claude-native features | Anthropic SDK |
| Gemini-native request shapes | Gemini-native API / SDK |
| LangChain / LlamaIndex / Vercel AI SDK | Use the dedicated integration pages |
Best Practices
Choose native routes when behavior matters
Choose native routes when behavior matters
Use Anthropic or Gemini native routes for provider-specific fields, tools, streaming details, and other behavior that should not be translated through another format.
Use OpenAI-compatible `/v1` for migration
Use OpenAI-compatible `/v1` for migration
OpenAI-compatible SDKs are the best path for existing OpenAI-style clients, portable chat, and embeddings. Treat them as a compatibility route, not as the only LemonData API surface.
Keep base URLs explicit
Keep base URLs explicit
Pass LemonData base URLs directly in your client configuration instead of relying on older environment-variable aliases.