AI and developer documentation
This human-readable page is generated from the same curated source as the Markdown files listed in llms.txt.
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. This site does not verify that credential-management UI is available. Independent developer access is a future direction and is not available through this site.
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 access guidance
The approved MCP artifact is a capability and authority inventory, not a public server listing.
There is no public MCP endpoint and no public MCP registry listing. Do not construct a connection URL from the artifact name or this site's origin.
The current Accounting MCP definition declares capability-inventory-only transport, read-or-proposal-only authority, required authentication context, and explicit prohibitions.
Connection instructions can be published only after a transport endpoint, authentication flow, security review, and production acceptance are separately approved.