Open data

• Page updated 2026-10-22

The numbers behind the RigCheck checkers are published as JSON files that anyone may reuse, including in commercial products, with credit to RigCheck.

01Files

• models.json: the file sizes and memory figures each checker works from (such as file sizes as Hugging Face lists them, KV cache at 32K context, or a publisher's memory table), with each page's update and sources-checked dates.
• strata.json: the Strata engine's size options, memory needs and benchmarks, each benchmark with its source and its type (measured, community report or estimate).
• hardware.json: the graphics cards and Macs the checkers offer, with label, vendor, memory and, where a source is recorded, memory bandwidth.
• lab.json: RigCheck Lab's own measurements, one record per run: the file and its checksum, the host, the llama.cpp build, the exact command, each speed sample, peak GPU memory, the outcome (failures included) and the record's correction history (see the method).
• catalog.json: the model catalog, with each model page, its variants, input and output types and which checkers answer for it.
• /data/fit/<model>.json: each model page's "Common setups" table, with the checker's quick answer on eight fixed setups, in the checker's own words, with its conditions. One file per model page:

• deepseek-v4-1-flash.json: DeepSeek V4.1 Flash
• flux-3-image-klein.json: FLUX 3 Image Klein
• gemma-4.json: Gemma 4
• glm-5-3-flash.json: GLM-5.3-Flash
• kolibri-1.json: Kolibri-1
• minimax-h3.json: MiniMax H3
• mistral-medium-3-5.json: Mistral Medium 3.5
• nemotron-3-5.json: Nemotron 3.5
• qwen-3-8-27b.json: Qwen3.8-27B
• qwen-3-8-flash-next.json: Qwen3.8-Flash-Next
• qwen-image-2-1.json: Qwen-Image-2.1
• strata.json: Strata checker

File sizes, published benchmarks and publishers' memory tables come from the sources named on each page. The fit answers are of different kinds, which each fit file names in its answerKinds field: a RigCheck capacity estimate, a planning budget, or a match against an official route, a published route or recipe, or a project's published requirements. None of them is a tested setup; the methodology page explains each. An answer of "unknown" means there is no route or source to check, not "does not fit".

02Licence and credit

The files are licensed under the Creative Commons Attribution 4.0 International licence (CC BY 4.0). You may copy, adapt and redistribute them for any purpose, commercial use included, if you:

• credit RigCheck, localrigcheck.com,
• link the RigCheck page the number comes from (entries name it in a page or url field; for hardware.json, link this page), and
• say if you changed the data.

Example credit: Source: RigCheck (localrigcheck.com/gemma-4/), CC BY 4.0. Using the data does not imply that RigCheck endorses you or your product.

03What the licence covers

• RigCheck's own work: the compiled tables, the calculations and estimates, the fit answers and the way they are organised.
• Material from other publishers is cited, not relicensed. Model cards, runtime documentation and benchmarks published elsewhere stay with their publishers; the files record the figures RigCheck uses with a link or label naming where they come from. To reuse their documents themselves, follow their own terms.
• Only what RigCheck has rights in. The licence does not restrict uses that need no permission, such as stating a single fact or file size.
• Names of models, runtimes and hardware belong to their owners. The licence does not cover the RigCheck name beyond the credit line.

04Your measurements

Measurements sent to RigCheck are published only after they are checked against the log, labeled as community reports, and only if the sender agrees that they may be published under CC BY 4.0, commercial reuse included. A report sent without that agreement is not published. The measurement form asks for the agreement before it accepts a report (failed attempts included), and the e-mail template linked from each model page includes it too.

05GitHub mirror

The same files are copied to the public repository github.com/Qtguns/rigcheck-data after a site update changes them; a rebuild that only changes a file's generated date is not copied. From 21 October 2026, each copy is a commit, so you can pin a version or see what changed. A copy can lag behind the site for a few days, and if a copy fails and the data changes again before the next one, the version in between is not kept. The live files on this site are the reference. Corrections go to hello@localrigcheck.com, as the About page describes.

06Changes and limits

• The files change when a page's data changes. Per-model entries carry the page's update date, the site's feed lists page updates, and the GitHub mirror's history shows the changes it has copied, field changes included.
• The files can be fetched from any website (CORS is open) without a key. There is no uptime or rate guarantee; please cache them rather than fetching them on every page view.
• The data comes with no warranty. Check the page and its sources before you buy hardware based on a number.