THE EXPLORER · PROFILE PUBLIC_EXPLORER · READ-ONLY
ENTER A MODEL
Most model sites let you download, run, chat. Here you enter, inspect, query, walk — because the model is the database, as an interaction, not a metaphor.
THE EXPLORER — ENTER A MODEL
psql, for a model.
Connected — vindex3-demo · compiled snapshot · 3.0-candidate / 2026-08-30
Profile: PUBLIC_EXPLORER (read-only) · the live endpoint connects quietly in the background
Type now — HELP for the grammar, Tab completes, or start with TREE layer.12;
Type from the first moment: the immutable snapshot answers instantly, and when the live endpoint wakes, a quiet ● LIVE line appears and the same grammar starts executing on a real container — the capability profile enforced in the server, after parsing, before execution. And a command need not return text: DESCRIBE a semantic address or WALK the weights and the answer arrives as a designed object — the HAUSE rendering in front, the RAW structured result one tab away, joined to the same knowledge graph Ask resolves.
The model is the database — as an interaction, not a metaphor. Read-only · rate-limited · nothing to drop.
Every interactive feature on this site demonstrates something the format itself makes possible.
ONE GRAMMAR, THREE TRANSPORTS
The terminal above is not a demo language — it is the format's query surface, and it is built to travel. The same commands will run on your machine, against a local container, through a small command-line tool that owns nothing but the format. Between the two sits a deliberately tiny protocol. Same commands, same semantics, different transport.
VINDEX3.ORG · LIVE
vindex> WALK "the capital of France" TOP 3
vindex> TREE layer.12
vindex> DESCRIBE layer.12.attention
The terminal above — a browser speaking the query surface against the hardened public endpoint: a real container, the profile enforced in the server. When the endpoint sleeps, an immutable snapshot answers instead.
THE VINDEX CLI · V0.8.0 · RELEASED
$ vindex encode hf://Qwen/Qwen3-0.6B --output qwen3-0.6b
$ vindex inspect qwen3-0.6b
$ vindex plan hf://zai-org/GLM-5.3-Flash --json
On your machine. From 0.8.0 vindex brings a model in directly from Hugging Face — headers first, then bytes over ranges, the checkpoint never landing on disk — and every reading verb (inspect, describe, representations, diff, represent, precision, verify, export) answers from the artifact alone, speaking --json. plan says what VINDEX understands about any repo from its headers, and since plan schema 4 the verdict names the commit it judged and the planner that judged it.
THE QUERY PROTOCOL · DRAFT
GET /v1/models
GET /v1/components/:address
GET …/:address/relations
GET …/:address/representations
GET …/:address/provenance
POST /v1/query
Between the two, a surface small enough to stay stable. This site is one client. The CLI is another. Any independent VINDEX3 reader could serve it.
The rule that keeps the grammar honest: if an independent implementation could support a command, it belongs. If only one engine could, it stays out.
The chapters explain what you are walking.