Vinci developer documentation
Vinci names the AI research, models, technologies, and products developed by SimpleDirect®, an independent Canadian AI lab operated by Alpine Pacific Trading Inc. in Toronto, Ontario, Canada.
Start with the artifact or service you want to use. Downloadable model weights, a terminal coding agent, and a hosted API are different integration paths; a release in one does not establish availability in another.
Hosted services under maintenance. Chat, Mobile, Platform and the managed API are under maintenance. Existing service references remain available; no return date or access guarantee is implied. Model downloads and Code CLI direct/BYOK are separate.
Choose a path
| Your task | Start here |
|---|---|
| Inspect or run released model weights | Models and evidence — Vinci MLE, Vinci Cyber, model cards and model-specific licences |
| Work on a repository with a terminal agent | Vinci Code CLI — installation, provider setup and upstream documentation |
| Read methods, evaluations and negative findings | Vinci research — numbered technical reports and research records |
| Continue an existing hosted API integration | Getting started: hosted API and API reference |
| Manage an existing Platform account | Platform documentation |
Current specialist models
- Vinci MLE 1.0 focuses on ML-engineering workflows. A valid held-out MLE-task evaluation was not completed for 1.0. Read the model entry guide before selecting weights or interpreting results.
- Vinci Cyber 1.0 focuses on defensive cybersecurity. Licences and evaluation coverage differ by size; see model-specific evidence.
The canonical model catalogue owns current availability. Earlier Piccolo, Bozza and Prova work remains accessible there and in research .
Public record and support
- Getting started — choose a model, software or service path.
- Press and release records — release dates, company facts, limitations and assets.
- About SimpleDirect — history and leadership.
- Help center — user guides and support.
API and Platform reference routes remain available for existing integrations. Their service-specific authentication, billing and data handling should not be applied to locally downloaded weights or another provider’s service. For the applicable data policy, start with Privacy and the provider or runtime you choose.