Skip to main content
Yanked

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

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.

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.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for modelspec-dev 0.1.1
File Size Uploaded
modelspec_dev-0.1.1.tar.gz 63.5 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for modelspec-dev 0.1.1
File Interpreter ABI Platform
modelspec_dev-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 63.8 MB

Release files / modelspec_dev-0.1.1.tar.gz

Download URL modelspec_dev-0.1.1.tar.gz
Size 63.5 MB
Tags Source
SHA-256 checksum
How to use checksums
86fe3adc357de69dc29cddc66cdf6733b0fca215944269bf96aaeccc264a6758
BLAKE2b-256 checksum
How to use checksums
bd01935f968012919d5ffde22a262e4bb50df5d75a1aa38ac0cf1d5651557bd9
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

Release files / modelspec_dev-0.1.1-py3-none-any.whl

Download URL modelspec_dev-0.1.1-py3-none-any.whl
Size 318.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
89a70736354b6b863c6650eae3933eb7a37eec04b17cd7dc20e691f7243529b8
BLAKE2b-256 checksum
How to use checksums
381ebb02b53f54160d48161a1c038c36da653672fc6b924daf675422c7794ad8
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

Release history Release notifications | RSS feed

1.0.0

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.0

2 release files

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page