Skip to contentК содержанию
LLMcode
ModelsМоделиPricingЦеныInstructionsИнструкцииDocsДокументацияNewsНовости
ENRU
EnglishРусский
Sign inВойтиCreate accountСоздать аккаунтAccountАккаунт
MenuМеню
ModelsМоделиPricingЦеныInstructionsИнструкцииDocsДокументацияNewsНовостиCreate accountСоздать аккаунт
LLMcode

Model names in the API are LLMcode profiles with their own routing. They do not mean direct access to the same-named models of OpenAI LLC or Anthropic PBC. Trademarks belong to their owners. The service is independent and is not affiliated with OpenAI or Anthropic.Названия моделей в API — профили LLMcode с собственной маршрутизацией. Они не означают прямой доступ к одноимённым моделям OpenAI LLC или Anthropic PBC. Товарные знаки принадлежат их правообладателям. Сервис независим и не аффилирован с OpenAI/Anthropic.

CatalogКаталог

ModelsМоделиPricingЦеныInstructionsИнструкцииDocsДокументацияKey checkПроверка ключа

LegalДокументы

OfferОфертаPrivacyКонфиденциальностьConsentСогласиеAcceptable useДопустимое использованиеRefundВозврат

LearnМатериалы

GuidesГайдыComparisonsСравненияAlternativesАльтернативыIntegrationsИнтеграцииUse casesСценарииGlossaryГлоссарийNewsНовостиRSSTelegramTelegram-канал
HomeГлавнаяModelsМоделиPricingЦеныSign inВойтиAccountАккаунт
LLMcode/Comparisons/OpenAI-compatible vs native Anthropic Messages

Comparison

OpenAI-compatible vs native Anthropic Messages

LLMcode exposes the same models over two interfaces: an OpenAI-compatible shape and native Anthropic Messages. The model is the same; the client and the endpoint differ.

Updated 2026-11-16

CriterionOpenAI-compatibleAnthropic Messages
Base URLhttps://llmcode.io/v1https://llmcode.io (no /v1)
AuthAuthorization: Bearerx-api-key + anthropic-version header
Endpoints/chat/completions, /responses, /embeddings/v1/messages
Best forOpenAI SDK, Cursor, LangChain, n8nClaude Code, Anthropic SDK clients
StreamingChat completionsMessages

Same catalog, two dialects

The published profiles are identical across both interfaces. You choose the protocol by which client you already use, not by which model you want.

The model field accepts the same profile name in both shapes.

Which to pick

If your codebase imports the OpenAI SDK or a tool speaks that protocol, use the compatible shape and keep the client unchanged.

If your tool is Anthropic-native, such as Claude Code, use Messages to keep tool calling and thinking parameters native.

Where they differ in practice

Responses and embeddings endpoints exist only on the compatible side. Anthropic Messages has no embeddings counterpart.

Streaming is supported for chat and messages. Responses with stream: true is not available in this version.

Published model prices

USD per 1M tokens. The numbers come from the public catalog on every page rebuild — this is the sale price, not an estimate.

ModelInputOutputCache
Claude Opus 5.5$2.70$8.00$0.14
DeepSeek Flash$0.50$2.00$0.01
Claude Sonnet 5.5$1.33$6.67$0.07
DeepSeek V4 Pro$2.20$6.60$0.07

Top-up from $10, balance in USD. 1 USD = 1,000,000 UT. No subscription and no auto-charge.

Questions

Do I pay differently per interface?

No. The price is per model and per token, identical across both protocols.

Can one key use both?

Yes. A key is not tied to a protocol.

Which base URL for the OpenAI SDK?

https://llmcode.io/v1 with a Bearer key.

Which base URL for Claude Code?

https://llmcode.io with ANTHROPIC_AUTH_TOKEN set to your key.

See also

OpenAI-compatible guideClaude API guide

One key for every model

OpenAI- and Anthropic-compatible endpoints, balance in USD, top-up from $10.

Create accountPricing
Base URL
https://llmcode.io/v1
Key format
sk-llmcode-…