Published-wheel evidence, not a compatibility checker.

A browser/runtime-constrained batch utility for current, provider-reported wheel metadata.

Use the endpoint

• GET /api/yumi/wheel-evidence returns the service descriptor.
• GET /api/yumi/wheel-evidence?request=... accepts one URL-encoded JSON request. GET is also subject to host URL limits; use POST for larger requests within the documented body limit.
• POST /api/yumi/wheel-evidence accepts an application/json request body.

One browser batch request can collect current facts for up to eight explicit releases instead of manually opening multiple release pages. Direct PyPI JSON and Python packaging are preferred for a small or native workflow.

Dedicated MCP endpoint

Use the dedicated endpoint at https://noqt.no-qt.chatgpt.site/api/yumi/mcp for stateless JSON-RPC POST requests. It supports initialize and tools/list, and exposes exactly one tool, pypi_wheel_evidence, with the same releases and tags arguments described below.

Requests are anonymous and require no account. The Origin header may be absent or exactly https://noqt.no-qt.chatgpt.site; each UTF-8 request body is limited to 65,536 bytes including the complete JSON-RPC envelope. There is no session or SSE transport. Results retain the provider-reported filename/tag intersection limitations and do not verify compatibility, security, or digest data.

Request shape and limits

The top-level request has exactly two keys: releases and tags. The releases array contains one to eight objects, each with exactly project and version. The tags array is global to the request and contains one to 256 tags.

Project names are one to 128 characters and use a conservative safe grammar with normalization. Versions are one to 64 characters and must match /^[A-Za-z0-9][A-Za-z0-9.!+_-]*$/. Version matching is literal provider equality; the service does not perform full PEP 440 alias resolution.

Each global tag is one to 128 characters and must be canonical and uncompressed. The decoded GET request and streamed POST body are capped at 65,536 UTF-8 bytes.

What the response means

Matching output is selected by filename in lexicographic order and is bounded at 50 matches per item. The exact matching total remains available, together with whether the output was truncated.

Evidence is based on filename tag intersection and provider-reported release metadata. A NO_MATCHING_WHEEL result means no wheel in the returned provider metadata intersects the supplied tags; it does not mean that the package is incompatible.

Provider-reported SHA-256 is not an artifact verification performed by this service. The service does not assess compatibility, installability, security, origin, artifact availability, or dependency resolution.

Source and scope

The fact source is release-specific PyPI JSON. The service never downloads wheel or artifact files, retries upstream requests, or follows redirects. Upstream errors remain explicit per-item results, rather than being converted into false no-match results.

Current facts can change. Strict literal versions may reject or flag aliases. Submit public non-secret requests. No account or authentication is required. The application does not persist or log requests, add tracking, call a model, or expose Yumi's private assistant, core, or memory, although the hosting provider may process request metadata.

This is not a novel matcher and makes no superiority, adoption, or AGI claim.

Compact request example

{
  "releases": [
    {
      "project": "example-project",
      "version": "1.2.3"
    }
  ],
  "tags": [
    "cp311-cp311-manylinux_2_17_x86_64"
  ]
}