Skip to content
Draft

Full Stack VPS

A VPS that provisions with its own scoped API key, ready for your code, the CLI and AI agents.

A Full Stack VPS is a standard Xuda-hosted server preloaded with the xuda-cli, codex, and its own auto-issued, scoped API key, so the box itself, your code running on it, the CLI, or an AI agent, can call back into the Xuda ecosystem the moment it boots. Provisioning runs from the dashboard: deploy_full_stack_vps is a session-only method. What that provisioning call hands you is the interesting part for this page.

What provisioning issues

A scoped key is minted

The box's own API key is created before provisioning, scoped by the full_stack_tools capability groups chosen at create time, file access, SSH access, firewall rules, domain connection and more, each group expands to a set of the same platform methods documented across this API section.

The key and endpoint are stamped on the app

full_stack_vps.api_key_id, full_stack_vps.tools and full_stack_vps.mcp_url land on the app document, so the box's own tooling can read them at boot without a person copying a key by hand.

The box connects itself

Cloud-init writes the key into /root/xuda.config.js and /etc/profile.d/xuda.sh, so a shell on the box, the CLI, or codex already has XUDA_API_KEY and XUDA_AGENT_KEY in its environment.

Capabilities are set at create time

The tool groups a box's key carries are set when the box is provisioned, so choose the groups it needs at that point.

What the box's key can call

The methods a Full Stack VPS key reaches are the same file, SSH and firewall surface documented on External VPS: vps_fs_list, vps_fs_read, vps_fs_write and the rest of the vps_fs_* family, vps_enable_ssh / vps_rotate_ssh_token / vps_disable_ssh, agent_firewall_list / _open / _close, agent_domain_list / agent_domain_connect, plus get_platform_regions, get_account_vps, get_deploy_info and get_app_server_usage for reading the box's own state.

curl -s https://xuda.ai/cpi/vps_fs_list \
  -H 'content-type: application/json' \
  -d '{"api_key":"YOUR_BOX_API_KEY","path":"/var/www"}'
const res = await fetch('https://xuda.ai/cpi/vps_fs_list', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({ api_key: 'YOUR_BOX_API_KEY', path: '/var/www' }),
});
const { code, data } = await res.json();
import requests

res = requests.post(
    'https://xuda.ai/cpi/vps_fs_list',
    json={'api_key': 'YOUR_BOX_API_KEY', 'path': '/var/www'},
)

Over MCP

full_stack_vps.mcp_url points at the same MCP endpoint every key uses. A box whose key carries the full_stack_vps scope also gets any installed plugin tools from the box's own app exposed alongside the ecosystem methods, so an agent connected to the box reaches both in one session.

Methods

The same full app_module table External VPS and Development Platform link. A box's own key only reaches the file, SSH, firewall and domain rows named above, not every row this table lists.