canitoolcall 0.1.0__tar.gz

canitoolcall-0.1.0/.gitignore

@@ -0,0 +1,29 @@
+# Isolated per-engine environments and spike scratch space (never committed)
+.venvs/
+.spikes/
+# Engine source clones, compiled harnesses, vocab-only GGUFs (built by scripts/engines/*.sh)
+.engines/
+
+# Run outputs (the matrix site is generated from these; publish via CI artifacts).
+# Dated snapshots (results/YYYY-MM-DD/, gzipped) are committed on purpose.
+/results/*
+!/results/[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]/
+/site/_build/
+
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+build/
+dist/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# OS / editors
+.DS_Store
+.idea/
+.vscode/

canitoolcall-0.1.0/CHANGELOG.md

@@ -0,0 +1,17 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses
+[semantic versioning](https://semver.org/).
+
+## [0.1.0] - 2026-09-26
+
+### Added
+
+- Fixture spec v0.1 (`spec/`), 469 fixtures across nine model families, each with provenance.
+- Offline replay through the pinned parsers of vLLM 0.30.0, SGLang 0.5.20, llama.cpp `a25c9865`,
+  Ollama `7af39318` and HF transformers 5.17.0, with eight checks and seeded token-level chunking.
+- Per-engine streaming granularity: multi-token chunkings are reported as synthetic for engines
+  whose servers stream one token per event (`run.synthetic_strategies`).
+- `canitoolcall probe` for live OpenAI-compatible endpoints, a pytest plugin, and the static matrix site.
+- A committed results snapshot (`results/2026-09-25/`) with every failure triaged.

canitoolcall-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at **[saurav.lall1+github@gmail.com](mailto:saurav.lall1+github@gmail.com)**. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

canitoolcall-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,144 @@
+# Contributing to CanIToolCall
+
+Thank you for helping. Most contributions fall into one of three kinds, and each fits in a single PR:
+
+1. **Add a model family.** This is the most common kind, and the rest of this guide centres on it.
+2. **Add fixtures to an existing family**, for example a new edge case or a regression from a bug report.
+3. **Add or update an engine adapter.**
+
+By participating you agree to the [Code of Conduct](CODE_OF_CONDUCT.md). Report security issues privately, as described in [SECURITY.md](SECURITY.md), not in public issues.
+
+## Development setup
+
+```sh
+uv sync                                   # main env: CLI, runner, checks, matrix (Python 3.12)
+uv run ruff check src tests scripts && uv run ruff format --check src tests scripts && uv run mypy && uv run pytest
+```
+
+CI runs exactly that command, plus `canitoolcall validate`, `uv build` and `twine check`. Engine tests (`@pytest.mark.engine("vllm")`) skip themselves until you build that engine's environment with `bash scripts/engines/<engine>.sh`. That script puts the engine in an **isolated** venv under `.venvs/<engine>/`. Never install vLLM, SGLang or torch into the main env.
+
+Read [`docs/DESIGN.md`](docs/DESIGN.md) for the architecture, and [`spec/README.md`](spec/README.md) for the fixture format.
+
+## Add a model family: one PR
+
+Suppose the new family's slug is `acme`, for a model `acme-ai/Acme-3`. The PR contains these files:
+
+| File | What it holds |
+|---|---|
+| `docs/formats/acme.md` | the format notes: the exact raw text, the special tokens, the source template URL and revision, the engine parsers that handle the format (with both vLLM's and SGLang's names), and known bugs with issue URLs |
+| `fixtures/acme/family.json` | the family metadata |
+| `fixtures/acme/*.jsonl` | the fixtures, grouped by topic (`basic.jsonl`, `parallel.jsonl`, `edge.jsonl`, `truncated.jsonl`, …) |
+| `scripts/fixtures/acme/build.py` | the generator that reproduces every `template_render` fixture |
+| `src/canitoolcall/adapters/<engine>.py` | only if an adapter needs a parser mapping for `acme` |
+
+### Step by step
+
+1. **Write the format notes first.** Render an assistant tool-call message through the model's **official** chat template or encoder, for example with `apply_chat_template` or the vendor's encoder library. Paste the output verbatim into `docs/formats/acme.md` and record the template URL at a pinned revision. Look up which parser each engine uses for it. [`docs/formats/qwen3-hermes.md`](docs/formats/qwen3-hermes.md) is a good model.
+
+2. **Write `fixtures/acme/family.json`** (schema: [`spec/family.schema.json`](spec/family.schema.json)):
+   - `slug`, `name`, `spec_version` and `has_reasoning`
+   - `markers`: every special string that must never leak into content, reasoning or arguments. The `no_leakage` check uses this list.
+   - `reference_models`: the models whose tokenizer and template the adapters use, each with:
+     - `repo` and `revision` (a full commit sha)
+     - `stop_tokens`, from `generation_config.json`
+     - `default_generation_prompt`, when `add_generation_prompt` pre-fills text such as `<think>\n`
+   - `format_notes`: `docs/formats/acme.md`
+
+3. **Write the generator, `scripts/fixtures/acme/build.py`.** Follow the "Token ids come first" rule in the spec:
+   1. Render with `apply_chat_template(tokenize=True)`.
+   2. Slice off the prompt ids.
+   3. Cut at the first stop id.
+   4. Store the result as `output_token_ids`, with a `tokenizer` pin.
+   5. Set `raw_output` to those ids decoded with `skip_special_tokens=False`.
+
+   Download only config and tokenizer files at pinned revisions, never weights. The script must be deterministic: re-running it must leave `git diff` clean. [`scripts/fixtures/qwen3-hermes/build.py`](scripts/fixtures/qwen3-hermes/build.py) is a complete example.
+
+4. **Cover the edge cases.** Aim for about 20 fixtures and use the tags from the spec:
+   - `single-call`, `parallel-calls` and `no-call`
+   - `nested-json`, `unicode`, `string-escapes` and `numeric-arguments`
+   - `empty-arguments` and `marker-in-arguments`
+   - `text-before-call`, `text-after-call`, `reasoning` and `reasoning-prefilled`
+   - `multi-turn` and `long-arguments`
+   - `truncated` and `malformed`: these carry an `expected_error` instead of `expected`
+   - `regression`: for fixtures taken from bug reports
+
+5. **Validate:** `uv run canitoolcall validate fixtures/acme/`.
+
+6. **Replay it** through every engine you can build, for example `uv run canitoolcall run --engine vllm --family acme`, and look at the result with `uv run canitoolcall matrix`. If the engine has no parser for the family, the adapter's `supports()` must say so, and the result is `unsupported`. When a failure looks like a real engine bug, first check that the fixture is right, then say so in the PR.
+
+7. **Open the PR** with the checklist below.
+
+### PR checklist
+
+- [ ] Every fixture has `provenance` (see below). Every `template_render` fixture names its `generator` and records `template_sha256`.
+- [ ] `output_token_ids` and `tokenizer` are present wherever the source allows.
+- [ ] Re-running the generator leaves `git diff` clean.
+- [ ] `canitoolcall validate` reports 0 issues, and the full lint and test command passes.
+- [ ] `docs/formats/acme.md` cites the template and every engine parser by URL at a pinned revision.
+
+## Fixture provenance rules
+
+**Never type a format by hand, and never invent one.** A fixture that looks plausible but is wrong makes an engine look broken when it is not. Every fixture needs a `provenance` block, in this order of preference:
+
+| `kind` | When | `source_url` | `license` |
+|---|---|---|---|
+| `template_render` | rendered through the official chat template or encoder by your generator script | the template file at the pinned revision | the model repo's license |
+| `engine_test` | copied verbatim from an engine's test suite | the test file at a commit, with a line anchor | vLLM, SGLang and transformers: Apache-2.0; llama.cpp and Ollama: MIT. Add `attribution`. |
+| `bug_report` | reproduces a public issue | the issue or comment URL | `NOASSERTION`, plus a short quote |
+| `recorded` | a real generation captured from the model | the log or dataset | as stated |
+| `spec_example` | quoted verbatim from the format's official spec or reference-library docs | the document at a commit, with a line anchor | the spec's license |
+
+**Rendering a past turn is not the same as generating one.** Chat templates serialize *history*, and history can differ from what the model *generates*:
+
+- Mistral v11 templates add a `[CALL_ID]` that the model never emits.
+- gpt-oss history puts the recipient in the role header.
+
+Engines parse generations. When the two differ, use an `engine_test` or `recorded` source, and explain why in `notes`.
+
+**Ids never change.** A fixture id is `acme/<kebab-name>` and is stable forever. If a fixture's content changes meaningfully, add a new id and delete the old one.
+
+## Add an engine adapter
+
+An adapter counts only if it runs **the engine's own parser code at a pinned version**. Never reimplement a parser. If something cannot run, report it as `unsupported`.
+
+1. **Build the environment.** `scripts/engines/<engine>.sh` builds `.venvs/<engine>` with pinned versions, plus any checkout or harness under `.engines/<engine>/` (gitignored). It must work on Linux and macOS, on x86_64 and arm64, with no GPU and no model weights.
+2. **Write the adapter class.** `src/canitoolcall/adapters/<engine>.py` defines one subclass of `canitoolcall.adapters.base.Adapter`:
+   - It must import with the **standard library only** at module level. Import the engine inside methods, because the worker loads the module inside the engine's venv with only `src/` on the path.
+   - Implement:
+     - `version`, and optionally `commit` and `engine_details`
+     - `supports(family, model)`: honest and cheap
+     - `parser_config`: record every parser name, template source and sha256, and every flag
+     - `units`: return the fixture's `output_token_ids`
+     - `parse`
+     - `parse_stream`: detokenize each group of ids with **the engine's own** incremental detokenizer, then call its streaming parser the way its server does
+   - Optionally implement `special_token_ids`, which enables the `special` strategy.
+   - Set `tokens_per_step = "one"` if the engine's server streams one event per generated token; multi-token chunkings are then reported as synthetic instead of counted.
+   - Follow the ten rules in the adapter contract in [`docs/DESIGN.md`](docs/DESIGN.md). Each rule exists because an adapter broke without it.
+3. **Compiled engines.** For an engine like llama.cpp or Ollama, put the harness in `harnesses/<engine>/`. It speaks JSON lines, and one process serves a whole run.
+4. **Register it.** Add one line to the `ENGINES` registry in `src/canitoolcall/adapters/__init__.py`, and add the engine to the matrix in `.github/workflows/nightly.yml`.
+5. **Test it.** Put the tests in `tests/adapters/test_<engine>.py`:
+   - a fast test of `supports` and `parser_config` that needs no engine
+   - `@pytest.mark.engine("<engine>")` tests that replay at least one fixture per supported family through the real worker
+
+Engine exceptions are **outcomes**: catch them and return `ParseResult(exception="Type: msg")`. Raise only for harness problems, which the runner records as `error`.
+
+## Reporting a parser bug upstream
+
+Each failing cell on the matrix site has a page with:
+
+- the failing checks and strategies
+- the observed parse, as a diff against the expected one
+- the parser configuration
+- a one-line replay command
+
+Before you file an issue with an engine:
+
+1. Re-run that command against the pinned version.
+2. Check the fixture's provenance.
+3. Link the fixture record in the issue.
+
+Please don't file bugs from the untriaged candidates in `docs/DESIGN.md` §6 until they have been turned into fixtures and verified.
+
+## Style
+
+Keep code typed (`mypy --strict`), use dataclasses, and format with `ruff format` (line length 120). Keep dependencies of the main package minimal. Write tests with pytest; the site's tests build their inputs with `RunResults` rather than committing results files.

canitoolcall-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

canitoolcall-0.1.0/LICENSES/deepseek-MIT.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 DeepSeek
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

canitoolcall-0.1.0/LICENSES/glm-5.3.txt

@@ -0,0 +1,29 @@
+GLM-5.3 License
+
+Copyright (c) 2026 Z.AI
+
+Permission is hereby granted, free of charge, to any person or entity (the "Licensee") obtaining a copy of this software — including the model weights, parameters, configuration files, inference and training code, and associated documentation (collectively, the "Software") — to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software; to run, deploy, fine-tune, or otherwise modify the Software and create derivative works from it; and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+1. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. The Licensee's use of the Software must comply with applicable laws and regulations.
+
+2. "Model as a Service" means giving a third party access to language model inference or fine-tuning (e.g., via API) in a manner that allows such third party to exercise meaningful control over the inputs, parameters, or training data. This does not include (a) end-user products with model capabilities solely embedded within specific features or harnesses, or (b) mere relaying of requests to models hosted by others.
+If the Licensee or any of its affiliates operates a Model as a Service business, and the aggregate revenue of the Licensee and its affiliates exceeds 10 billion US dollars (or the equivalent in other currencies) in total over any consecutive 12 months, the Licensee must pass Z.AI's security review before using the Software or its derivative works for any commercial purpose. The scope and method of the security review shall be reasonably determined by Z.AI.
+
+3. THE SOFTWARE AND ANY OUTPUT AND RESULTS THEREFROM ARE PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL Z.AI OR ITS AFFILIATES OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+For any questions regarding this license, please contact glmlicense@z.ai.
+
+-----
+
+版权所有 (c) 2026 Z.AI
+
+特此免费授予任何获得本软件副本的个人或实体（"被许可方"）——包括模型权重、参数、配置文件、推理和训练代码及相关文档（统称"软件"）——不受限制地处理本软件的权利，包括但不限于：使用、复制、修改、合并、发布、分发、再许可和/或销售软件副本；运行、部署、微调或以其他方式修改软件并创建衍生作品；以及允许获得软件的其他人行使上述权利，但须遵守以下条件：
+
+1. 上述版权声明和本许可声明应包含在软件的所有副本或实质性部分中。被许可方对软件的使用必须符合适用法律法规。
+
+2. "模型即服务"指以允许第三方对输入、参数或训练数据行使实质性控制的方式，向第三方提供语言模型推理或微调服务（如通过API）。不包括：(a) 模型能力仅嵌入特定功能或框架中的终端用户产品，或(b) 单纯转发请求至他人托管的模型。
+若被许可方或其关联方运营"模型即服务"业务，且被许可方及关联方在任意连续12个月内累计总收入超过100亿美元（或等值其他货币），则被许可方在使用软件或其衍生作品进行任何商业用途之前，须通过Z.AI的安全审查。安全审查的范围和方式由Z.AI合理确定。
+
+3. 软件及其任何输出和结果均按"现状"提供，不附带任何形式的保证，无论是明示还是暗示，包括但不限于适销性、特定用途适用性和不侵权的保证。在任何情况下，Z.AI或其关联方或版权持有人均不对任何索赔、损害或其他责任承担责任，无论该责任是基于合同、侵权或其他方式，因软件或使用软件而产生或与之相关。
+
+如对本许可有任何疑问，请联系 glmlicense@z.ai。

canitoolcall-0.1.0/LICENSES/kimi-k2-modified-MIT.txt

@@ -0,0 +1,27 @@
+Modified MIT License
+
+Copyright (c) 2025 Moonshot AI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the “Software”), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+Our only modification part is that, if the Software (or any derivative works
+thereof) is used for any of your commercial products or services that have
+more than 100 million monthly active users, or more than 20 million US dollars
+(or equivalent in other currencies) in monthly revenue, you shall prominently
+display "Kimi K2" on the user interface of such product or service.

canitoolcall-0.1.0/LICENSES/kimi-k2.6-modified-MIT.txt

@@ -0,0 +1,27 @@
+Modified MIT License
+
+Copyright (c) 2026 Moonshot AI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the “Software”), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+Our only modification part is that, if the Software (or any derivative works
+thereof) is used for any of your commercial products or services that have
+more than 100 million monthly active users, or more than 20 million US dollars
+(or equivalent in other currencies) in monthly revenue, you shall prominently
+display "Kimi K2.6" on the user interface of such product or service.

canitoolcall-0.1.0/LICENSES/kimi-k3.txt

@@ -0,0 +1,52 @@
+Kimi K3 License
+
+Copyright (c) 2026 Moonshot AI
+
+Permission is hereby granted, free of charge, to any person (the "Licensee")
+obtaining a copy of this software — including the model weights, parameters,
+configuration files, inference and training code, and associated documentation
+(collectively, the "Software") — to deal in the Software without restriction.
+This includes, without limitation, the rights to use, copy, modify, merge,
+publish, distribute, sublicense, and/or sell copies of the Software; to run,
+deploy, fine-tune, or otherwise modify the Software and create derivative works
+from it; and to permit persons to whom the Software is furnished to do so, in
+each case subject to the following conditions:
+
+1. The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software. Licensee's use of the
+Software must comply with applicable laws and regulations.
+
+2. "Model as a Service" means giving a third party access to language model
+inference or fine-tuning (e.g., via API) in a manner that allows such third
+party to exercise meaningful control over the inputs, parameters, or training
+data. This does not include (a) end-user products with model capabilities solely
+embedded within specific features or harnesses, or (b) mere relaying of requests
+to models hosted by others.
+
+If the Licensee or any of its affiliates operates a Model as a Service business,
+and the aggregate revenue of the Licensee and its affiliates exceeds 20 million
+US dollars (or the equivalent in other currencies) in total over any consecutive
+12 months, the Licensee must enter into a separate agreement with Moonshot AI
+before using the Software or its derivative works for any commercial purpose. 
+
+3. If the Software (or any derivative works thereof) is used for any of the
+Licensee's commercial products or services that have more than 100 million
+monthly active users, or more than 20 million US dollars (or equivalent in other
+currencies) in monthly revenue, "Kimi K3" must be prominently displayed on the
+user interface of such product or service.
+
+4. The requirements set forth in Sections 2 and 3 do not apply to: (a) internal
+use of the Software, defined as any use that does not make the Software, its
+outputs, or its underlying capabilities available to third parties; or (b) any
+use of the Software accessed through Moonshot AI's official products or
+certified inference partners.
+
+5. THE SOFTWARE AND ANY OUTPUT AND RESULTS THEREFROM ARE PROVIDED ON AN “AS IS”
+BASIS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
+LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
+AND NONINFRINGEMENT. IN NO EVENT SHALL MOONSHOT AI OR ITS AFFILIATES OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+For any questions regarding this license, please contact <license@moonshot.ai>.