Documentation menu

Choose an integration

How to pick between the REST API, the MCP server, LangChain tools, the n8n node, Make and Zapier, and function calling, and what they all have in common.

View as Markdown

All of FluentC's integrations call the same engine. They differ in who decides when to translate: your code, an AI agent, or a workflow.

Which one to use

You are...UseWhy
Writing application code in any languageREST APIFull control; works anywhere that can send HTTP
Giving an AI agent or MCP client a translation toolMCP serverThe agent discovers and calls the tool itself; no glue code
Building agents or chains with LangChain in PythonLangChain toolsReady-made BaseTool classes, including batch polling
Building workflows in n8nn8n nodeVisual nodes, language dropdowns, automatic batch polling
Using Make or ZapierMake and ZapierHTTP steps; no code
Using a model with tool calling (OpenAI or others)Function callingOne tool definition and a small handler

If your tool isn't listed, use the REST API. Anything that can send an HTTP request can call FluentC.

What they share

  • One API key. Create it in the dashboard and use it everywhere. See Authentication.
  • One plan. A Batch plan key can use batch mode in any integration. Real-time mode needs the Real-time plan. See Concepts.
  • One translation memory. A string translated through n8n is answered from memory when an agent asks for it later. See Concepts.
  • The same rules. Language codes, input formats and limits are identical, so everything in the REST reference applies.

Real-time or batch in an integration

If the translation is...Use
Part of a conversation or a tool call someone is waiting onreal-time
A large document, catalog, or a list of stringsbatch
Triggered in bulk by a schedulebatch

Integrations that poll batch jobs for you (the n8n node, the LangChain batch tool) cap the number of attempts, so a job that never finishes ends with a clear error instead of hanging.

Something unclear, or missing? Tell us.