Use the registry as data.

Static, cacheable JSON for 700 verified model records plus evidence history, compatibility relationships and benchmark results. The same data is exposed to AI agents through the public MCP endpoint.

Evidence statusSource-first verified

Field evidence checked2026-10-02

Full field verification2026-10-02

Source policy →Methodology →

/api/v1/meta.json

Registry metadata, count, schema and freshness.

/api/v1/models.json

Compact machine-readable model index.

/api/v1/models/{id}.json

Full field-verified record for one model.

/api/v1/developers.json

Developer aggregation.

/api/v1/licenses.json

License and commercial-use aggregation.

/api/v1/changes.json

Rolling release / verification change history.

/api/v1/history.json

Evidence-ledger index with snapshot/diff counts.

/api/v1/evidence/{id}.json

Observed evidence snapshots and field-level diffs for one model.

/api/v1/evidence-runs.json

Index of canonical daily evidence manifests.

/api/v1/compatibility.json

Structured model/runtime/format/precision/license/memory relationship graph.

/api/v1/benchmarks.json

Accepted reproducible deployment benchmark results.

/mcp

Stateless Streamable HTTP MCP endpoint for AI agents.

/openapi.json

OpenAPI 3.1 description of the static JSON layer.

/registry.json

Canonical full registry JSON.

Stability

/api/v1/ is the first versioned machine-readable surface. Additive fields may appear without a version bump; breaking shape changes will use a new API version.

CORS & caching

JSON API paths are configured for cross-origin read access and short public caching. The canonical registry remains available at /registry.json.

Evidence semantics

Machine-readable values preserve verification status, sources, explicit unknowns and the distinction between repository revision checks and full field verification.