This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 1.0.0 instead.
Reason given by maintainers: Retired. ModelSpec is available only as a hosted service at modelspec.dev.
ModelSpec catalogs AI models as YAML+Markdown cards, exports them to versioned JSON on Cloudflare Pages (modelspec.dev), and ranks from that export — in the browser, or offline from a local snapshot. No database is on the serving path.
- Site: modelspec.dev · graph · downselect
- CLI contract:
docs/cli-contract.md - Current state:
docs/handoff/current.md - Agent entry:
AGENTS.md
Quick start
pipx install modelspec-dev
modelspec snapshot fetch
modelspec offline rank coding --json
snapshot fetch is the only networked command. After that, rank and fit read the cache.
The supported interface is docs/cli-contract.md:
modelspec snapshot fetch [--origin URL]
modelspec snapshot status [--json]
modelspec offline rank <use-case> [...]
modelspec offline fit [<hardware-id>]
Graph commands (stats, search, info, compare, rank, hardware, …) need a local FalkorDB and are outside this contract.
Serving path
models/*.md ──▶ pipeline/build.py ──▶ static JSON on Cloudflare Pages
(modelspec.dev /api/*.json)
│
CLI `snapshot fetch` ───────────────────────┘
Wizard / 3D graph read the same JSON in the browser.
FalkorDB is optional local graph exploration only. It is not required to rank, fit, or render the sites.
Contribute
Read CONTRIBUTING.md. Sign off commits (git commit -s) to certify the DCO — not a copyright assignment. Every fact carries a source and the date it was read; unknown means an empty field.
Cards live in models/{provider}/{model-slug}.md. Edit and open a PR.
License
Two licences, because the code and the corpus want different things.
| Part | Licence |
|---|---|
| Code (everything outside the data directories) | MIT |
Data (models/, benchmarks/, hardware/, hosts/) |
CC BY-SA 4.0 |
The corpus is share-alike: build on it, including commercially, but if you redistribute it or a derivative, credit ModelSpec and publish yours under the same terms. The code is permissive so the CLI can go anywhere. Full text in LICENSE and LICENSE-DATA.
Every card and page records the sources it draws on and the date each was read. Those sources keep their own licences.
Metadata
Release files for modelspec-dev 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| modelspec_dev-0.1.0.tar.gz | 63.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| modelspec_dev-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 63.3 MB
Release files / modelspec_dev-0.1.0.tar.gz
| Download URL | modelspec_dev-0.1.0.tar.gz |
|---|---|
| Size | 63.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
817e02466d15228a9785e7f08439f17bbe7d61f8b7a5c49f4634847306a9ead4
|
|
BLAKE2b-256 checksum How to use checksums |
96eb44c82a1dbc1ecf781e5eb4d1c6227c8d8b29f3e2a7db971b9ff81e0614b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency logRelease files / modelspec_dev-0.1.0-py3-none-any.whl
| Download URL | modelspec_dev-0.1.0-py3-none-any.whl |
|---|---|
| Size | 305.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a92b955193edc4452a7997b9dbd8df15920ba88b631911f26a65ce867ad34bf
|
|
BLAKE2b-256 checksum How to use checksums |
a819883d9e56044d5f61bfb3962dd7a0bc38da047f6ac7cb1163cea79bf0d6ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency log