Gorilla

Gorilla's value is not that it is a chatbot — it is that it is one of the few openly licensed models built end-to-end for producing API calls, plus a benchmark suite to prove whether any model is actually good at it. OpenFunctions-v2 was trained natively for parallel functions (several calls at once) and multiple functions (choosing one or more from a supplied set), and it extended coverage to Java and REST alongside Python, with function-relevance detection so the model can decline when none of the provided functions fit the question. The Berkeley Function Calling Leaderboard turns that into an apples-to-apples number across roughly 2,000 question-function-answer pairs and multiple languages. Where Gorilla gets interesting for production work is the surrounding tooling. GoEX approaches agent safety differently from the usual guardrail stack: instead of trying to validate every intermediate step before execution, it assumes post-facto validation and gives you undo plus damage confinement, so you can revert an action or bound its blast radius after you see the result. RAFT is the third leg — a fine-tuning recipe that trains a base model against a specific document set rather than generic instruction data, intended for domain RAG where you know the corpus. Strengths: Apache 2.0 across the model, the execution engine and the reproducibility code; no per-call fee; you can fine-tune and self-host; the leaderboard and datasets are public, so you can verify claims yourself. Multiple low-friction doors in — pip install gorilla-cli, a Spotlight Search integration, a web demo and a Colab notebook with no sign-up. Weaknesses are structural, not fixable by configuration. You own deployment, latency and maintenance. The model is specialized for function calling, so it is not the right pick for open-domain conversation or general writing. GoEX's docs themselves lay out the hard parts of post-facto validation — hallucination, stochasticity, and downstream effects you cannot see while they happen — meaning undo and damage confinement are mitigations, not a solved problem. Undo also has limits: the GoEX write-up notes it depends on the level of system access and can require keeping multiple versions of state, which costs memory and compute. Where it fits: platform and infrastructure engineers building tool-calling agents, researchers who need a reproducible benchmark, and teams building domain RAG who can invest in fine-tuning. Where it does not: product teams that need a vendor on the hook for uptime, and anyone who needs a general-purpose assistant out of the box.