Skip to content

docs(cognition): add the Cognition provider page - #822

Merged
mateo-berri merged 4 commits into
mainfrom
litellm_cognition_provider_docs
Aug 21, 2026
Merged

docs(cognition): add the Cognition provider page#822
mateo-berri merged 4 commits into
mainfrom
litellm_cognition_provider_docs

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Summary

Companion docs for BerriAI/litellm#37743, which gives Cognition its own provider identity instead of routing it as custom_llm_provider: openai. Adds docs/providers/cognition.md (the cognition/ route, the SWE model pricing table, SDK and proxy usage, the Anthropic Messages path, and the api_base override), the sidebar entry, and COGNITION_API_KEY / COGNITION_API_BASE rows in the config settings reference.

Pricing on the page matches Cognition's own model list at https://docs.devin.ai/desktop/models, which embeds it as raw JSON: swe-1.7 at $0.50 in / $2.50 out per million with $0.20 cache reads, swe-1.7-lightning at $2.50 / $12.50 with $1.00, swe-1.6 at $0.50 / $2.50 with $0.20. An earlier revision of this page had the Lightning numbers on the plain swe-1.7 row and no row for Lightning at all; BerriAI/litellm#37763 makes the same correction in the cost map. The retired swe-1.5 is not listed. The page also notes that Cognition serves per-customer endpoints, so api_base is usually set per deployment.

The original PR body said this had to merge before the code PR's CI could pass, via tests/documentation_tests/test_env_keys.py. That is not true for the current code diff: the test only collects env var names passed as string literals to os.getenv / get_secret* in .py files under litellm/, and the code PR reads the key through json_provider.api_key_env, with the literal COGNITION_API_KEY living in providers.json. The two PRs can land in either order, though docs reading correctly only once the provider ships argues for merging this one alongside or just after the code PR.

Link to Devin session: https://app.devin.ai/sessions/c27f086d609843cdb6380708ecd31b2f
Requested by: @shivamrawat1

Cognition is now its own provider route on LiteLLM instead of the generic OpenAI-compatible one, so document the cognition/ models, COGNITION_API_KEY, and COGNITION_API_BASE.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@shivamrawat1 shivamrawat1 self-assigned this Aug 8, 2026
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@vercel

vercel Bot commented Aug 8, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview Aug 21, 2026 2:48am

Request Review

…he 5x one

Cognition's model list at https://docs.devin.ai/desktop/models has uid swe-1-7 at
$0.50 in / $2.50 out per million with $0.20 cache reads, and uid swe-1-7-lightning
at $2.50 / $12.50 with $1.00. The page had the Lightning numbers under the plain
swe-1.7 row and no row for Lightning itself.

Matches the cost map correction in BerriAI/litellm#37763.

@mateo-berri mateo-berri left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mateo-berri
mateo-berri merged commit a6cdfa8 into main Aug 21, 2026
3 checks passed
@mateo-berri
mateo-berri deleted the litellm_cognition_provider_docs branch August 21, 2026 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants