{
  "data": {
    "a": {
      "slug": "deepl-api",
      "name": "DeepL API",
      "vendor": "DeepL",
      "vendorUrl": "https://www.deepl.com/en/products/api",
      "kind": "http-api",
      "category": "translation",
      "summary": "Translation API for text and documents in over 100 languages, with glossaries, formality control, style rules, custom instructions, a writing endpoint and a voice API.",
      "url": "https://www.anchorterminal.com/tools/deepl-api",
      "markdownUrl": "https://www.anchorterminal.com/tools/deepl-api.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/deepl-api.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/deepl-api.json",
      "repo": "https://github.com/DeepL/deepl-mcp-server",
      "license": "MIT (MCP server)",
      "transports": [
        "http",
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://api.deepl.com/v2/translate",
      "packages": [
        {
          "registry": "npm",
          "name": "deepl-node"
        },
        {
          "registry": "pypi",
          "name": "deepl"
        },
        {
          "registry": "npm",
          "name": "deepl-mcp-server"
        }
      ],
      "auth": "mixed",
      "authNotes": "`Authorization: DeepL-Auth-Key \u003ckey\u003e` header. API Free keys end in `:fx` and go to api-free.deepl.com, paid keys to api.deepl.com. The hosted MCP at mcp.deepl.com signs in with OAuth 2.1 against a DeepL account and takes no API key. The local MCP server reads `DEEPL_API_KEY`.",
      "pricing": "freemium",
      "pricingNotes": "DeepL has replaced its API plans. API Free (500,000 characters a month) and API Pro can no longer be bought. API Developer, where the free API key sign-up leads, allows 1,000,000 characters in total and never resets. API Growth is a monthly or yearly subscription with 1 million characters a month included (12 million a year), pay-as-you-go above that, and caps of 50 million characters and 300 speech-to-text hours a month. Enterprise is custom (https://support.deepl.com/hc/en-us/articles/360021200939-DeepL-API-plans, https://www.deepl.com/en/ai-agents). Every source character counts, spaces included, but HTML and XML tags don't when tag handling is on. Word, PowerPoint, Excel and PDF files bill at least 50,000 characters each (https://support.deepl.com/hc/en-us/articles/360020685720-Usage-count-and-billing-in-DeepL-API). We couldn't read the per-character rates, which the pricing page renders only in a browser.",
      "priceSummary": "Freemium",
      "where": "both",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": 13,
      "popularity": {
        "githubStars": 117,
        "npmWeekly": 328192,
        "pypiWeekly": 291467,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://developers.deepl.com",
      "llmsTxt": "https://developers.deepl.com/llms.txt",
      "openapi": "https://developers.deepl.com/api-reference/openapi.yaml",
      "capabilities": [
        "translate.text",
        "translate.documents",
        "translate.glossary",
        "translate.detect",
        "translate.formality",
        "speech.translation"
      ],
      "tags": [
        "hosted",
        "freemium",
        "free-tier",
        "no-card",
        "mcp",
        "llms-txt",
        "openapi",
        "typescript",
        "python",
        "eu",
        "enterprise",
        "closed-source"
      ],
      "lastRelease": "2026-09-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 72,
        "grade": "BB",
        "agentReady": true,
        "rank": 98,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 2,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 87,
          "payments": 30,
          "reliability": 52,
          "schema": 95,
          "security": 82,
          "transparency": 80
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "Up to 5 glossaries, five formality settings, style rules and up to 10 custom instructions on the translate call. API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset.",
        "bestFor": "Agents that need terminology control, formality and document layout kept, in European and Asian languages, and teams that want an MCP server today.",
        "strengths": [
          "Up to 5 glossaries, five formality settings, style rules and up to 10 custom instructions on the translate call",
          "OpenAPI document synced daily to GitHub, llms.txt and 17 dated changelog entries since 1 July 2026",
          "API Key Permissions scope a key to chosen endpoints, and keys travel only in a header",
          "Two official MCP servers, hosted with OAuth and local with an API key, the local one with CI and 15 releases since July",
          "Documented retry rules, retry 429, 529 and 5xx with backoff, don't retry 456"
        ],
        "weaknesses": [
          "API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset",
          "Per-character rates only appear on a browser-rendered pricing page",
          "No published request rate and no SLA found for self-serve plans",
          "The privacy policy doesn't say how API Developer text is handled",
          "Office and PDF files bill at least 50,000 characters each"
        ],
        "agentNotes": [
          "Match the host to the key. Keys ending `:fx` go to api-free.deepl.com, others to api.deepl.com",
          "Send the key in the `Authorization: DeepL-Auth-Key` header, since query and body keys now get 403",
          "Retry 429 and 529 with exponential backoff but stop on 456, which means the quota is spent",
          "Set `tag_handling` to html for markup so the tags survive and aren't billed",
          "Put a key-level usage limit on any key an agent holds, and scope it to the endpoints it needs"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 72
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 87,
          "payments": 30,
          "reliability": 52,
          "schema": 95,
          "security": 82,
          "transparency": 67
        },
        "provenanceScore": 93
      },
      "connect": {
        "install": "pip install deepl   # or: npm i deepl-node",
        "http": "curl -X POST https://api.deepl.com/v2/translate -H \"Authorization: DeepL-Auth-Key $DEEPL_API_KEY\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"text\":[\"Your table is booked for seven.\"],\"target_lang\":\"FR\",\"formality\":\"prefer_more\"}'",
        "claudeCode": "claude mcp add --transport http deepl https://mcp.deepl.com/v1/mcp",
        "config": {
          "mcpServers": {
            "deepl": {
              "args": [
                "-y",
                "deepl-mcp-server"
              ],
              "command": "npx",
              "env": {
                "DEEPL_API_KEY": "${DEEPL_API_KEY}"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/translate.text",
        "tool": "https://letme.dev/deepl-api"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "DeepL SE",
        "domain": "deepl.com",
        "domainRegistered": "2010-04-22",
        "endpointOnVendorDomain": true,
        "terms": "https://www.deepl.com/en/pro-license",
        "privacy": "https://www.deepl.com/en/privacy",
        "statusPage": "https://status.deepl.com",
        "changelog": "https://developers.deepl.com/docs/resources/roadmap-and-release-notes",
        "securityTxt": "valid",
        "checked": "2026-10-01",
        "notes": [
          "The privacy policy names DeepL SE and DeepL AI GmbH, Maarweg 165, 50825 Cologne, as controllers.",
          "security.txt is PGP-signed and expires on 2026-12-01, per the 30 September check.",
          "The changelog says status.deepl.com became one combined page with a dedicated API view on 2026-07-16. It renders only in a browser."
        ],
        "score": 93
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/deepl-api.json",
      "live": {
        "slug": "deepl-api",
        "probe": {
          "target": "https://api.deepl.com/v2/translate",
          "method": "get",
          "lastAt": "2026-10-08T21:12:08.65520986Z",
          "lastOk": true,
          "lastStatus": 403,
          "lastMs": 126,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 122,
          "p95ms24h": 154,
          "samples24h": 271,
          "samples30d": 1955,
          "days": [
            {
              "date": "2026-10-01",
              "probes": 109,
              "ok": 109
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 239,
              "ok": 239
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.deepl.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-08T19:38:25.689562478Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "DeepL/deepl-mcp-server",
            "version": "v1.3.13",
            "released": "2026-10-08",
            "seenAt": "2026-10-08T16:08:33.533547283Z"
          },
          {
            "registry": "npm",
            "name": "deepl-mcp-server",
            "version": "1.3.13",
            "seenAt": "2026-10-08T16:08:33.319349297Z"
          },
          {
            "registry": "npm",
            "name": "deepl-node",
            "version": "1.28.0",
            "seenAt": "2026-10-08T16:08:30.819547806Z"
          },
          {
            "registry": "pypi",
            "name": "deepl",
            "version": "1.32.0",
            "released": "2026-08-13",
            "seenAt": "2026-10-08T16:08:33.111257258Z"
          }
        ],
        "githubStars": 116,
        "npmWeekly": 333300,
        "pypiWeekly": 272428,
        "securityTxt": {
          "url": "https://deepl.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2026-12-01T09:00:00.000Z",
          "checkedAt": "2026-10-08T15:39:08.610875618Z"
        },
        "llmsTxt": {
          "url": "https://developers.deepl.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:00:19.238712612Z"
        },
        "domain": {
          "domain": "deepl.com",
          "registered": "2010-04-22",
          "source": "https://rdap.verisign.com/com/v1/domain/deepl.com",
          "checkedAt": "2026-10-04T13:05:06.317725836Z"
        },
        "pages": [
          {
            "url": "https://developers.deepl.com/docs/resources/roadmap-and-release-notes",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-08T18:17:31.120332607Z",
            "changedAt": "2026-10-07T18:04:14.194353904Z",
            "fingerprint": "b1979ef50112"
          },
          {
            "url": "https://www.deepl.com/en/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-08T18:27:21.429192924Z",
            "changedAt": "2026-10-06T16:14:39.26426417Z",
            "fingerprint": "fa594613dc10"
          },
          {
            "url": "https://www.deepl.com/en/pro-license",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-08T18:27:23.57360392Z",
            "changedAt": "2026-10-06T16:14:41.437106775Z",
            "fingerprint": "c0c13dd80195"
          }
        ],
        "updatedAt": "2026-10-08T21:12:08.65520986Z"
      }
    },
    "answer": "DeepL API scores 72 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on reliability.",
    "b": {
      "slug": "lingo-dev",
      "name": "Lingo.dev",
      "vendor": "Replexica, Inc.",
      "vendorUrl": "https://lingo.dev",
      "kind": "http-api",
      "category": "translation",
      "summary": "Lingo.dev is a hosted AI translation platform from Replexica, Inc. Customers configure engines with glossaries, brand voices, rules and a model per language pair, then call them through a REST API, a CLI or a hosted MCP server.",
      "url": "https://www.anchorterminal.com/tools/lingo-dev",
      "markdownUrl": "https://www.anchorterminal.com/tools/lingo-dev.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lingo-dev.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lingo-dev.json",
      "repo": "https://github.com/lingodotdev/lingo.dev",
      "license": "Proprietary hosted service under Lingo.dev's terms of service. The lingodotdev/lingo.dev repository (legacy CLI, JavaScript SDK, compiler) and the Python SDK are Apache-2.0. The `@lingo.dev/cli` package states no licence on npm",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.lingo.dev/account",
      "packages": [
        {
          "registry": "npm",
          "name": "@lingo.dev/cli"
        },
        {
          "registry": "npm",
          "name": "lingo.dev"
        },
        {
          "registry": "npm",
          "name": "@lingo.dev/_sdk"
        },
        {
          "registry": "pypi",
          "name": "lingodotdev"
        }
      ],
      "auth": "mixed",
      "authNotes": "The REST API takes an API key in the `X-API-Key` header. A person creates the key in the dashboard after a browser signup, with no review or sales step. Personal keys exist on every plan and carry their creator's access. Organisation keys with their own role and engine scope need the Enterprise plan. The MCP server signs in through a browser with OAuth (authorisation code, PKCE, dynamic client registration) and the user picks one organisation on the consent screen. No OAuth scopes are published.",
      "pricing": "usage",
      "pricingNotes": "Usage is billed from prepaid credits with auto-reload. Lingo.dev charges $2 per million output tokens on top of the LLM provider's price, which is passed through with no markup, plus $0.50 per engine a month and $0.01 per AI review run. Sandbox has a $0 base and 100,000 tokens a day, so an agent's owner can start without a contract. Production is $99 a month with 5 million tokens a day, and Enterprise is custom. No free usage allowance was found, and whether signup needs a card could not be read without an account (https://lingo.dev/en/pricing, checked 2026-10-08).",
      "priceSummary": "$99 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the API docs or the pricing page. The API's 402 status means the organisation's credit limit was reached and carries no payment instructions (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 5402,
        "npmWeekly": 91991,
        "pypiWeekly": 1975,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://lingo.dev/en/docs/api",
      "registryName": "dev.lingo/main",
      "capabilities": [
        "translate.text",
        "translate.glossary",
        "translate.detect",
        "translate.formality"
      ],
      "tags": [
        "hosted",
        "usage-priced",
        "prepaid",
        "mcp",
        "oauth",
        "api-key",
        "cli",
        "webhooks",
        "async-jobs",
        "typescript",
        "python",
        "closed-source",
        "status-page",
        "soc2",
        "enterprise"
      ],
      "lastRelease": "2026-10-07",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.3,
        "grade": "B",
        "agentReady": false,
        "rank": 341,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 8,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 87,
          "payments": 20,
          "reliability": 71,
          "schema": 54,
          "security": 62,
          "transparency": 71
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "Lingo.dev suits teams that want glossary and tone control on every translation call, with a published fee of $2 per million output tokens and model costs passed through. It has no public OpenAPI file, its `llms.txt` is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan.",
        "bestFor": "Product teams that translate interface strings and content into many locales and want glossary, tone and rule control held in one place, driven from code, CI or a coding assistant.",
        "strengths": [
          "Glossary terms, per-locale brand voice and rules apply on every call, sync or async, through one configured engine",
          "Each sync response reports the model used, token counts and cost in USD",
          "Async jobs take up to 100 target locales, an `idempotencyKey`, signed webhooks and cursor paging with `limit` up to 100",
          "The hosted MCP server signs in with OAuth, PKCE and dynamic client registration, with no key to paste",
          "Public prices, a weekly changelog since March 2026 and an OpenStatus page with incident history"
        ],
        "weaknesses": [
          "No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version",
          "Organisation keys with their own role and engine scope, RBAC and audit logs are Enterprise only. On other plans every member is an Owner",
          "The status page lists two partial API outages in 90 days, on 18 July 2026 (closed after 19 hours) and 22 September 2026 (1 hour 50 minutes)",
          "Errors carry a status code and a free-text `message`, with no machine-readable code and no `Retry-After` documented",
          "The privacy policy points to lingo.dev/security for sub-processors, and that page returned 404 on 8 October 2026"
        ],
        "agentNotes": [
          "Send `X-API-Key` to https://api.lingo.dev and keep the key server-side. On non-Enterprise plans a personal key reaches every engine its creator can",
          "Use `POST /process/localize` for one language pair and `POST /jobs/localization` with an `idempotencyKey` for several. Pipeline stages run on async jobs only",
          "Treat 402 (credit limit) and 429 (daily token quota) as limits to report, not to retry. Retry 500 with backoff",
          "Read `usage.cost` on each sync response to track spend. Sandbox stops at 100,000 tokens a day",
          "Connect MCP clients to https://mcp.lingo.dev/account. Its tools can create and revoke API keys and invite members, so ask before those calls"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.3
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 87,
          "payments": 20,
          "reliability": 71,
          "schema": 54,
          "security": 62,
          "transparency": 51
        },
        "provenanceScore": 91
      },
      "connect": {
        "install": "npm install -g @lingo.dev/cli",
        "http": "curl -X POST https://api.lingo.dev/process/localize \\\n  -H \"X-API-Key: your_api_key\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"engineId\": \"eng_abc123\", \"sourceLocale\": \"en\", \"targetLocale\": \"de\", \"data\": {\"greeting\": \"Hello\"}}'",
        "claudeCode": "claude mcp add lingo --transport http https://mcp.lingo.dev/account --scope user",
        "config": {
          "lingo": {
            "type": "http",
            "url": "https://mcp.lingo.dev/account"
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/translate.text",
        "tool": "https://letme.dev/lingo-dev"
      },
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Lingo.dev infrastructure fee",
          "unit": "1m-tokens",
          "usd": 2,
          "note": "Computed from output tokens. The LLM provider's price is added with no markup"
        },
        {
          "item": "Production plan base",
          "unit": "month",
          "usd": 99,
          "note": "5 million tokens a day. Sandbox base is $0 with 100,000 a day"
        },
        {
          "item": "Each engine",
          "unit": "month",
          "usd": 0.5,
          "note": "Per engine on Sandbox and Production"
        },
        {
          "item": "AI review run",
          "unit": "call",
          "usd": 0.01,
          "note": "Per run"
        }
      ],
      "provenance": {
        "legalEntity": "Replexica, Inc.",
        "domain": "lingo.dev",
        "domainRegistered": "2021-05-03",
        "endpointOnVendorDomain": true,
        "terms": "https://lingo.dev/en/legal/terms",
        "privacy": "https://lingo.dev/en/legal/privacy",
        "statusPage": "https://status.lingo.dev",
        "changelog": "https://lingo.dev/en/changelog",
        "securityTxt": "valid",
        "checked": "2026-10-08",
        "notes": [
          "The terms of service (last updated 7 May 2026) cover the website, the platform, the APIs, the CLI and the MCP server, name Replexica Inc. and Lingo.dev (Replexica, Inc), and are governed by Delaware law.",
          "The privacy policy (last updated 7 May 2026) covers the website and the platform, including content submitted for translation.",
          "The API answers at api.lingo.dev and the MCP server at mcp.lingo.dev, both on the vendor's domain.",
          "lingo.dev/.well-known/security.txt gives security@lingo.dev, a canonical URL and a disclosure policy with a safe-harbour promise. It has no Expires field.",
          "RDAP for lingo.dev gives a registration date of 2021-05-03. The site footer says the company is headquartered in San Francisco. No street address was found in the terms or the privacy policy.",
          "The privacy policy says the sub-processor list is kept in the Data Processing Agreement and at lingo.dev/security. That URL returned 404 on 8 October 2026 and no published DPA was found."
        ],
        "score": 91
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/lingo-dev.json",
      "live": {
        "slug": "lingo-dev",
        "probe": {
          "target": "https://mcp.lingo.dev/account",
          "method": "get",
          "lastAt": "2026-10-08T21:12:14.053179587Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 707,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 958,
          "p95ms24h": 1336,
          "samples24h": 21,
          "samples30d": 21,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 21,
              "ok": 21
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.lingo.dev",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-08T19:38:45.164350131Z"
        },
        "updatedAt": "2026-10-08T21:12:14.053179587Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "DeepL",
        "b": "Replexica, Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://api.deepl.com/v2/translate",
        "b": "https://mcp.lingo.dev/account",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP, stdio",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "MIT (MCP server)",
        "b": "Proprietary hosted service under Lingo.dev's terms of service. The lingodotdev/lingo.dev repository (legacy CLI, JavaScript SDK, compiler) and the Python SDK are Apache-2.0. The `@lingo.dev/cli` package states no licence on npm",
        "name": "Licence"
      },
      {
        "a": "13",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "dev.lingo/main",
        "name": "MCP registry"
      },
      {
        "a": "2026-09-30",
        "b": "2026-10-07",
        "name": "Last release"
      },
      {
        "a": "2026-08-01",
        "b": "2026-05-07",
        "name": "Terms last updated"
      },
      {
        "a": "2026-09-01",
        "b": "2026-05-07",
        "name": "Privacy policy last updated"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "117 stars, 328k npm/wk, 291k PyPI/wk",
        "b": "5.4k stars, 92k npm/wk, 2k PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "3.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "DeepL API scores 72 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on reliability.",
        "question": "Which is better for AI agents, DeepL API or Lingo.dev?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do DeepL API and Lingo.dev need an API key?"
      },
      {
        "answer": "Yes. DeepL API has a hosted endpoint at https://api.deepl.com/v2/translate and Lingo.dev at https://mcp.lingo.dev/account.",
        "question": "Can an agent call DeepL API and Lingo.dev without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 95 against 54",
          "Agent ergonomics, 83 against 75",
          "Security \u0026 auth, 82 against 62",
          "Payments \u0026 pricing, 30 against 20",
          "Transparency \u0026 trust, 80 against 71"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "Agents that need terminology control, formality and document layout kept, in European and Asian languages, and teams that want an MCP server today.",
        "slug": "deepl-api",
        "watchFor": "API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset"
      },
      {
        "aheadOn": [
          "Reliability, 71 against 52"
        ],
        "also": null,
        "goodFor": "Product teams that translate interface strings and content into many locales and want glossary, tone and rule control held in one place, driven from code, CI or a coding assistant.",
        "slug": "lingo-dev",
        "watchFor": "No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version"
      }
    ],
    "job": {
      "capability": "translate.text",
      "name": "Translate text"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/amazon-translate-vs-deepl-api.json",
        "title": "Amazon Translate vs DeepL API",
        "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-deepl-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.json",
        "title": "Amazon Translate vs Lingo.dev",
        "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/azure-translator-vs-deepl-api.json",
        "title": "Azure Translator vs DeepL API",
        "url": "https://www.anchorterminal.com/compare/azure-translator-vs-deepl-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.json",
        "title": "Azure Translator vs Lingo.dev",
        "url": "https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crowdin-vs-deepl-api.json",
        "title": "Crowdin vs DeepL API",
        "url": "https://www.anchorterminal.com/compare/crowdin-vs-deepl-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.json",
        "title": "Crowdin vs Lingo.dev",
        "url": "https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepl-api-vs-google-cloud-translation.json",
        "title": "DeepL API vs Google Cloud Translation",
        "url": "https://www.anchorterminal.com/compare/deepl-api-vs-google-cloud-translation"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepl-api-vs-lara-translate.json",
        "title": "DeepL API vs Lara Translate API",
        "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lara-translate"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepl-api-vs-libretranslate.json",
        "title": "DeepL API vs LibreTranslate",
        "url": "https://www.anchorterminal.com/compare/deepl-api-vs-libretranslate"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.json",
        "title": "DeepL API vs Lingvanex Translation API",
        "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.json",
        "title": "DeepL API vs Lokalise",
        "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lokalise"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepl-api-vs-phrase.json",
        "title": "DeepL API vs Phrase",
        "url": "https://www.anchorterminal.com/compare/deepl-api-vs-phrase"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepl-api-vs-systran.json",
        "title": "DeepL API vs SYSTRAN Translate API",
        "url": "https://www.anchorterminal.com/compare/deepl-api-vs-systran"
      },
      {
        "json": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.json",
        "title": "Google Cloud Translation vs Lingo.dev",
        "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.json",
        "title": "Lara Translate API vs Lingo.dev",
        "url": "https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.json",
        "title": "LibreTranslate vs Lingo.dev",
        "url": "https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.json",
        "title": "Lingo.dev vs Lingvanex Translation API",
        "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.json",
        "title": "Lingo.dev vs Lokalise",
        "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.json",
        "title": "Lingo.dev vs Phrase",
        "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-systran.json",
        "title": "Lingo.dev vs SYSTRAN Translate API",
        "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-systran"
      }
    ],
    "scores": [
      {
        "by": 19,
        "deepl-api": 52,
        "edge": "lingo-dev",
        "key": "reliability",
        "lingo-dev": 71,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 41,
        "deepl-api": 95,
        "edge": "deepl-api",
        "key": "schema",
        "lingo-dev": 54,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 8,
        "deepl-api": 83,
        "edge": "deepl-api",
        "key": "ergonomics",
        "lingo-dev": 75,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 20,
        "deepl-api": 82,
        "edge": "deepl-api",
        "key": "security",
        "lingo-dev": 62,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 10,
        "deepl-api": 30,
        "edge": "deepl-api",
        "key": "payments",
        "lingo-dev": 20,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 0,
        "deepl-api": 87,
        "edge": "",
        "key": "maintenance",
        "lingo-dev": 87,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 9,
        "deepl-api": 80,
        "edge": "deepl-api",
        "key": "transparency",
        "lingo-dev": 71,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "DeepL API scores 72 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on reliability. Both do translate text.",
    "verdicts": {
      "deepl-api": "Up to 5 glossaries, five formality settings, style rules and up to 10 custom instructions on the translate call. API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset.",
      "lingo-dev": "Lingo.dev suits teams that want glossary and tone control on every translation call, with a published fee of $2 per million output tokens and model costs passed through. It has no public OpenAPI file, its `llms.txt` is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev",
    "json": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.md",
    "slim": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.min.md"
  },
  "markdown": "DeepL API scores 72 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on reliability. Both do translate text.\n\n- DeepL API: grade BB, 72/100, rank #98 of 722. Markdown https://www.anchorterminal.com/tools/deepl-api.md · JSON https://www.anchorterminal.com/api/v1/tools/deepl-api.json\n- Lingo.dev: grade B, 62.3/100, rank #341 of 722. Markdown https://www.anchorterminal.com/tools/lingo-dev.md · JSON https://www.anchorterminal.com/api/v1/tools/lingo-dev.json\n\n## Which one, for what\n\n### DeepL API (BB)\n\nGood for: Agents that need terminology control, formality and document layout kept, in European and Asian languages, and teams that want an MCP server today.\n\nAhead on:\n- Schema \u0026 documentation, 95 against 54\n- Agent ergonomics, 83 against 75\n- Security \u0026 auth, 82 against 62\n- Payments \u0026 pricing, 30 against 20\n- Transparency \u0026 trust, 80 against 71\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset\n\n### Lingo.dev (B)\n\nGood for: Product teams that translate interface strings and content into many locales and want glossary, tone and rule control held in one place, driven from code, CI or a coding assistant.\n\nAhead on:\n- Reliability, 71 against 52\n\nWatch for: No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version\n\n\n## Score by category\n\n| Category | Weight | DeepL API | Lingo.dev | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 71 | Lingo.dev +19 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 95 | 54 | DeepL API +41 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 75 | DeepL API +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 82 | 62 | DeepL API +20 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | DeepL API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 87 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 80 | 71 | DeepL API +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72 · BB** | **62.3 · B** | |\n\n## Facts side by side\n\n| Fact | DeepL API | Lingo.dev |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | DeepL | Replexica, Inc. |\n| Hosted endpoint | `https://api.deepl.com/v2/translate` | `https://mcp.lingo.dev/account` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | MIT (MCP server) | Proprietary hosted service under Lingo.dev's terms of service. The lingodotdev/lingo.dev repository (legacy CLI, JavaScript SDK, compiler) and the Python SDK are Apache-2.0. The `@lingo.dev/cli` package states no licence on npm |\n| Tools exposed | 13 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | not listed | `dev.lingo/main` |\n| Last release | 2026-09-30 | 2026-10-07 |\n| Terms last updated | 2026-08-01 | 2026-05-07 |\n| Privacy policy last updated | 2026-09-01 | 2026-05-07 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 117 stars, 328k npm/wk, 291k PyPI/wk | 5.4k stars, 92k npm/wk, 2k PyPI/wk |\n| Agent reviews | 3.5/5 (2) | none |\n\n## Verdicts\n\n**DeepL API.** Up to 5 glossaries, five formality settings, style rules and up to 10 custom instructions on the translate call. API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset.\n\n**Lingo.dev.** Lingo.dev suits teams that want glossary and tone control on every translation call, with a published fee of $2 per million output tokens and model costs passed through. It has no public OpenAPI file, its `llms.txt` is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan.\n\n## Before you call either\n\n### DeepL API\n\n1. Match the host to the key. Keys ending `:fx` go to api-free.deepl.com, others to api.deepl.com\n2. Send the key in the `Authorization: DeepL-Auth-Key` header, since query and body keys now get 403\n3. Retry 429 and 529 with exponential backoff but stop on 456, which means the quota is spent\n4. Set `tag_handling` to html for markup so the tags survive and aren't billed\n5. Put a key-level usage limit on any key an agent holds, and scope it to the endpoints it needs\n\n### Lingo.dev\n\n1. Send `X-API-Key` to https://api.lingo.dev and keep the key server-side. On non-Enterprise plans a personal key reaches every engine its creator can\n2. Use `POST /process/localize` for one language pair and `POST /jobs/localization` with an `idempotencyKey` for several. Pipeline stages run on async jobs only\n3. Treat 402 (credit limit) and 429 (daily token quota) as limits to report, not to retry. Retry 500 with backoff\n4. Read `usage.cost` on each sync response to track spend. Sandbox stops at 100,000 tokens a day\n5. Connect MCP clients to https://mcp.lingo.dev/account. Its tools can create and revoke API keys and invite members, so ask before those calls\n\n## Questions\n\n### Which is better for AI agents, DeepL API or Lingo.dev?\n\nDeepL API scores 72 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on reliability.\n\n### Do DeepL API and Lingo.dev need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call DeepL API and Lingo.dev without installing anything?\n\nYes. DeepL API has a hosted endpoint at https://api.deepl.com/v2/translate and Lingo.dev at https://mcp.lingo.dev/account.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.json, and with the fewest tokens: https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"deepl-api\", \"b\": \"lingo-dev\"}`. From a terminal: `anchor compare deepl-api lingo-dev`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/deepl-api.json and https://www.anchorterminal.com/api/v1/tools/lingo-dev.json\n\n## Other comparisons with DeepL API or Lingo.dev\n\n- [Amazon Translate vs DeepL API](https://www.anchorterminal.com/compare/amazon-translate-vs-deepl-api.md)\n- [Amazon Translate vs Lingo.dev](https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.md)\n- [Azure Translator vs DeepL API](https://www.anchorterminal.com/compare/azure-translator-vs-deepl-api.md)\n- [Azure Translator vs Lingo.dev](https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.md)\n- [Crowdin vs DeepL API](https://www.anchorterminal.com/compare/crowdin-vs-deepl-api.md)\n- [Crowdin vs Lingo.dev](https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.md)\n- [DeepL API vs Google Cloud Translation](https://www.anchorterminal.com/compare/deepl-api-vs-google-cloud-translation.md)\n- [DeepL API vs Lara Translate API](https://www.anchorterminal.com/compare/deepl-api-vs-lara-translate.md)\n- [DeepL API vs LibreTranslate](https://www.anchorterminal.com/compare/deepl-api-vs-libretranslate.md)\n- [DeepL API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.md)\n- [DeepL API vs Lokalise](https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.md)\n- [DeepL API vs Phrase](https://www.anchorterminal.com/compare/deepl-api-vs-phrase.md)\n- [DeepL API vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/deepl-api-vs-systran.md)\n- [Google Cloud Translation vs Lingo.dev](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.md)\n- [Lara Translate API vs Lingo.dev](https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.md)\n- [LibreTranslate vs Lingo.dev](https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.md)\n- [Lingo.dev vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.md)\n- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)\n- [Lingo.dev vs Phrase](https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.md)\n- [Lingo.dev vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingo-dev-vs-systran.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-08",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "DeepL API vs Lingo.dev",
        "url": ""
      }
    ],
    "description": "DeepL API scores 72 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on reliability. Both do translate text. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "DeepL API BB 72",
      "Lingo.dev B 62.3",
      "scores"
    ],
    "h1": "DeepL API vs Lingo.dev",
    "image": "https://www.anchorterminal.com/assets/og/compare-deepl-api-vs-lingo-dev.png",
    "path": "/compare/deepl-api-vs-lingo-dev",
    "published": "2026-10-01",
    "section": "tools",
    "title": "DeepL API vs Lingo.dev for AI agents, BB 72 vs B 62.3",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev"
  },
  "tokens": {
    "markdown": 2350,
    "slim": 780
  },
  "version": 1
}
