Cohere: North Mini Code (free)
North Mini Code is Cohere's first agentic coding model and the debut of its North family. A sparse mixture-of-experts model with 30B total parameters and 3B active, it is optimized...
Anyone in the Project can @-mention Cohere: North Mini Code (free) with the team's shared context - pooled credits, one chat, one memory.
Starter is free forever - 1 Project, 100 credits/month, 1 MCP. No card.
Verdict
Best for
- Zero-cost code prototyping and experimentation
- Large codebase analysis on tight budgets
- Learning prompt engineering without API costs
- Internal tools with unpredictable usage spikes
Strengths
The 256K context window lets you feed entire repositories or multi-file codebases in a single request, removing the need for chunking strategies. Zero pricing eliminates cost anxiety during development cycles — you can iterate freely without watching token meters. The code-specific tuning means it handles syntax highlighting, function extraction, and basic refactoring tasks competently enough for internal tooling or educational use cases.
Trade-offs
Free models typically lag paid tiers on complex reasoning, nuanced code generation, and edge-case handling. Without public benchmarks, it's unclear how North Mini Code stacks up against GPT-4o-mini or Claude Haiku on standardized coding tests like HumanEval. Expect slower response times or rate limits compared to paid endpoints. The proprietary license means you can't self-host or fine-tune, limiting flexibility for teams wanting model customization.
Specifications
- Provider
- cohere
- Category
- llm
- Context length
- 256,000 tokens
- Max output
- 64,000 tokens
- Modalities
- text
- License
- proprietary
- Released
- 2026-06-17
Pricing
- Input
- $0.00/Mtok
- Output
- $0.00/Mtok
- Model ID
cohere/north-mini-code:free
Per-token prices show what the model costs upstream. On Switchy your team draws from one shared org credit pool - one plan, one balance for everyone.
Team cost calculator
5 seats · 80 msgs/day
Switchy meters this against your org's shared credit pool - one plan, one balance for everyone.
Providers
| Provider | Context | Input | Output | P50 latency | Throughput | 30d uptime |
|---|---|---|---|---|---|---|
| cohere | 256k | $0.00/Mtok | $0.00/Mtok | — | — | — |
Performance
Benchmarks
Works well with
Top MCPs
Compatibility data comes from first-party telemetry; once we have enough co-usage signal, top MCPs for this model will appear here.
How Switchy teams use it
Starter prompts
Codebase Documentation Generator
Review the following codebase files and generate a README with sections for architecture overview, key modules, and setup instructions. Focus on clarity for new contributors.
Multi-File Refactor Suggestions
Analyze these Python files for code duplication, unused imports, and opportunities to extract shared utilities. Provide specific line-number recommendations.
Dependency Conflict Resolver
Given this package.json and yarn.lock, identify version conflicts and suggest compatible dependency ranges that resolve the issues.
API Endpoint Mapper
Parse these Express.js route files and generate an API reference table with endpoints, HTTP methods, required parameters, and response shapes.
Test Coverage Gap Finder
Compare these source modules with the test files and list functions or branches that lack test coverage. Prioritize by complexity.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
Refactor this Python function to use list comprehension instead of a for loop: def square_evens(nums): result = []; for n in nums: if n % 2 == 0: result.append(n**2); return result
Here's the refactored version using list comprehension: ```python def square_evens(nums): return [n**2 for n in nums if n % 2 == 0] ``` This one-liner does the same work: it filters for even numbers with the `if n % 2 == 0` condition and squares them in a single pass. The list comprehension is more Pythonic and typically faster for operations like this since it's optimized at the interpreter level.
North Mini Code handles straightforward refactoring tasks cleanly, producing idiomatic Python with brief explanations. The 256k context window means you can paste entire modules for analysis. However, as a free-tier model without published benchmarks, expect less sophisticated reasoning on complex architectural decisions compared to paid alternatives.
Find the bug in this JavaScript: const users = [{id: 1, name: 'Alice'}, {id: 2, name: 'Bob'}]; const user = users.find(u => u.id = 3); console.log(user);
The bug is on line 2: you're using assignment (`=`) instead of comparison (`===`) in the find callback. **Current:** `u.id = 3` assigns 3 to `u.id` and returns 3 (truthy), so `find()` returns the first user. **Fixed:** `u.id === 3` This will correctly search for a user with id 3 (which doesn't exist, so `user` will be `undefined`). The assignment version mutates your data and always matches the first element.
The model correctly identifies a common mistake and explains both the symptom and the fix. Good for catching syntax-level bugs in short snippets. The free tier makes this useful for quick sanity checks, though without benchmark data we can't verify performance on subtle logic errors or large codebases.
Explain what this SQL query does: SELECT c.name, COUNT(o.id) as order_count FROM customers c LEFT JOIN orders o ON c.id = o.customer_id WHERE c.created_at > '2024-01-01' GROUP BY c.id, c.name HAVING COUNT(o.id) > 5;
This query finds active customers (created after Jan 1, 2024) who have placed more than 5 orders. **Breakdown:** - `LEFT JOIN` includes all customers, even those with zero orders - `WHERE` filters to recent customers before aggregation - `GROUP BY` collects rows per customer - `HAVING` filters groups to only those with >5 orders - Result: customer name + their order count Note: customers with 0-5 orders are excluded by the HAVING clause, even though LEFT JOIN initially includes them.
North Mini Code provides clear step-by-step explanations of query logic, useful for onboarding or documentation. The zero-cost pricing makes it practical for batch documentation tasks. Trade-off: without performance benchmarks, we can't assess how well it handles optimization advice or complex nested queries with CTEs.
Use-case deep-dives
When free beats paid for early-stage code prototyping
A 3-person startup building an internal tool generator needs to test whether LLM-assisted code completion fits their workflow before committing budget. North Mini Code (free) gives them 256K context—enough to load entire module histories—at zero cost during the discovery phase. The lack of public benchmarks means you're flying blind on quality versus GPT-4 or Claude, but for throwaway prototypes where you're learning the prompting patterns more than shipping production code, free removes the friction. Run 500 generations this week to see if the output style matches your stack. If the team decides it's worth productionizing, you've spent nothing to validate the approach and can upgrade to a benchmarked model with confidence.
Zero-cost code assistance for learning environments
A community coding bootcamp with 40 students needs an AI pair programmer for homework help but has no budget for API costs. North Mini Code (free) slots in as the default assistant: students paste their broken Python functions, get suggestions, and iterate without the instructor worrying about a monthly bill. The 256K context window handles multi-file projects, so learners can submit entire Flask apps for debugging feedback. Quality is unverified—no MBPP or HumanEval scores—so instructors should spot-check outputs and treat it as a teaching aid, not an oracle. If half the cohort finds it useful and the bootcamp scales to 200 students, migrate to a paid model with documented performance. Until then, free is the entire business case.
When zero-dollar code examples beat manual wiki updates
A 12-person SaaS team maintains an internal Notion wiki with 80+ code snippets showing how to call their API. Keeping examples current across Python, Node, and Go is a monthly chore no one wants. North Mini Code (free) automates it: feed the OpenAPI spec into the 256K context, prompt for idiomatic examples in each language, and regenerate the wiki section in 10 minutes. The output quality is a gamble without benchmarks, so a senior dev should review the first batch, but once the pattern works, the time savings justify the risk. If you're generating 500+ snippets monthly or need guaranteed correctness for customer-facing docs, pay for a model with published eval scores. For internal wiki maintenance where a human reviews anyway, free is the right call.
Frequently asked
Is Cohere North Mini Code good for coding tasks?
Yes, for basic code completion and simple debugging. The 256k context window handles large codebases well. However, with no public benchmarks available, expect performance below paid alternatives like GPT-4 or Claude for complex refactoring or architecture decisions. Best for prototyping or learning projects where cost matters more than output quality.
How does the free pricing compare to other code models?
It's completely free at $0 per million tokens, making it the cheapest option by definition. GPT-4o costs $2.50/$10 per Mtok and Claude Sonnet runs $3/$15. For students, hobbyists, or high-volume experimentation, this eliminates budget constraints entirely. Trade-off is likely weaker code quality and reasoning compared to paid tiers.
Can it handle multi-file refactoring with the 256k context?
The context window supports it technically—256k tokens fits roughly 50-80 medium-sized files. Practical limitation is the model's reasoning capability, not memory. Without benchmark data, assume it struggles with complex dependency tracking or architectural changes that require deep understanding across files. Use it for simpler cross-file edits.
Is this better than GitHub Copilot for free users?
Different use cases. Copilot excels at inline suggestions during active coding. North Mini Code works better for chat-based debugging or explaining existing code chunks due to the massive context window. If you need real-time autocomplete, stick with Copilot. For batch analysis or learning from large codebases, try this first.
Should I use this for production code generation?
No. Free models typically lack the reliability and accuracy needed for production. Use it for generating boilerplate, exploring API usage patterns, or drafting initial implementations that you'll review carefully. For production code, pay for GPT-4, Claude Sonnet, or Gemini Pro where benchmarks prove consistent quality and you get support guarantees.
Compare with
More language models
- DeepSeek: DeepSeek Flash Latestdeepseek
- DeepSeek: DeepSeek Pro Latestdeepseek
- DeepSeek: DeepSeek V3deepseek
- DeepSeek: DeepSeek V3 0324deepseek
- DeepSeek: DeepSeek V3.1deepseek
- DeepSeek: DeepSeek V3.1 Terminusdeepseek
- DeepSeek: DeepSeek V3.2deepseek
- DeepSeek: DeepSeek V3.2 Expdeepseek
- DeepSeek: DeepSeek V4.1 Flashdeepseek
- DeepSeek: DeepSeek V4.1 Flash 1017deepseek
- DeepSeek: DeepSeek V4.1 Flash (batch)deepseek
- DeepSeek: DeepSeek V4 Flash 0423deepseek