Docs
Test any AI, prove the result
VVDex connects to any model or AI app, puts it through Forge exams or your own tests, and seals every run in a signed receipt. Pick where you want to start.
vvdex command.
GitHub ActionFail a pull request when a model drops below your bar.
MCP serverGive an MCP client tools to list models and run tests.
API schemaThe OpenAPI schema of every public endpoint, generated from the server. Load it into any OpenAPI tool.
How the proof works
Words used everywhere
- Workspace
Everything you make belongs to a workspace: connections, datasets, runs, keys. Nobody outside it can see them unless you share a link.
- Connection
How VVDex reaches a model: a provider and your key, an OpenAI-compatible address, or an HTTP app. Keys are encrypted and never shown again.
- Model reference
{"connection_id": "…", "model": "…"}in the API,CONNECTION:MODELin the CLI.- Run
One evaluation: a source (a Forge exam or your dataset), one or more models, and for a dataset its graders and optional repeats.
- Receipt
The signed record of a run. Anyone can check it at /check-receipt.
- API key
Starts with
vvx_. Create one in the web app under Settings → API keys; it is shown once.