Model reference · open weights

LFM2-Tool

Available as managed deployment Licence fee LLMs LiquidAI Text gen 1 variants 1k dl/mo

LFM2-Tool is an open-weight language model from LiquidAI. AxForge deploys and operates it for you on dedicated EU-owned hardware — with the licence handled where one is required.

Available as managed deployment — configured and operated for you on dedicated EU hardware, quoted per deployment.

What it is

Released byLiquidAI
TypeLanguage models
TaskText gen
Parameters (lead)1.2B
Context125k tokens
Runs withtransformers
Based onLiquidAI/LFM2-1.2B
Released2025-09-03
Popularity1k downloads / month
LicenceCommercial licence needed

About

What LFM2-Tool is

src="https://cdn-uploads.huggingface.co/production/uploads/61b8e2ba285851687028d395/2b08LKpev0DNEk6DlnWkY.png" alt="Liquid AI" style="width: 100%; max-width: 100%; height: auto; display: inline-block; margin-bottom: 0.5em; margin-top: 0.5em;" />

Read the full model card

LFM2-1.2B-Tool

Based on LFM2-1.2B, LFM2-1.2B-Tool is designed for concise and precise tool calling. The key challenge was designing a non-thinking model that outperforms similarly sized thinking models for tool use.

Use cases:

  • Mobile and edge devices requiring instant API calls, database queries, or system integrations without cloud dependency.
  • Real-time assistants in cars, IoT devices, or customer support, where response latency is critical.
  • Resource-constrained environments like embedded systems or battery-powered devices needing efficient tool execution.

You can find more information about other task-specific models in this blog post.

📄 Model details

Generation parameters: We recommend using greedy decoding with a temperature=0.

System prompt: The system prompt must provide all the available tools

Supported languages: English, Arabic, Chinese, French, German, Japanese, Korean, Portuguese, and Spanish.

Tool use: It consists of four main steps:

  1. Function definition: LFM2 takes JSON function definitions as input (JSON objects between and special tokens), usually in the system prompt
  2. Function call: LFM2 writes Pythonic function calls (a Python list between and special tokens), as the assistant answer.
  3. Function execution: The function call is executed and the result is returned (string between and special tokens), as a "tool" role.
  4. Final answer: LFM2 interprets the outcome of the function call to address the original user prompt in plain text.

Here is a simple example of a conversation using tool use:

List of tools: [{"name": "get_candidate_status", "description": "Retrieves the current status of a candidate in the recruitment process", "parameters": {"type": "object", "properties": {"candidate_id": {"type": "string", "description": "Unique identifier for the candidate"}}, "required": ["candidate_id"]}}]
What is the current status of candidate ID 12345?
The candidate with ID 12345 is currently in the "Interview Scheduled" stage for the position of Clinical Research Associate, with an interview date set for 2023-11-20.

[!WARNING] ⚠️ The model supports both single-turn and multi-turn conversations.

📈 Performance

For edge inference, latency is a crucial factor in delivering a seamless and satisfactory user experience. Consequently, while test-time-compute inherently provides more accuracy, it ultimately compromises the user experience due to increased waiting times for function calls.

Therefore, the goal was to develop a tool calling model that is competitive with thinking models, yet operates without any internal chain-of-thought process.

We evaluated each model on a proprietary benchmark that was specifically designed to prevent data contamination. The benchmark ensures that performance metrics reflect genuine tool-calling capabilities rather than memorized patterns from training data.

🏃 How to run

You can use the following Colab notebooks for easy inference and fine-tuning:

NotebookDescriptionLink
InferenceRun the model with Hugging Face's transformers library.
SFT (TRL)Supervised Fine-Tuning (SFT) notebook with a LoRA adapter using TRL.
DPO (TRL)Preference alignment with Direct Preference Optimization (DPO) using TRL.
SFT (Axolotl)Supervised Fine-Tuning (SFT) notebook with a LoRA adapter using Axolotl.
SFT (Unsloth)Supervised Fine-Tuning (SFT) notebook with a LoRA adapter using Unsloth.

📬 Contact

  • If you are interested in custom solutions with edge deployment, please contact our sales team.

Citation

@article{liquidai2025lfm2,
 title={LFM2 Technical Report},
 author={Liquid AI},
 journal={arXiv preprint arXiv:2511.23404},
 year={2025}
}

From the published model card. Full card on the HuggingFace links in the sidebar.

Using it via the API

Call it like any OpenAI endpoint

Once AxForge deploys lfm2-tool for you, it answers on the OpenAI-compatible API — the same base URL and keys as every other model. (lfm2-tool below is illustrative; you get the exact model name on deployment.)

$ curl -sS https://api.axforge.ai/v1/chat/completions \
  -H "Authorization: Bearer $AXFORGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"lfm2-tool","messages":[{"role":"user","content":"Hello"}]}'

Create an account — your API key is available in the console. 3M free tokens every 30 days with every new account.

© 2026 AxForge · EU-hosted AI infrastructure Pricing Docs Trust Privacy Terms