LiteLLM
by BerriAI Model router in Model APIs & inference
Berrie AI Incorporated · litellm.ai since 2023 · who's behind it
Open-source Python SDK and self-hosted AI gateway from BerriAI that puts 100+ model providers behind one OpenAI-compatible API, with virtual keys, spend tracking, budgets, fallbacks, guardrails and an MCP gateway.
Best for Teams that want one OpenAI-compatible endpoint over many providers on their own infrastructure, with per-key budgets, model allowlists and an MCP gateway.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Models. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. An MIT-licensed gateway that puts 100+ model providers behind one OpenAI-compatible API, with virtual keys, budgets, fallbacks and an MCP gateway, released several times a week. Its security record is the main limitation. Two PyPI releases carried a credential stealer on 24 March 2026, and 30 GitHub advisories followed in 12 months, five of them critical.
Facts
Access how an agent reaches and pays for it
- Transport
- HTTP
- Auth
- API key
- Pricing
- Freemium
- x402
- No
- Licence
- MIT, except the enterprise/ directory, which is under its own licence and needs an Enterprise licence key
- Capabilities
- inference.router obs.gateway agent.mcp-client guard.pii
Where it lives packages, source, docs and releases
- Packages
pypilitellmdockerdocker.litellm.ai/berriai/litellm- Docs
- docs.litellm.ai
- llms.txt
- published
- Last release
- GitHub stars
- 63k
- PyPI / week
- 22.5M
From our research 10 facts checked against the vendor's pages
- Surfaces
- Python SDK (
litellm.completion()and async versions) and a self-hosted gateway on port 4000 with OpenAI, Anthropic Messages, MCP and A2A endpoints, an Admin UI at /ui and Postgres for keys and spend - Routing
- Load balancing, retries, cooldowns and fallbacks across deployments and providers, tag-based routing and an auto router
- Credentials
- Master key with full admin rights. Virtual keys with model, route, MCP server, budget, rate and expiry limits, blockable. Rotation with a grace period is Enterprise only
- Errors
- OpenAI-shaped
errorenvelope with a stringcode. Gateway 429s carryretry-after,rate_limit_typeandreset_at; provider 429s don't. Management API answers RFC 9457 problem+json - MCP gateway
- One endpoint for registered MCP servers with access by key, team or organisation, OAuth patterns, guardrails before and after tool calls, and a tool-search mode that exposes four virtual tools
- Telemetry
- None by default. Usage telemetry (v1.107.0 and later) counts requests and Admin UI page views only when the operator turns groups on and picks their own table or HTTP endpoint, with
LITELLM_TELEMETRY_DISABLED=trueto lock it off. Start-up fetches the model price map from GitHub unlessLITELLM_LOCAL_MODEL_COST_MAP=True - Release support
- The four most recent stable minor lines get patches. A new minor line ships roughly weekly. Release notes carry a breaking changes section
- Image security
- GHCR images signed with cosign; the signing key changed in the 24 October 2026 patch releases. No SBOM or provenance attestation, and the default image runs as root (a
-non_rootvariant exists) - Enterprise
- Annual licence through sales. SSO beyond five users, SCIM, audit logs, key rotation, IP allowlists, team-scoped guardrails, 72-hour security patch SLA. 30-day trial with no card
- Certifications
- SOC 2 Type II per the data security page, report through trust.litellm.ai
Facts verified 6 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- MIT core, self-hosted, with no telemetry when self-hosted per the data security page
- Virtual keys limited by model, route, MCP server, budget, rate and expiry, and blockable at once
- Every proxy serves Swagger, ReDoc and /openapi.json, and the docs have llms.txt with a Markdown twin of every page
- Error reference tells a gateway 429 (with
retry-after,rate_limit_type,reset_at) from a provider 429 - v1.108.1 on 5 November 2026, 125 tags since 8 August, and four stable minor lines supported with patches
Weaknesses
- litellm 1.82.7 and 1.82.8 on PyPI carried a credential stealer for about 40 minutes on 24 March 2026
- 30 GitHub advisories from 6 November 2025 to 6 November 2026, five critical, including unauthenticated SQL injection fixed in 1.83.7
- Key rotation, audit logs and SSO beyond five users need an Enterprise licence, priced only through sales
- Breaking changes ship in weekly minor releases on the 1.x line, and lines older than the latest four stop getting fixes
- The default Docker image runs as root, and the Swagger, ReDoc and OpenAPI pages are public until switched off
Before you call it notes for agents
- Pin an exact litellm version or image digest, verify the cosign signature, and never install an unpinned latest in CI
- Give each agent a virtual key limited to its models, routes and MCP servers, with a budget and an expiry
- Treat a 429 with
retry-afteras the gateway's own limit and wait that long; a 429 without it came from the provider - Set
NO_DOCS,NO_REDOCandNO_OPENAPIto True in production, and use the-non_rootimage variant - Set
LITELLM_LOCAL_MODEL_COST_MAP=Truewhere egress is blocked, since start-up otherwise fetches the price map from GitHub
Who's behind it provenance 49/100
- Legal entity namedBerrie AI Incorporated20/20
- Domain agelitellm.ai, registered 2023-08-07 (3 years)7/15
- Endpoint on the vendor's domain is not on litellm.ai0/15
- Terms of servicenot found0/10
- Privacy policyread, states 0 of the 8 things a reader expects4/10
- Status pagenot found0/10
- Changelogpublished10/10
- security.txtnot found0/10
- People named2 named with their role, 2 with a public profile10/10
- Support routea support address, help pages, a community5/5
Terms and privacy, as read
Terms of service none to read
TL;DR We found no terms of service published for this product, so there is nothing to read and the check scores 0.
Privacy policy gives no date, states 0 of 8
TL;DR Gives no date. States 0 of the 8 things a reader expects, and we didn't find what is collected, how long data is kept, who else gets the data, whether data is sold, people's rights, a privacy contact or 1 more. The rules found no clause to flag.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
Not found in the text.
The basic statement a privacy policy exists to make.
Says how long data is kept
Not found in the text.
Says when data sent to the service is deleted.
Says who else receives the data
Not found in the text.
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising
Not found in the text.
A plain statement either way.
Says what rights people have over their data
Not found in the text.
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact
Not found in the text.
An address or officer to send a request to.
Says where data is transferred or stored
Not found in the text.
The countries data goes to and the safeguard used.
The document · read 2026-11-06 · 864 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
The data security page names the legal entity as Berrie AI Incorporated, with krrish@berri.ai as the security contact.
The gateway is software the operator runs, so there's no vendor endpoint and no status page.
No terms of service or privacy policy found on www.litellm.ai (/terms, /privacy and /legal return 404). The data security page in the docs covers self-hosted data handling.
www.litellm.ai/.well-known/security.txt and the docs host both return 404. Reports go to GitHub private vulnerability reporting under security.md.
RDAP for litellm.ai gives a registration date of 2023-08-07.
Rechecked 2026-11-06: www.litellm.ai/terms, /privacy, /legal, /terms-of-service and /privacy-policy all return 404, and neither host serves security.txt. Both robots.txt files allow all.
Checked 2026-11-06 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Krrish DholakiaCo-founder and CEO
- Ishaan JafferCo-founder and CTO
Berrie AI Incorporated (LiteLLM) on LinkedIn @litellm GitHub
Raised $1.6M in total, as of November 2026 source
Backed byY Combinator,Gravity VC,Pioneer Fund
Researched 6 November 2026 from public pages. Founders, roles and their LinkedIn, X and GitHub links are from LiteLLM's about page (read 6 November 2026), which names Berrie AI Incorporated, a Y Combinator Winter 2023 company in San Francisco. The data security page names the same entity and krrish@berri.ai as the security contact. Funding is the about page's own statement of a $1.6M seed round from Y Combinator, Gravity Fund and Pioneer Fund; no later round was found on the about, pricing or enterprise pages. No other data/humans file covers BerriAI. A web search on 6 November 2026 found no later round and no stated valuation, only database pages, which aren't used. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-07 16:01 UTC
- github
BerriAI/litellmv1.108.2, released 2026-11-06 - pypi
litellm1.108.2, released 2026-11-06 - GitHub stars 63k
- PyPI downloads a week 22.5M
- security.txt none · 1 hour ago
- llms.txt answers · 2 hours ago
Pages we watch
| Page | Kind | Last checked | Last changed |
|---|---|---|---|
| docs.litellm.ai/release_notes | changelog | 3 hours ago · 200 | no change seen |
| www.litellm.ai/pricing | pricing | 3 hours ago · 200 | no change seen |
| docs.litellm.ai/docs/data_security | privacy | 3 hours ago · 200 | no change seen |
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/litellm.json
Notable
- On 24 March 2026 litellm 1.82.7 and 1.82.8 were uploaded to PyPI with a credential stealer after a publishing token leaked through the Trivy compromise. They were live for about 40 minutes and the official Docker image wasn't affected source
- GitHub advisory GHSA-5mg7-485q-xm76 (critical) covers the two releases, and v1.83.0 on 30 March was the first release from the rebuilt CI/CD pipeline source
- OSV lists 30 GitHub advisories for litellm published from 6 November 2025 to 6 November 2026, five critical, ten high, six moderate and nine low. Three came on 27 October 2026, among them a privilege escalation from internal_user to proxy_admin fixed in 1.100.4, 1.101.3, 1.102.2 and 1.103.1 source
- security.md runs a bug bounty of $500 to $3,000 for supply-chain and unauthenticated-access reports, and closes any report sent without a reproduction video source
- The four most recent stable minor lines get patch releases, and a new minor line ships roughly every week, per the policy in effect since 29 June 2026 source
- The package fetches its model price map from raw.githubusercontent.com at start-up unless
LITELLM_LOCAL_MODEL_COST_MAP=Trueis set (https://github.com/BerriAI/litellm/blob/main/litellm/__init__.py). Usage telemetry, added in v1.107.0, is off by default and goes only to the operator's own table or endpoint source - v1.108.0 (4 November 2026) and v1.108.1 (5 November) are the newest stable tags. Release notes from 4 November say v1.106.7 removes the Lens beta, so
lensWorker.enabledmust come out of Helm values before upgrading source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using LiteLLM, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used LiteLLM, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 6 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 6 November 2026 | 16%20 | 14.0 | |
| Read with the local-software lines, since the gateway runs on the operator's hardware and BerriAI hosts nothing an agent calls. litellm on PyPI states Python 3.10 to 3.14, and the gateway ships as a Docker image, a Helm chart and Terraform modules, with GHCR images signed by cosign (20). 51 GitHub Actions workflows plus a CircleCI config cover unit, proxy-database, end-to-end, chaos, mutation and UI tests. The GitHub API was rate-limited for our reader on 6 November and Actions pages refused it on 6 October, so we couldn't confirm main is passing (15 of 25). The issue tracker showed 1,674 open issues on 6 November, with eight bug reports among the 15 newest, seven of them with a reply, against a project that tags several releases a day (10 of 25, down from an unchecked 12). Release notes carry breaking-change bullets, but breaking changes land in weekly minor releases on the 1.x line, so version numbers don't signal them (10 of 15). 1.108.1, past 1.0 (15). | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 6 November 2026 | 13%16.2 | 14.8 | |
Every gateway serves Swagger at /, ReDoc at /redoc and the raw schema at /openapi.json, and the docs host a public Swagger explorer (25). llms.txt, llms-full.txt and a Markdown twin of every page via .md (10). Pages say what a feature is for and where its limits are, and the key-auth page explains how permissions are inherited and where they aren't, but the reference is very large for a model to navigate (16 of 20). OpenAI-shaped request schemas from Pydantic models, with metadata, litellm_params and config blocks left as free-form objects (10 of 15). A full error reference with the envelope, every status, response headers and how to tell gateway limits from provider limits, plus examples on every page (15). Release notes per version with dates, newest v1.108.0 and v1.106.7 on 4 November 2026 (15). | |||
| Agent ergonomicschecked 6 November 2026 | 13%16.2 | 12.8 | |
Read with the API lines for the gateway an agent calls. Responses size through the usual max_tokens and streaming, and the MCP gateway can replace a large tool catalogue with four virtual tools (tool search) or filter tools by semantic relevance, which cuts context cost (20 of 25). Key, team and spend listings page and filter, though we didn't check every list call (15 of 20). Errors keep the OpenAI envelope with a string code, gateway 429s carry retry-after, rate_limit_type and reset_at, management routes answer RFC 9457 problem+json, and a table says which errors are safe to retry (20). Retries, cooldowns and fallbacks run inside the gateway and the docs say which errors to retry, but there are no idempotency keys for the management writes (12 of 20). Any OpenAI or Anthropic SDK works by changing the base URL, but the only first-party client is the Python SDK, and keys and spend need Postgres and a master key before the first call (12 of 15). | |||
| Security & authchecked 6 November 2026 | 14%17.5 | 12.6 | |
Read with the tool checklist for self-hosted software. Virtual keys are hashed, revocable and blockable, with model, route, MCP server, budget, rate and expiry limits, and a proxy_admin_viewer read-only role exists. Rotation with a grace period is Enterprise only, so 25, less 10 because the docs pass a key as ?key= on /key/info and on the Claude Code marketplace manifest (15 of 30). allowed_routes, MCP permissions by key and team, an approval queue for submitted MCP servers and stdio MCP servers off by default from 1.104.0 (15 of 20). Guardrails can run before a model call and on MCP tool results, and an OWASP LLM Top 10 page maps each risk to a control, but prompt-injection detectors such as Lakera need an Enterprise licence and all of it is off by default (12 of 15). Request and spend logs per key in the open-source build; audit logs of admin actions are Enterprise only (12 of 15). security.md with GitHub private reporting, a bug bounty from $500 to $3,000 for P0 and P1 reports, a security announcements list, SOC 2 Type II per the data security page, CodeQL, OSV and Scorecard workflows, and advisories published on GitHub. No security.txt, and reports without a video are closed unread (18 of 20). | |||
| Payments & pricingchecked 6 November 2026 | 10%12.5 | 7.5 | |
| Read with the self-hosted rule, since an agent uses the free gateway and Enterprise is a sales-led licence for the same software. No x402, MPP or L402 (0). MIT with no account and no card, so 20, 20 and 20 on the last three lines. Model calls cost what the operator's provider keys cost. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 6 November 2026 | 7%8.8 | 7.2 | |
| v1.108.1 tagged on 5 November 2026, v1.108.0 and v1.106.7 on 3 and 4 November (30). 125 tags between 8 August and 6 November, stable, patch, release-candidate and dev builds, with patch releases for four minor lines at once (20). Reply times not measured. On the issues page 7 of the 15 newest had a reply on the day, workflows auto-close duplicates and label issues, and Discord is the listed community channel (12 of 25). The package is the official SDK, current, with OpenAI and Anthropic SDKs working against the gateway (12 of 15). Dependency and image scanning (OSV, zizmor, Scorecard, grype) run in CI, with pass state unchecked (8 of 10). | |||
| Transparency & trusteditorial 77, provenance 49checked 6 November 2026 | 7%8.8 | 5.5 | |
| MIT for everything outside enterprise/, which has its own licence (25 of 30). The data security page (updated 6 November 2026) and security.md agree that a self-hosted gateway sends no data or telemetry to BerriAI, and the gateway stores prompts and spend in the operator's own Postgres. We found no terms of service or privacy policy on litellm.ai for its site, trial or Enterprise licence (20 of 30). A version support policy since 29 June 2026 (four stable minor lines), deprecated pages labelled in the docs, and release notes with breaking-change bullets (15 of 20). Usage telemetry, new in v1.107.0, is off by default, lists every field it can send and goes only to a table or endpoint the operator sets. A main-branch commit of 23 October 2026 made the Admin UI chat post a hashed user id to chat-telemetry.litellm.ai, and it was removed on 24 October before any tagged release contained it, so it isn't deducted. The start-up fetch of the price map from GitHub is documented with an opt-out (17 of 20). | |||
| Negative events | ≤15 |
| -12 |
| Total | 62.4 · B | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 62.4 B methodology v0.7
Fix list 23 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on LiteLLM. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: whether CI passes on main, since the GitHub API was rate-limited for our reader on 6 November and Actions and CircleCI refused it on 6 October
- unchecked: reply times on issues and pull requests and who answered them; only the first page of the issue list was read on 6 November
- No terms of service or privacy policy found on www.litellm.ai for the site, the trial or LiteLLM Cloud, which security.md still describes
- SOC 2 Type II is a vendor claim; the report sits behind trust.litellm.ai and wasn't read
- The kind is
routerto match openrouter, but it's self-hosted software, so reliability uses the local-software lines
Sources 23
- docs index docs.litellm.ai · seen 2026-11-06
- full docs text, error reference, rate limits, OpenAPI switches docs.litellm.ai · seen 2026-10-06
- data privacy and security, legal entity, telemetry docs.litellm.ai · seen 2026-11-06
- security.md, disclosure policy and bug bounty github.com · seen 2026-10-06
- supply-chain incident report docs.litellm.ai · seen 2026-10-06
- malware advisory api.osv.dev · seen 2026-10-06
- advisories for the litellm package api.osv.dev · seen 2026-11-06
- enterprise extras, support SLAs, version support policy docs.litellm.ai · seen 2026-10-06
- virtual keys, rotation, blocking docs.litellm.ai · seen 2026-10-06
- gateway quickstart docs.litellm.ai · seen 2026-10-06
- Claude Code client setup docs.litellm.ai · seen 2026-10-06
- release notes docs.litellm.ai · seen 2026-11-06
- pricing litellm.ai · seen 2026-11-06
- enterprise trial litellm.ai · seen 2026-11-06
- PyPI releases pypi.org · seen 2026-10-06
- PyPI downloads pypistats.org · seen 2026-11-06
- repository, LICENSE, workflows, source github.com · seen 2026-11-06
- RDAP for litellm.ai rdap.identitydigital.services · seen 2026-10-06
- usage telemetry docs.litellm.ai · seen 2026-11-06
- advisory GHSA-7hp6-4w63-5g45 api.osv.dev · seen 2026-11-06
- advisory GHSA-g5ff-637f-6q2m api.osv.dev · seen 2026-11-06
- issue tracker github.com · seen 2026-11-06
- pull request removing chat telemetry github.com · seen 2026-11-06
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Freemium Freemium Free to self-host under MIT, with no account or card. Model calls bill at each upstream provider's own prices on the operator's keys. Enterprise (SSO, audit logs, key rotation, team-scoped guardrails, support SLAs) is an annual licence priced through sales, with a 30-day trial key emailed after a form and no card (https://www.litellm.ai/pricing, https://www.litellm.ai/enterprise).
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/litellm.xml, or this listing's score history at history.json.
Connect
Install
pip install litellm # SDK; gateway: curl -sSLO https://github.com/BerriAI/litellm/raw/main/docker/docker-compose.quickstart.yml && docker compose -f docker-compose.quickstart.yml up -dFirst request
curl http://localhost:4000/v1/chat/completions \
-H 'Authorization: Bearer sk-<your-virtual-key>' \
-H 'Content-Type: application/json' \
-d '{
"model": "gpt-5.6-terra",
"messages": [{"role": "user", "content": "Say hello in five words."}]
}'Claude Code
export ANTHROPIC_BASE_URL="http://localhost:4000"
export ANTHROPIC_AUTH_TOKEN="sk-<your-virtual-key>"
export ANTHROPIC_MODEL="<a model_name from your config>"
claudeAlternatives to LiteLLM
#20 of 42 in Best model APIs and inference for AI agents · All 830 models comparisons
Cloudflare AI Gateway BVercel AI Gateway BTencent Cloud TokenHub COpenRouter BEden AI CAntseed C
Head to head Antseed vs LiteLLM · Cloudflare AI Gateway vs LiteLLM · Eden AI vs LiteLLM · Hugging Face Inference Providers vs LiteLLM · LiteLLM vs OpenRouter · LiteLLM vs Router.com (Ramp Router) · LiteLLM vs RouterPlus · LiteLLM vs Tencent Cloud TokenHub · LiteLLM vs Vercel AI Gateway
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| Cloudflare AI Gateway Cloudflare, Inc. | B | 67.8 | inference.router obs.gateway guard.pii | partial |
| Vercel AI Gateway Vercel Inc. | B | 67.8 | inference.router obs.gateway | no |
| LocalAI Ettore Di Giacinto and the LocalAI team | B | 62.5 | agent.mcp-client guard.pii | no |
| Tencent Cloud TokenHub Tencent Cloud | C | 59.5 | inference.router obs.gateway | no |
| AI SDK Vercel Inc. | AA | 89.8 | agent.mcp-client | no |
| OpenAI Agents SDK OpenAI | AA | 86.2 | agent.mcp-client | no |
Machine-readable
- JSON
/api/v1/tools/litellm.json· historyhistory.json· badge/badges/litellm.svg· changes feed/feeds/tools/litellm.xml - Markdown
/tools/litellm.md· slim/tools/litellm.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/litellm.md·/fixes/litellm.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool litellm --md(the CLI) · over MCPget_tool {"slug": "litellm"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT litellm.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/litellm"><img src="https://www.anchorterminal.com/badges/litellm.svg" alt="LiteLLM on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/litellm)<a href="https://www.anchorterminal.com/tools/litellm">LiteLLM on Anchor Terminal</a>It counts on a page on litellm.ai or one of its subdomains, or the README at the root of github.com/BerriAI/litellm.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "litellm", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say LiteLLM is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/litellm. The logo is the one on this listing. If it's wrong or out of date, send us the right one.