AI and developer documentation

This human-readable page is generated from the same curated source as the Markdown files listed in llms.txt.

• Authentication
• Approved API catalog
• Changelog
• AI-readable Markdown index

Vision developer documentation

Use approved, checksum-pinned contract snapshots to understand Vision integrations.

This public site is a development review surface, not a launch announcement. API lifecycle and runtime labels in the registry remain authoritative.

The accepted access design assigns integration credential control to tenant administrators. A workspace owner or administrator creates API clients in Vision; see https://developers.runonvision.com/authentication#get-credentials.

Start with authentication, then choose an approved App contract. Do not infer availability from documentation completeness.

Authentication and access

Vision uses narrowly scoped bearer credentials bound to audience, App entitlement, workspace, and granted scopes.

The accepted access design assigns credential control to tenant administrators. This development portal does not issue API keys, create integrations, or verify that credential-management UI is available.

Never place a service credential in browser code, public repositories, generated documentation, or AI prompts.

A documented operation can still be preview, restricted, acceptance-gated, or unavailable. Consult each App's runtime status.

MCP server

Vision runs a read-only Model Context Protocol server at the /mcp path of the preview environment host; it is not yet enabled in production.

Transport: MCP Streamable HTTP, stateless, POST only, JSON responses, protocol version 2025-11-25. Authentication: a Vision Platform access token as a Bearer credential.

tools/list returns only the tools the token scopes allow: vision.organization.get, vision.apps.list, todo.tasks.list, crm.leads.list, crm.pipeline.list, accounting.overview.get, accounting.invoices.list, accounting.payments.list, accounting.credit_notes.list and accounting.customers.list. All are read-only.

Tokens last at most five minutes. To connect Claude Code, Claude Desktop or another stdio MCP client, run the Vision MCP bridge script published under /tools on this site, which holds client credentials locally and refreshes tokens. Full instructions are on the MCP server page of this site.

The per-App MCP capability inventories on this site describe intended authority, not the tools the server exposes today.