---
title: ToolRouter — Use Case
description: Step-by-step guide for a real-world ToolRouter use case with agent-specific instructions.
url: https://toolrouter.com/tools/translate/use-cases/translate-api-docs
---
# Translate API Documentation

Developer documentation is increasingly consumed by global audiences, yet most API docs are English-only. Developers in non-English speaking markets -- particularly in Asia, Latin America, and Eastern Europe -- consistently cite language barriers as a top frustration when evaluating tools.

ToolRouter's translate_text skill handles the unique challenges of technical documentation: preserving code blocks, API endpoint paths, parameter names, and JSON examples while translating prose explanations, error messages, and tutorial content. It understands the boundary between what should and should not be translated.

This is critical for developer tools expanding internationally, open-source projects seeking global contributors, and API platforms competing for adoption in non-English markets. Translated documentation lowers the barrier to entry and accelerates time-to-first-API-call for international developers.

**Tool:** [Translate](https://toolrouter.com/tools/translate)
**Skills:** translate_text

## Agent Guides

- [How to Translate API Docs with Claude](https://toolrouter.com/tools/translate/use-cases/translate-api-docs/claude): Guide for Claude
- [How to Translate API Docs with ChatGPT](https://toolrouter.com/tools/translate/use-cases/translate-api-docs/chatgpt): Guide for ChatGPT
- [How to Translate API Docs with Copilot](https://toolrouter.com/tools/translate/use-cases/translate-api-docs/copilot): Guide for Copilot
- [How to Translate API Docs with OpenClaw](https://toolrouter.com/tools/translate/use-cases/translate-api-docs/openclaw): Guide for OpenClaw
