feat(providers): add Tokenify as an OpenAI-compatible provider

[BeEdward]

TLDR

Problem this solves:

• Tokenify users can only reach it through openai/ plus a manual api_base
• No cost tracking or Admin UI entry for Tokenify

How it solves it:

• Registers tokenify through the JSON provider config (openai_like/providers.json)
• Declares chat completions, responses and Anthropic messages, as Cortecs (feat(providers): add Cortecs as an OpenAI-compatible provider #43872) does

User Flow

Before: a developer has to know the base URL and route through the generic OpenAI provider

1. They call litellm.completion(model="tokenify/deepseek/deepseek-v4-pro", ...)
2. LiteLLM raises "LLM Provider NOT provided" because tokenify is not a known prefix
3. They fall back to model="openai/deepseek/deepseek-v4-pro" with api_base="https://api.tokenify.dev/v1"

After: the provider prefix works on its own

1. They set TOKENIFY_API_KEY and call litellm.completion(model="tokenify/deepseek/deepseek-v4-pro", ...)
2. The request goes to https://api.tokenify.dev/v1/chat/completions with their key and returns a normal completion
3. litellm.responses(...) and litellm.anthropic.messages.acreate(...) with the same model reach /v1/responses and /v1/messages
4. In the Admin UI, "Tokenify" appears in the provider list with API Base and API Key fields

Pre-Submission checklist

• I have added meaningful tests (tests/unit/llms/openai_like/test_tokenify_provider.py, mirroring the Cortecs tests)
• The test files covering my change pass locally: pytest tests/unit/llms/openai_like/test_tokenify_provider.py tests/unit/llms/openai_like/test_cortecs_provider.py → 14 passed; ruff check and ruff format --check clean
• My PR passes all required CI/CD checks
• My PR's scope is as isolated as possible; it only adds one provider
• Greptile Confidence Score of at least 4/5

Type

🆕 New Feature

Docs: https://www.tokenify.dev/docs/ — models: GET https://api.tokenify.dev/v1/models. A docs page for docs.litellm.ai can follow in BerriAI/litellm-docs once this lands.

🤖 Generated with Claude Code

[CLAassistant]

All committers have signed the CLA.

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Adds a new OpenAI-compatible provider to the routing system.

The PR appears safe to merge; no outstanding findings remain.

Summary

Adds Tokenify as an OpenAI-compatible provider, with model pricing, endpoint declarations, Admin UI fields, and request tests.

• The latest change makes the five expected model IDs explicit so the tests detect missing price entries.

_{Reviews (4) · Last reviewed commit: "test(providers): pin the expected Tokeni..."}

[codspeed]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing BeEdward:feat/add-tokenify-provider (f28f328) with main (fe9b6fd)¹}

Footnotes

1. No successful run was found on main (615ed79) during the generation of this report, so fe9b6fd was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[BeEdward]

@greptileai

[BeEdward]

@greptileai

[BeEdward]

@greptileai

[BeEdward]

Hi maintainers — this is ready for review whenever you have a moment: all required checks pass, Greptile is at 5/5, and the CLA is signed. It follows the Cortecs provider (#43872): a JSON openai_like entry, cost-map entries for the five models, and unit tests. Happy to adjust anything, or for you to land it as an internal copy if that is easier. Thank you!