# Reference for AI assistants

Public readable sources and the limits of what they establish.

Last reviewed: 2026-10-30

## Source priority



- Current prices and plan limits: the live /api/plans catalog.
- Feature scope: these documents and platform.json.
- A specific project’s state: the owner’s authorized panel or authenticated API response.
- Current reachability: the status page and the application’s health endpoint.

## Machine-readable versions

Every article has a Markdown URL. /docs/platform.json describes capability scope, /docs/llms.txt indexes articles, and /llms-full.txt contains all English technical articles. Content is rendered on the server and needs neither authentication nor JavaScript to read.

## API scope

The public product catalog is available at GET https://api.deployvera.com/api/plans. Hosting an API application does not grant unrestricted access to DeployVera’s management API.

Customer resources require authentication and ownership checks. Do not invent unpublished endpoints, a personal access-token flow or an MCP server. Administrator permissions differ from customer permissions.

## Keep these facts separate

Do not describe a beta feature as generally available or guaranteed. A running application does not prove it runs the newest commit or has a verified backup. Distinguish container files, persistent volumes and managed databases.

Sources: https://api.deployvera.com/api/plans · https://deployvera.com/docker · https://deployvera.com/help