{ "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-08T22:39:45.901307965Z", "lastOk": true, "lastStatus": 403, "lastMs": 116, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 121, "p95ms24h": 145, "samples24h": 269, "samples30d": 1970, "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": 254, "ok": 254 } ] }, "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-08T22:39:45.901307965Z" } }, "answer": "DeepL API and Lokalise score within a point of each other on agent readiness, 72 (BB) and 71.3 (BB). Lokalise leads on reliability.", "b": { "slug": "lokalise", "name": "Lokalise", "vendor": "Lokalise, Inc.", "vendorUrl": "https://lokalise.com", "kind": "http-api", "category": "translation", "summary": "Lokalise is a hosted translation management system for software strings, documents and marketing content. Agents reach it through a REST API, the `lokalise2` CLI, SDKs in four languages and a hosted MCP server in beta.", "url": "https://www.anchorterminal.com/tools/lokalise", "markdownUrl": "https://www.anchorterminal.com/tools/lokalise.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lokalise.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lokalise.json", "repo": "https://github.com/lokalise/lokalise-cli-2-go", "license": "Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.lokalise.com/api2", "packages": [ { "registry": "npm", "name": "@lokalise/node-api" }, { "registry": "pypi", "name": "python-lokalise-api" }, { "registry": "go", "name": "github.com/lokalise/lokalise-cli-2-go" } ], "auth": "mixed", "authNotes": "Self-serve. A user creates a personal API token under Profile settings, read-only or read/write, and sends it in the `X-Api-Token` header. Tokens don't expire, can be deleted, and carry the creating user's project access. OAuth 2 for the API needs an app registered through Lokalise support, with scopes such as `read_keys` and `write_projects`. The MCP server takes OAuth with dynamic client registration, or an API token in the `apikey` header.", "pricing": "paid", "pricingNotes": "Explorer $149, Growth $379 and Advanced $1,049 a month billed yearly, Enterprise by quote. Monthly-billing prices load only in a browser and were not read. Every plan starts with a 14-day trial with no card, so an agent can start without a contract. There is no free plan except for open-source non-profit projects on request. The MCP article says API access depends on the plan, and the page did not show which plans include it (checked 2026-10-08).", "priceSummary": "$149 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI files or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 124, "npmWeekly": 337721, "pypiWeekly": 39399, "asOf": "2026-10-08" }, "docsUrl": "https://developers.lokalise.com", "llmsTxt": "https://developers.lokalise.com/llms.txt", "openapi": "https://developers.lokalise.com/openapi/lokalise-api-without-branches.yml", "capabilities": [ "translate.text", "translate.glossary", "translate.documents" ], "tags": [ "hosted", "official", "closed-source", "mcp", "oauth", "openapi", "llms-txt", "webhooks", "cli", "typescript", "python", "no-card", "status-page", "soc2" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 71.3, "grade": "BB", "agentReady": true, "rank": 115, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 84, "payments": 30, "reliability": 84, "schema": 76, "security": 73, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.", "bestFor": "Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.", "strengths": [ "Three public OpenAPI 3.0.3 files, llms.txt and a Markdown twin of every reference page", "Rate limits published as 6 requests a second per token and per IP, with 10 concurrent requests per project", "API tokens are read-only or read/write, and OAuth 2 carries read and write scopes per resource", "The MCP server signs in with OAuth, PKCE and dynamic client registration, and lists 22 scopes", "`GET /v1/audit-logs` returns team audit events in OCSF 1.3.0 format since 16 July 2026" ], "weaknesses": [ "The Master Service Agreement forbids using the service for benchmarking or competitive analysis", "No free plan. Explorer is $149 a month billed yearly after a 14-day trial without a card", "No idempotency keys in the OpenAPI files, though the errors page mentions an idempotent key under 409", "API tokens never expire and carry every permission of the user who made them", "The Developer Program Agreement lets Lokalise change or end API access with or without notice", "The MCP server is labelled beta in the help centre article" ], "agentNotes": [ "Send the token in the `X-Api-Token` header to `https://api.lokalise.com/api2`. OAuth access tokens go in `Authorization: Bearer` and expire after about 60 minutes.", "Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read `X-RateLimit-Reset`.", "Use a read-only token for reads. A read/write token can call `PUT /projects/{project_id}/empty`, which deletes every key and translation.", "Use `pagination=cursor` on `/keys` and `/translations`, with `limit` at most 500 on keys, and follow `X-Pagination-Next-Cursor`.", "Projects above 10,000 key-language pairs need `/files/async-download`. Poll `/processes/{process_id}` for the bundle URL, and do the same after `/files/upload`." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 84, "payments": 30, "reliability": 84, "schema": 76, "security": 73, "transparency": 63 }, "provenanceScore": 98 }, "connect": { "install": "brew tap lokalise/cli-2\nbrew install lokalise2", "http": "curl \"https://api.lokalise.com/api2/projects?limit=5\" -H \"X-Api-Token: $LOKALISE_API_TOKEN\"", "claudeCode": "claude mcp add lokalise_pm --transport http https://mcp.lokalise.com/mcp/project-management", "config": { "lokalise_pm": { "url": "https://mcp.lokalise.com/mcp/project-management" }, "lokalise_sd": { "url": "https://mcp.lokalise.com/mcp/software-development" } } }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/lokalise" }, "area": "everyday", "unitPrices": [ { "item": "Explorer", "unit": "month", "usd": 149, "note": "billed yearly" }, { "item": "Growth", "unit": "month", "usd": 379, "note": "billed yearly" }, { "item": "Advanced", "unit": "month", "usd": 1049, "note": "billed yearly" } ], "provenance": { "legalEntity": "Lokalise, Inc.", "domain": "lokalise.com", "domainRegistered": "2016-09-26", "endpointOnVendorDomain": true, "terms": "https://lokalise.com/msa-new/", "privacy": "https://lokalise.com/privacy-policy/", "statusPage": "https://status.lokalise.com", "changelog": "https://lokalise.com/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Master Service Agreement (last updated November 2025) names Lokalise, Inc., a Delaware company at 3500 South DuPont Highway, Suite BZ-101, Dover, DE 19901. It governs paid subscriptions.", "Trial and individual users fall under the User and Trial Access Terms of Service at https://lokalise.com/terms-of-service/ (November 2025). API integrations published in the app library fall under the Developer Program Agreement at https://lokalise.com/dev-hub-terms/, which shows no date.", "The privacy policy (last updated March 2026) covers the website, platform and services, and says Lokalise is the processor for customer data.", "The API answers at api.lokalise.com and the MCP server at mcp.lokalise.com.", "https://lokalise.com/.well-known/security.txt gives vdp.lokalise.com and security@lokalise.com as contacts and expires on 20 August 2027.", "RDAP for lokalise.com gives a registration date of 2016-09-26." ], "score": 98 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lokalise.json", "live": { "slug": "lokalise", "probe": { "target": "https://api.lokalise.com/api2", "method": "get", "lastAt": "2026-10-08T22:39:51.614959125Z", "lastOk": true, "lastStatus": 404, "lastMs": 89, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 91, "p95ms24h": 146, "samples24h": 36, "samples30d": 36, "days": [ { "date": "2026-10-08", "probes": 36, "ok": 36 } ] }, "vendorStatus": { "page": "https://status.lokalise.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T22:39:27.45262208Z" }, "updatedAt": "2026-10-08T22:39:51.614959125Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "DeepL", "b": "Lokalise, Inc.", "name": "Vendor" }, { "a": "https://api.deepl.com/v2/translate", "b": "https://api.lokalise.com/api2", "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": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT (MCP server)", "b": "Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause", "name": "Licence" }, { "a": "13", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-10-05", "name": "Last release" }, { "a": "2026-08-01", "b": "2025-11-01", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2026-03-01", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "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": "124 stars, 338k npm/wk, 39k PyPI/wk", "name": "Popularity" }, { "a": "3.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "DeepL API and Lokalise score within a point of each other on agent readiness, 72 (BB) and 71.3 (BB). Lokalise leads on reliability.", "question": "Which is better for AI agents, DeepL API or Lokalise?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do DeepL API and Lokalise need an API key?" }, { "answer": "Yes. DeepL API has a hosted endpoint at https://api.deepl.com/v2/translate and Lokalise at https://api.lokalise.com/api2.", "question": "Can an agent call DeepL API and Lokalise without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 95 against 76", "Agent ergonomics, 83 against 69", "Security \u0026 auth, 82 against 73" ], "also": [ "Runs on your own machine" ], "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, 84 against 52" ], "also": null, "goodFor": "Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.", "slug": "lokalise", "watchFor": "The Master Service Agreement forbids using the service for benchmarking or competitive analysis" } ], "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-lokalise.json", "title": "Amazon Translate vs Lokalise", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise" }, { "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-lokalise.json", "title": "Azure Translator vs Lokalise", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-lokalise" }, { "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-lokalise.json", "title": "Crowdin vs Lokalise", "url": "https://www.anchorterminal.com/compare/crowdin-vs-lokalise" }, { "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-lingo-dev.json", "title": "DeepL API vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev" }, { "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-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-lokalise.json", "title": "Google Cloud Translation vs Lokalise", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lara-translate-vs-lokalise.json", "title": "Lara Translate API vs Lokalise", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/libretranslate-vs-lokalise.json", "title": "LibreTranslate vs Lokalise", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-lokalise" }, { "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/lingvanex-vs-lokalise.json", "title": "Lingvanex Translation API vs Lokalise", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lokalise-vs-phrase.json", "title": "Lokalise vs Phrase", "url": "https://www.anchorterminal.com/compare/lokalise-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/lokalise-vs-systran.json", "title": "Lokalise vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lokalise-vs-systran" } ], "scores": [ { "by": 32, "deepl-api": 52, "edge": "lokalise", "key": "reliability", "lokalise": 84, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 19, "deepl-api": 95, "edge": "deepl-api", "key": "schema", "lokalise": 76, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 14, "deepl-api": 83, "edge": "deepl-api", "key": "ergonomics", "lokalise": 69, "name": "Agent ergonomics", "weight": 13 }, { "by": 9, "deepl-api": 82, "edge": "deepl-api", "key": "security", "lokalise": 73, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "deepl-api": 30, "edge": "", "key": "payments", "lokalise": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "deepl-api": 87, "edge": "deepl-api", "key": "maintenance", "lokalise": 84, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 1, "deepl-api": 80, "edge": "lokalise", "key": "transparency", "lokalise": 81, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "DeepL API and Lokalise score within a point of each other on agent readiness, 72 (BB) and 71.3 (BB). Lokalise 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.", "lokalise": "The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/deepl-api-vs-lokalise", "json": "https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.md", "slim": "https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.min.md" }, "markdown": "DeepL API and Lokalise score within a point of each other on agent readiness, 72 (BB) and 71.3 (BB). Lokalise 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- Lokalise: grade BB, 71.3/100, rank #115 of 722. Markdown https://www.anchorterminal.com/tools/lokalise.md · JSON https://www.anchorterminal.com/api/v1/tools/lokalise.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 76\n- Agent ergonomics, 83 against 69\n- Security \u0026 auth, 82 against 73\n\nAlso in its favour:\n- Runs on your own machine\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### Lokalise (BB)\n\nGood for: Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.\n\nAhead on:\n- Reliability, 84 against 52\n\nWatch for: The Master Service Agreement forbids using the service for benchmarking or competitive analysis\n\n\n## Score by category\n\n| Category | Weight | DeepL API | Lokalise | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 84 | Lokalise +32 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 95 | 76 | DeepL API +19 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 69 | DeepL API +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 82 | 73 | DeepL API +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 84 | DeepL API +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 80 | 81 | Lokalise +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72 · BB** | **71.3 · BB** | |\n\n## Facts side by side\n\n| Fact | DeepL API | Lokalise |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | DeepL | Lokalise, Inc. |\n| Hosted endpoint | `https://api.deepl.com/v2/translate` | `https://api.lokalise.com/api2` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | MIT (MCP server) | Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause |\n| Tools exposed | 13 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-09-30 | 2026-10-05 |\n| Terms last updated | 2026-08-01 | 2025-11-01 |\n| Privacy policy last updated | 2026-09-01 | 2026-03-01 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\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 | 124 stars, 338k npm/wk, 39k 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**Lokalise.** The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.\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### Lokalise\n\n1. Send the token in the `X-Api-Token` header to `https://api.lokalise.com/api2`. OAuth access tokens go in `Authorization: Bearer` and expire after about 60 minutes.\n2. Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read `X-RateLimit-Reset`.\n3. Use a read-only token for reads. A read/write token can call `PUT /projects/{project_id}/empty`, which deletes every key and translation.\n4. Use `pagination=cursor` on `/keys` and `/translations`, with `limit` at most 500 on keys, and follow `X-Pagination-Next-Cursor`.\n5. Projects above 10,000 key-language pairs need `/files/async-download`. Poll `/processes/{process_id}` for the bundle URL, and do the same after `/files/upload`.\n\n## Questions\n\n### Which is better for AI agents, DeepL API or Lokalise?\n\nDeepL API and Lokalise score within a point of each other on agent readiness, 72 (BB) and 71.3 (BB). Lokalise leads on reliability.\n\n### Do DeepL API and Lokalise need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call DeepL API and Lokalise without installing anything?\n\nYes. DeepL API has a hosted endpoint at https://api.deepl.com/v2/translate and Lokalise at https://api.lokalise.com/api2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.json, and with the fewest tokens: https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"deepl-api\", \"b\": \"lokalise\"}`. From a terminal: `anchor compare deepl-api lokalise`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/deepl-api.json and https://www.anchorterminal.com/api/v1/tools/lokalise.json\n\n## Other comparisons with DeepL API or Lokalise\n\n- [Amazon Translate vs DeepL API](https://www.anchorterminal.com/compare/amazon-translate-vs-deepl-api.md)\n- [Amazon Translate vs Lokalise](https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise.md)\n- [Azure Translator vs DeepL API](https://www.anchorterminal.com/compare/azure-translator-vs-deepl-api.md)\n- [Azure Translator vs Lokalise](https://www.anchorterminal.com/compare/azure-translator-vs-lokalise.md)\n- [Crowdin vs DeepL API](https://www.anchorterminal.com/compare/crowdin-vs-deepl-api.md)\n- [Crowdin vs Lokalise](https://www.anchorterminal.com/compare/crowdin-vs-lokalise.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 Lingo.dev](https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.md)\n- [DeepL API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.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 Lokalise](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.md)\n- [Lara Translate API vs Lokalise](https://www.anchorterminal.com/compare/lara-translate-vs-lokalise.md)\n- [LibreTranslate vs Lokalise](https://www.anchorterminal.com/compare/libretranslate-vs-lokalise.md)\n- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)\n- [Lingvanex Translation API vs Lokalise](https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.md)\n- [Lokalise vs Phrase](https://www.anchorterminal.com/compare/lokalise-vs-phrase.md)\n- [Lokalise vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lokalise-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 Lokalise", "url": "" } ], "description": "DeepL API and Lokalise score within a point of each other on agent readiness, 72 (BB) and 71.3 (BB). Lokalise leads on reliability. Both do translate text. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "DeepL API BB 72", "Lokalise BB 71.3", "scores" ], "h1": "DeepL API vs Lokalise", "image": "https://www.anchorterminal.com/assets/og/compare-deepl-api-vs-lokalise.png", "path": "/compare/deepl-api-vs-lokalise", "published": "2026-10-01", "section": "tools", "title": "DeepL API vs Lokalise for AI agents, BB 72 vs BB 71.3", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lokalise" }, "tokens": { "markdown": 2300, "slim": 680 }, "version": 1 }