INTERFACE LAYER
One system.
Seven ways in.
Each surface preserves the same distinction between sourced facts, measured evidence, calculated estimates, and unknowns. Choose the interface that fits the workflow—not a different truth model.
CLI
@moemodels/cli · 0.1.0Inspect exact artifacts, calculate checkpoint residency, build validation plans, and stage evaluation evidence from the terminal.
BOUNDARYRuns from a repository checkout. It does not download weights, execute a model, or certify runtime performance.
$ npm run moemodels -- plan kimi-k3 h200 --devices 8 --json
DeployBench
@moemodels/bench · 0.1.0Send a bounded workload to an OpenAI-compatible endpoint and capture request-level TTFT, total latency, success, token usage, and throughput.
BOUNDARYA result is measured but comparison-ineligible until exact artifact, runtime, hardware, topology, repetitions, and raw evidence pass review.
$ npm run build:bench
Deployment Passport
@moemodels/bench/browser · 0.2 CONTRACTPack compatible DeployBench trials under one content digest, recompute their summaries, inspect reproducibility gates, and verify optional operator signatures.
BOUNDARYIntegrity proves that bytes match. A self-signature proves control of a key. Neither proves the declared deployment, admits a run, or makes it comparison-eligible.
$ node packages/bench/dist/cli.js verify passport.json --json
HTTP API
PUBLIC JSON · V1Query the versioned registry, calculated fit, deployment-validation plans, and evaluation evidence over public JSON routes.
BOUNDARYFit and plan outputs are deterministic calculations—not measured performance, runtime certification, or procurement advice.
$ curl https://moemodels.ai/api/v1/registry
TypeScript SDK
@moemodels/sdk · 0.1.0Use one typed, browser-safe client for registry, fit, evaluation, and planning endpoints without duplicating query serialization.
BOUNDARYThe package is not published to npm. Import it from the GitHub source workspace while its public contract is hardened.
$ npm run build:sdk
MCP server
@moemodels/mcp · 0.1.0Give compatible coding agents structured access to model search, sourced comparisons, static fit, evidence summaries, and validation-plan exports.
BOUNDARYThe local stdio server cannot run benchmarks, mutate the registry, fetch remote content, or present reported claims as measurements.
$ npm run build:mcp && node packages/mcp/dist/index.js
GitHub
MONOREPO · APACHE-2.0 CODEThe schemas, registries, calculation engine, adapters, application, packages, fixtures, and contribution checks live in one source repository.
BOUNDARYClone and build from GitHub source while packages remain unpublished. Third-party weights, datasets, benchmark content, and marks retain their own rights.