Environments
Vision runs separate environments with separate clients, keys and data. A credential from one never works in another.
Hosts
| Environment | Vision Core (token endpoint, Platform API, MCP) | Purpose |
|---|---|---|
| Production | https://app.runonvision.com (also https://api.runonvision.com) | Real workspaces and data. |
| Staging | https://staging.runonvision.com | Release candidates. Credentials by arrangement. |
| Preview | https://preview.runonvision.com | Newest features. Where integrations are built and tested. |
Each App (CRM, To-Do, Calendar, Accounting, Directory) is its own service with its own origin, such as https://crm.runonvision.com. The Getting started by App page lists each origin and audience.
What works where
Production status on 2026-11-03, checked against the running services without credentials:
| Capability | Production | Preview |
|---|---|---|
POST /oauth/token | Live | Live |
/.well-known/jwks.json | Live | Live |
Platform API /vision-core/v1/* | Not enabled (404) | Not enabled (404) |
MCP server /mcp | Not enabled (404) | Live (Bearer token required) |
CRM API on crm.runonvision.com | Live (Bearer token required; 401 without one) | Restricted |
Other App APIs on *.runonvision.com | Restricted (403 from the internet) | Restricted |
Health /api/health/live, /api/health/ready | Live | Live |
The API availability page carries each contract's lifecycle label.
Test data
There is no sandbox tenant or test-mode key yet. Ask your Vision contact for a dedicated test workspace in the preview environment, and use a client bound to that workspace only. Never point a test suite at a production workspace.
Retired hostnames
Older documentation used vision.ivisionstudios.com and api.ivisionstudios.com with a /platform/v1 path. Those hosts do not resolve and that path does not exist. Use the hosts above and /vision-core/v1.