# Fix list: GLiClass

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/gliclass, the October 2026 research run, assessed 8 October 2026. Grade D, 49.9 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on GLiClass: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 43 out of 100, up to 11.4 more on the total

Why it scored 43: Scored on the local-package checklist, since GLiClass is a library and weights the owner runs. `pip install gliclass` from PyPI at 0.1.20 with Python 3.10 or newer stated. The README's source install calls a `requirements.txt` the repository doesn't have, and the base v3.0 card still names `transformers>=4.48.0` while the package requires 5.0 (17 of 20). A public Tests workflow runs 151 pytest functions on Python 3.10 to 3.12 and a ruff job. Its last three runs on main, all on 24 September 2026, failed, after five passing runs from 19 May to 21 July. We didn't read which job failed (10 of 25). 15 issues and 1 pull request were open on 8 October, the oldest from 22 September 2024, among them #44 (models not loading with transformers v5, 6 July 2026), #35 (demo error, 6 February 2026) and #12 (every label scored 0.99). We didn't check reply times (12 of 25). No changelog file. Three GitHub releases carry one-line notes, and 0.1.18 moved the dependency floor to transformers 5 in a patch version (4 of 15). Version 0.1.20, with no statement of stability (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Security & auth, 38 out of 100, up to 10.9 more on the total

Why it scored 38: Read as software the owner runs. No account. The Ray Serve deployment checks no credential and has no option for one, and the command line binds to 0.0.0.0 by default (6 of 30). A classifier has no write actions, and the one other route, `/adapter-cache`, only reads (15 of 20). The output is labels and scores, so no untrusted text comes back. The docs warn that the safety checkpoints can miss new or obfuscated attacks. Nothing documents how hostile text moves a score (10 of 15). The server logs start-up and label truncation only, and the docs describe no per-call record (3 of 15). No SECURITY.md, no security.txt on knowledgator.com (404) and no bounty. Weights are safetensors and PyPI releases use trusted publishing. `gliclass/config.py` loads an unknown encoder's configuration with `trust_remote_code=True` (4 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 3. Schema & documentation, 49 out of 100, up to 8.3 more on the total

Why it scored 49: Read for a model the owner serves. No OpenAPI file. The serving page documents the seven request fields of `POST /gliclass` and the response array in a table, and the pipeline's Python signatures carry type hints (10 of 25). docs.knowledgator.com has no llms.txt (404). The README, `docs/streaming.md` and the model cards are Markdown (5 of 10). The cards and docs name the intended uses (topic, sentiment, intent, natural language inference, reranking) and print per-dataset F1 that shows the weak cases, such as 0.3376 on sst5 for base v3.0. The base card has no limitations section and says nothing on calibration (11 of 20). Labels are free strings or a dict of groups, the mode is one of two values and `threshold` is a number. The HTTP handler reads fields from the body without validation, and a list in `texts` is cut to its first item (8 of 15). Examples for every mode in the docs. The handler's 400 and 404 answers are not documented, and a request without `labels` gets a 404 (8 of 15). Versions on PyPI and version numbers in model names, with three one-line GitHub release notes and no changelog (7 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 4. Agent ergonomics, 60 out of 100, up to 6.5 more on the total

Why it scored 60: Read as an API an agent calls for a decision, as with the other decision models. The answer is a short list of labels and scores and no text is generated. Text and labels share one sequence, 1,024 tokens by default, with 25 labels by default (17 of 25). The caller sets a threshold, picks single-label or multi-label, and can ask for hierarchical output. The pipeline takes a batch of texts and a chunking pipeline handles long documents. The HTTP endpoint takes one text a request (15 of 20). Errors are `{"error": "..."}` with 400 or 404 and are undocumented. Truncation of long input is silent (7 of 20). Classification calls are stateless and safe to retry. The server has a request timeout and a queue capacity in its configuration. We found no `Retry-After` or retry guidance in the serve package or the docs (12 of 20). Loading takes a model, a tokeniser and a pipeline call, and a Python client ships with the server. Python is the only language, and the server defaults to CUDA and needs three flags on a CPU (9 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 5. Payments & pricing, 60 out of 100, up to 5 more on the total

Why it scored 60: Free Apache-2.0 software with nothing to buy, so 20 + 20 + 20 for pricing, free use and no sign-up under the self-hosted rule. No payment protocol (0). Knowledgator's hosted platform and its plans were unreachable from our network on 8 October 2026 and are not graded here.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 6. Maintenance & community, 44 out of 100, up to 4.9 more on the total

Why it scored 44: Read for an open-weight model with a library. 0.1.20 on 21 July 2026, 79 days before the check (20 of 30). One release in the last 90 days, and the newest GLiClass checkpoints we found on the Hub date from April 2026 (0 of 20). Three outside pull requests were merged on 24 September 2026. 15 issues were open, eleven of them more than a year old, and we didn't check reply times. A Discord server is linked (10 of 25). The Python package is current and runs on transformers 5. No other SDK (10 of 15). CI and a `uv.lock` exist, and PyPI publishing is automated on tags, but the Tests workflow is failing on main (4 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Transparency & trust, 64 out of 100, up to 3.2 more on the total

Made of editorial 60, provenance 68.

Why it scored 64: Apache-2.0 for the library and the weights, with `train.py`, the training datasets named on the card and an arXiv paper (30). Self-hosted, so inputs stay on the owner's hardware, though no project page says so. The company's privacy policy of 21 September 2023 covers its website and services, not the library (18 of 30). No deprecation policy. Older model generations stay on the Hub without a notice of which are current (2 of 20). We found no telemetry code in the package and no statement either way. Weights download from the Hugging Face Hub (10 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: knowledgator.com, registered 2021-06-25 (5 years) (11 of 15)
- Status page: not found (0 of 10)
- security.txt: not found (0 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: platform.knowledgator.com (the hosted platform and its plans page). Our network's proxy answered 502 for that host, so whether GLiClass is sold as a hosted API, and at what price, is not established.
- unchecked: which job (pytest or ruff) failed in the three Tests runs of 24 September 2026. The run list was read, the logs were not.
- unchecked: reply times on issues and pull requests. The GitHub API refused us for its rate limit, and we read the issue list from the web page only.
- The lead named ONNX exports. We found no ONNX file in `knowledgator/gliclass-base-v3.0`, none among Knowledgator's 31 GLiClass repositories by name, and no export command in the library. Community ONNX builds under other accounts were not searched.
- The lead's statement that OpenClaw's docs name GLiClass as a local option was not checked.
- Licences were read for the library and `gliclass-base-v3.0` only, not for each of the 31 checkpoints.
- The fit with decision models is loose. GLiClass returns softmax or sigmoid label scores and publishes F1 only, with no expected calibration error or Brier score.
- `provenance.terms` and `provenance.privacy` are left out. Knowledgator's terms of use and privacy policy cover its website and hosted services, and no document other than the Apache-2.0 licence governs the library.

## Weaknesses

- No calibration evidence. The cards report F1 only, and the docs tell users to calibrate thresholds on their own traffic
- The bundled server has no authentication, and `python -m gliclass.serve` binds to 0.0.0.0 by default
- The last three runs of the Tests workflow on main, all on 24 September 2026, failed
- Still 0.1.x with no changelog file. 0.1.18 raised the `transformers` floor to 5.0, and issue #44 on v5 loading has been open since 6 July 2026
- No OpenAPI file, no llms.txt, no SECURITY.md and no documented error responses

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Pass `--host 127.0.0.1` to `python -m gliclass.serve`, or put the port behind your own gateway. The server checks no credential
- On a machine without a GPU add `--device cpu --dtype float32 --num-gpus-per-replica 0`. The default configuration expects CUDA
- Send one text a request to `POST /gliclass`. An array in `texts` is cut to its first item without an error
- Set `multi_label` to false for one label from a set. The default scores each label independently, so scores do not sum to 1
- Keep text plus labels under the pipeline's 1,024-token `max_length`, or use `ZeroShotClassificationWithChunkingPipeline`. Longer input is truncated silently

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.