North Mini Code 1.0 is Cohere’s model for agentic software engineering, terminal tasks and code generation. It takes text and produces text, including code, explanations and tool requests. The manufacturer released its weights under Apache 2.0 and identifies it as the first model in the North code-agent family. It is a specialized coding profile rather than an image-understanding model or a generic decision scorer.
The model has 30 billion total parameters with about 3 billion active. Its decoder-only Transformer uses a sparse Mixture of Experts with 128 experts, eight activated per token, and a dense layer before the sparse layers. Sliding-window attention with rotary positions is interleaved with global attention without positional embeddings in a 3:1 ratio. The active-parameter figure describes the computation used for a token, not the total set of weights that must be stored.
Cohere’s post-training uses two stages of supervised fine-tuning followed by reinforcement learning with verifiable rewards, focused on software engineering and terminal work. The producer describes training across multiple agent harnesses instead of one fixed scaffold. That supports preparing a task around the required behavior and available tools, while the surrounding harness remains responsible for obtaining files, executing commands and returning observations.
Supply the current code and behavior, the requested change, the relevant file or interface boundaries and the evidence that will establish completion. For a bug, include the observed error or failing input and the expected result. For a feature, state the required behavior and the compatibility constraints. A useful final artifact is a proposed code change with an explanation and results from checks that actually ran.
An illustrative request can ask to update a parser for an additional supported input while preserving existing formats. Identify representative inputs and the part of the repository that defines the parser’s behavior. The model can use code and tool observations to develop the change; a generated patch or a statement that a command should run is not evidence that the command succeeded.
The native model card documents tool-use training and recommends JSON-schema tool descriptions through the model’s chat template. Describe a tool’s purpose and arguments clearly. A command-execution tool can return the actual output and status, while a file-inspection tool can return the material the next step needs. Keep each tool result associated with its call identifier so later analysis uses the intended observation.
The producer’s example preserves a tool call and the assistant’s reasoning in history, executes the tool, and adds its result before generating again. Its native template example uses a structured dictionary for the tool result. Preserve that representation according to the documented integration rather than assuming every unrelated API serializes tool results in the same way. A JSON schema describing a tool’s arguments is different from claiming arbitrary schema-constrained final output support.
North Mini Code supports interleaved thinking, which the producer recommends enabling for agentic work. Carry model-generated thinking content and tool calls into subsequent agent steps and conversation turns. The native example keeps a reasoning field with the assistant message and returns the corresponding tool observation afterward. This preserves the information the model used when deciding what to inspect or change next.
Keep the current objective, the source material and actual observations in the task history. For a longer repository task, summarize the final result around the changed behavior and the useful artifact, while retaining the evidence needed to review it. Interleaved reasoning does not imply that a short visible answer required no analysis, nor does it establish that an action described by the model has already occurred.
The maker also identifies scientific coding and algorithmic reasoning outside an agent loop. Supply the problem definition, input and output format, constraints, relevant numerical assumptions and expected edge behavior. Ask for a complete function or program when that is the artifact required, with an explanation at the level the reader needs.
For code explanation, provide the implementation and the particular behavior or dependency to clarify. For data-visualization code, identify the supplied fields and the intended comparison rather than leaving the chart’s purpose implicit. The producer’s development examples include code explanation, editing, visualization and implementation from a specification. These are task patterns for generating or modifying code, not a promise of correct results for every repository or framework.
The manufacturer’s model card and API page list a 256K-token context window and a maximum output of 64K tokens. Prepare substantial repository material around those separate allowances and the final artifact’s size. Keep source boundaries and identifiers intact, and remove irrelevant material rather than assuming that a large window eliminates the need for a focused brief.
The native model card recommends temperature 1.0 and top_p 0.95 for generation and uses the model’s chat template, including a generation prompt, for text and tool workflows. Its example output limits are settings for those examples, not a replacement for the model’s published maximum. Cohere publishes BF16 weights and a separately named FP8 artifact. Select the appropriate artifact when preparing a deployment.
A useful North Mini Code result is an inspectable code artifact or technical explanation tied to the supplied requirements. Compare the result with the original behavior and actual tool output, check assumptions that affect the code, and retain the source and observations needed for review. The text-only coding model supplies reasoning and generated content; the surrounding application performs the operations that turn those proposals into a completed software task.
", "aboutText": "North Mini Code 1.0 is Cohere’s model for agentic software engineering, terminal tasks and code generation. It takes text and produces text, including code, explanations and tool requests. The manufacturer released its weights under Apache 2.0 and identifies it as the first model in the North code-agent family. It is a specialized coding profile rather than an image-understanding model or a generic decision scorer.\n\n### Sparse architecture and coding preparation\n\nThe model has 30 billion total parameters with about 3 billion active. Its decoder-only Transformer uses a sparse Mixture of Experts with 128 experts, eight activated per token, and a dense layer before the sparse layers. Sliding-window attention with rotary positions is interleaved with global attention without positional embeddings in a 3:1 ratio. The active-parameter figure describes the computation used for a token, not the total set of weights that must be stored.\n\nCohere’s post-training uses two stages of supervised fine-tuning followed by reinforcement learning with verifiable rewards, focused on software engineering and terminal work. The producer describes training across multiple agent harnesses instead of one fixed scaffold. That supports preparing a task around the required behavior and available tools, while the surrounding harness remains responsible for obtaining files, executing commands and returning observations.\n\n### Prepare a repository-level change\n\nSupply the current code and behavior, the requested change, the relevant file or interface boundaries and the evidence that will establish completion. For a bug, include the observed error or failing input and the expected result. For a feature, state the required behavior and the compatibility constraints. A useful final artifact is a proposed code change with an explanation and results from checks that actually ran.\n\nAn illustrative request can ask to update a parser for an additional supported input while preserving existing formats. Identify representative inputs and the part of the repository that defines the parser’s behavior. The model can use code and tool observations to develop the change; a generated patch or a statement that a command should run is not evidence that the command succeeded.\n\n### Terminal tools and structured observations\n\nThe native model card documents tool-use training and recommends JSON-schema tool descriptions through the model’s chat template. Describe a tool’s purpose and arguments clearly. A command-execution tool can return the actual output and status, while a file-inspection tool can return the material the next step needs. Keep each tool result associated with its call identifier so later analysis uses the intended observation.\n\nThe producer’s example preserves a tool call and the assistant’s reasoning in history, executes the tool, and adds its result before generating again. Its native template example uses a structured dictionary for the tool result. Preserve that representation according to the documented integration rather than assuming every unrelated API serializes tool results in the same way. A JSON schema describing a tool’s arguments is different from claiming arbitrary schema-constrained final output support.\n\n### Interleaved thinking and multi-turn history\n\nNorth Mini Code supports interleaved thinking, which the producer recommends enabling for agentic work. Carry model-generated thinking content and tool calls into subsequent agent steps and conversation turns. The native example keeps a reasoning field with the assistant message and returns the corresponding tool observation afterward. This preserves the information the model used when deciding what to inspect or change next.\n\nKeep the current objective, the source material and actual observations in the task history. For a longer repository task, summarize the final result around the changed behavior and the useful artifact, while retaining the evidence needed to review it. Interleaved reasoning does not imply that a short visible answer required no analysis, nor does it establish that an action described by the model has already occurred.\n\n### Standalone code and explanation tasks\n\nThe maker also identifies scientific coding and algorithmic reasoning outside an agent loop. Supply the problem definition, input and output format, constraints, relevant numerical assumptions and expected edge behavior. Ask for a complete function or program when that is the artifact required, with an explanation at the level the reader needs.\n\nFor code explanation, provide the implementation and the particular behavior or dependency to clarify. For data-visualization code, identify the supplied fields and the intended comparison rather than leaving the chart’s purpose implicit. The producer’s development examples include code explanation, editing, visualization and implementation from a specification. These are task patterns for generating or modifying code, not a promise of correct results for every repository or framework.\n\n### Context, output and generation settings\n\nThe manufacturer’s model card and API page list a 256K-token context window and a maximum output of 64K tokens. Prepare substantial repository material around those separate allowances and the final artifact’s size. Keep source boundaries and identifiers intact, and remove irrelevant material rather than assuming that a large window eliminates the need for a focused brief.\n\nThe native model card recommends temperature 1.0 and top_p 0.95 for generation and uses the model’s chat template, including a generation prompt, for text and tool workflows. Its example output limits are settings for those examples, not a replacement for the model’s published maximum. Cohere publishes BF16 weights and a separately named FP8 artifact. Select the appropriate artifact when preparing a deployment.\n\nA useful North Mini Code result is an inspectable code artifact or technical explanation tied to the supplied requirements. Compare the result with the original behavior and actual tool output, check assumptions that affect the code, and retain the source and observations needed for review. The text-only coding model supplies reasoning and generated content; the surrounding application performs the operations that turn those proposals into a completed software task.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "c49be12d73b07866f93207aa26edea7b5b7e3a0071b88daaa9595ad8605415e2", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "cohere/north-mini-code:freeNorth Mini Code 1.0 is Cohere’s text-only model for code generation, repository changes and terminal-driven agent tasks. Its sparse 30B-total/3B-active design supports tool use and interleaved thinking, with a documented 256K context and 64K output allowance.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
North Mini Code 1.0 is Cohere’s model for agentic software engineering, terminal tasks and code generation. It takes text and produces text, including code, explanations and tool requests. The manufacturer released its weights under Apache 2.0 and identifies it as the first model in the North code-agent family. It is a specialized coding profile rather than an image-understanding model or a generic decision scorer.
The model has 30 billion total parameters with about 3 billion active. Its decoder-only Transformer uses a sparse Mixture of Experts with 128 experts, eight activated per token, and a dense layer before the sparse layers. Sliding-window attention with rotary positions is interleaved with global attention without positional embeddings in a 3:1 ratio. The active-parameter figure describes the computation used for a token, not the total set of weights that must be stored.
Cohere’s post-training uses two stages of supervised fine-tuning followed by reinforcement learning with verifiable rewards, focused on software engineering and terminal work. The producer describes training across multiple agent harnesses instead of one fixed scaffold. That supports preparing a task around the required behavior and available tools, while the surrounding harness remains responsible for obtaining files, executing commands and returning observations.
Supply the current code and behavior, the requested change, the relevant file or interface boundaries and the evidence that will establish completion. For a bug, include the observed error or failing input and the expected result. For a feature, state the required behavior and the compatibility constraints. A useful final artifact is a proposed code change with an explanation and results from checks that actually ran.
An illustrative request can ask to update a parser for an additional supported input while preserving existing formats. Identify representative inputs and the part of the repository that defines the parser’s behavior. The model can use code and tool observations to develop the change; a generated patch or a statement that a command should run is not evidence that the command succeeded.
The native model card documents tool-use training and recommends JSON-schema tool descriptions through the model’s chat template. Describe a tool’s purpose and arguments clearly. A command-execution tool can return the actual output and status, while a file-inspection tool can return the material the next step needs. Keep each tool result associated with its call identifier so later analysis uses the intended observation.
The producer’s example preserves a tool call and the assistant’s reasoning in history, executes the tool, and adds its result before generating again. Its native template example uses a structured dictionary for the tool result. Preserve that representation according to the documented integration rather than assuming every unrelated API serializes tool results in the same way. A JSON schema describing a tool’s arguments is different from claiming arbitrary schema-constrained final output support.
North Mini Code supports interleaved thinking, which the producer recommends enabling for agentic work. Carry model-generated thinking content and tool calls into subsequent agent steps and conversation turns. The native example keeps a reasoning field with the assistant message and returns the corresponding tool observation afterward. This preserves the information the model used when deciding what to inspect or change next.
Keep the current objective, the source material and actual observations in the task history. For a longer repository task, summarize the final result around the changed behavior and the useful artifact, while retaining the evidence needed to review it. Interleaved reasoning does not imply that a short visible answer required no analysis, nor does it establish that an action described by the model has already occurred.
The maker also identifies scientific coding and algorithmic reasoning outside an agent loop. Supply the problem definition, input and output format, constraints, relevant numerical assumptions and expected edge behavior. Ask for a complete function or program when that is the artifact required, with an explanation at the level the reader needs.
For code explanation, provide the implementation and the particular behavior or dependency to clarify. For data-visualization code, identify the supplied fields and the intended comparison rather than leaving the chart’s purpose implicit. The producer’s development examples include code explanation, editing, visualization and implementation from a specification. These are task patterns for generating or modifying code, not a promise of correct results for every repository or framework.
The manufacturer’s model card and API page list a 256K-token context window and a maximum output of 64K tokens. Prepare substantial repository material around those separate allowances and the final artifact’s size. Keep source boundaries and identifiers intact, and remove irrelevant material rather than assuming that a large window eliminates the need for a focused brief.
The native model card recommends temperature 1.0 and top_p 0.95 for generation and uses the model’s chat template, including a generation prompt, for text and tool workflows. Its example output limits are settings for those examples, not a replacement for the model’s published maximum. Cohere publishes BF16 weights and a separately named FP8 artifact. Select the appropriate artifact when preparing a deployment.
A useful North Mini Code result is an inspectable code artifact or technical explanation tied to the supplied requirements. Compare the result with the original behavior and actual tool output, check assumptions that affect the code, and retain the source and observations needed for review. The text-only coding model supplies reasoning and generated content; the surrounding application performs the operations that turn those proposals into a completed software task.
POST /v1/chat/completionstexttext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits cohere/north-mini-code:free | Default— |
Fieldmessages | Typearray | RequirementRequired | Values & limits | Default— |
Fieldstream | Typeboolean | RequirementOptional | Values & limits false | Defaultfalse |
Fieldmax_tokens | Typeinteger | RequirementOptional | Values & limits Minimum: 1 Maximum: 64,000 | Default— |
Fieldmax_completion_tokens | Typeinteger | RequirementOptional | Values & limits Minimum: 1 Maximum: 64,000 | Default— |
Fieldn | Typeinteger | RequirementOptional | Values & limits Minimum: 1 Maximum: 128 | Default— |
Fieldtemperature | Typenumber | RequirementOptional | Values & limits | Default— |
Fieldtop_p | Typenumber | RequirementOptional | Values & limits | Default— |
Fieldseed | Typeinteger | RequirementOptional | Values & limits | Default— |
Fieldstop | Type | RequirementOptional | Values & limits | Default— |
Fieldfrequency_penalty | Typenumber | RequirementOptional | Values & limits | Default— |
Fieldpresence_penalty | Typenumber | RequirementOptional | Values & limits | Default— |
Fielduser | Typestring | RequirementOptional | Values & limits | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, messages |
Parameteroptional | Contractstream, max_tokens, max_completion_tokens, n, temperature, top_p, seed, stop, frequency_penalty, presence_penalty, user |
Parametermaterial_types | Contracttext |
Parameterconditions | ContractUse literal text messages only. Cache controls, tools, image/audio/video content and streamed responses are unavailable for this method., The complete encoded JSON request must not exceed 256000 bytes. |
Lifecycle: synchronous_json
Tariff references do not add request options. Supported parameters are listed for the selected method.
| Configuration | Rate schedule | Charge |
|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens $0 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np=json.loads('{"model": "cohere/north-mini-code:free", "messages": [{"role": "user", "content": "Summarize the supplied text in three concise points."}], "stream": false}')\n\nPath("request.json").write_text(json.dumps(p,ensure_ascii=False))\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/chat/completions \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\n# Submit once. Retain the complete result, original identifiers and every response header.\nJSON
Keep every complete returned response, file and content part.
Retain the complete response, all actual results, original identifiers, usage and response headers.
Preserve the original response, headers and X-Client-Request-ID. An uncertain outcome does not authorize another creation.
Ailoot Ultra cohere/north-mini-code:free
Use the method paths shown above.
cohere/north-mini-code:freeNorth Mini Code 1.0 is Cohere’s text-only model for code generation, repository changes and terminal-driven agent tasks. Its sparse 30B-total/3B-active design supports tool use and interleaved thinking, with a documented 256K context and 64K output allowance.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
North Mini Code 1.0 is Cohere’s model for agentic software engineering, terminal tasks and code generation. It takes text and produces text, including code, explanations and tool requests. The manufacturer released its weights under Apache 2.0 and identifies it as the first model in the North code-agent family. It is a specialized coding profile rather than an image-understanding model or a generic decision scorer.
The model has 30 billion total parameters with about 3 billion active. Its decoder-only Transformer uses a sparse Mixture of Experts with 128 experts, eight activated per token, and a dense layer before the sparse layers. Sliding-window attention with rotary positions is interleaved with global attention without positional embeddings in a 3:1 ratio. The active-parameter figure describes the computation used for a token, not the total set of weights that must be stored.
Cohere’s post-training uses two stages of supervised fine-tuning followed by reinforcement learning with verifiable rewards, focused on software engineering and terminal work. The producer describes training across multiple agent harnesses instead of one fixed scaffold. That supports preparing a task around the required behavior and available tools, while the surrounding harness remains responsible for obtaining files, executing commands and returning observations.
Supply the current code and behavior, the requested change, the relevant file or interface boundaries and the evidence that will establish completion. For a bug, include the observed error or failing input and the expected result. For a feature, state the required behavior and the compatibility constraints. A useful final artifact is a proposed code change with an explanation and results from checks that actually ran.
An illustrative request can ask to update a parser for an additional supported input while preserving existing formats. Identify representative inputs and the part of the repository that defines the parser’s behavior. The model can use code and tool observations to develop the change; a generated patch or a statement that a command should run is not evidence that the command succeeded.
The native model card documents tool-use training and recommends JSON-schema tool descriptions through the model’s chat template. Describe a tool’s purpose and arguments clearly. A command-execution tool can return the actual output and status, while a file-inspection tool can return the material the next step needs. Keep each tool result associated with its call identifier so later analysis uses the intended observation.
The producer’s example preserves a tool call and the assistant’s reasoning in history, executes the tool, and adds its result before generating again. Its native template example uses a structured dictionary for the tool result. Preserve that representation according to the documented integration rather than assuming every unrelated API serializes tool results in the same way. A JSON schema describing a tool’s arguments is different from claiming arbitrary schema-constrained final output support.
North Mini Code supports interleaved thinking, which the producer recommends enabling for agentic work. Carry model-generated thinking content and tool calls into subsequent agent steps and conversation turns. The native example keeps a reasoning field with the assistant message and returns the corresponding tool observation afterward. This preserves the information the model used when deciding what to inspect or change next.
Keep the current objective, the source material and actual observations in the task history. For a longer repository task, summarize the final result around the changed behavior and the useful artifact, while retaining the evidence needed to review it. Interleaved reasoning does not imply that a short visible answer required no analysis, nor does it establish that an action described by the model has already occurred.
The maker also identifies scientific coding and algorithmic reasoning outside an agent loop. Supply the problem definition, input and output format, constraints, relevant numerical assumptions and expected edge behavior. Ask for a complete function or program when that is the artifact required, with an explanation at the level the reader needs.
For code explanation, provide the implementation and the particular behavior or dependency to clarify. For data-visualization code, identify the supplied fields and the intended comparison rather than leaving the chart’s purpose implicit. The producer’s development examples include code explanation, editing, visualization and implementation from a specification. These are task patterns for generating or modifying code, not a promise of correct results for every repository or framework.
The manufacturer’s model card and API page list a 256K-token context window and a maximum output of 64K tokens. Prepare substantial repository material around those separate allowances and the final artifact’s size. Keep source boundaries and identifiers intact, and remove irrelevant material rather than assuming that a large window eliminates the need for a focused brief.
The native model card recommends temperature 1.0 and top_p 0.95 for generation and uses the model’s chat template, including a generation prompt, for text and tool workflows. Its example output limits are settings for those examples, not a replacement for the model’s published maximum. Cohere publishes BF16 weights and a separately named FP8 artifact. Select the appropriate artifact when preparing a deployment.
A useful North Mini Code result is an inspectable code artifact or technical explanation tied to the supplied requirements. Compare the result with the original behavior and actual tool output, check assumptions that affect the code, and retain the source and observations needed for review. The text-only coding model supplies reasoning and generated content; the surrounding application performs the operations that turn those proposals into a completed software task.
POST /v1/messagestexttext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits cohere/north-mini-code:free | Default— |
Fieldmessages | Typearray | RequirementRequired | Values & limits | Default— |
Fieldstream | Typeboolean | RequirementOptional | Values & limits false | Defaultfalse |
Fieldsystem | Typestring | RequirementOptional | Values & limits | Default— |
Fieldmax_tokens | Typeinteger | RequirementRequired | Values & limits Minimum: 1 Maximum: 64,000 | Default— |
Fieldtemperature | Typenumber | RequirementOptional | Values & limits | Default— |
Fieldtop_p | Typenumber | RequirementOptional | Values & limits | Default— |
Fieldtop_k | Typeinteger | RequirementOptional | Values & limits | Default— |
Fieldstop_sequences | Typearray | RequirementOptional | Values & limits | Default— |
Fieldmetadata | Typeobject | RequirementOptional | Values & limits | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, messages, max_tokens |
Parameteroptional | Contractstream, system, temperature, top_p, top_k, stop_sequences, metadata |
Parametermaterial_types | Contracttext |
Parameterconditions | ContractUse literal text messages only. Cache controls, tools, image/audio/video content and streamed responses are unavailable for this method., The complete encoded JSON request must not exceed 256000 bytes. |
Lifecycle: synchronous_json
Tariff references do not add request options. Supported parameters are listed for the selected method.
| Configuration | Rate schedule | Charge |
|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens $0 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np=json.loads('{"model": "cohere/north-mini-code:free", "messages": [{"role": "user", "content": "Summarize the supplied text in three concise points."}], "stream": false, "max_tokens": 256}')\n\nPath("request.json").write_text(json.dumps(p,ensure_ascii=False))\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/messages \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\n# Submit once. Retain the complete result, original identifiers and every response header.\nJSON
Keep every complete returned response, file and content part.
Retain the complete response, all actual results, original identifiers, usage and response headers.
Preserve the original response, headers and X-Client-Request-ID. An uncertain outcome does not authorize another creation.
Ailoot Ultra cohere/north-mini-code:free
Use the method paths shown above.