Development Platform
Create a project, author its Studio programs, read and write its tables, ship a release.
This is the widest API surface Xuda publishes, 71 methods across three microservices, and it is what lets an external tool, your own backend, or an AI agent over MCP do the same work a person does in Studio: create a project, author its programs, read and write its tables, check a build and ship a numbered release.
Authoring a Studio program
The four methods behind Studio's own editor are exactly the ones an API caller uses, so a node created over the API is identical to one created by hand.
Create the project
create_project starts a new app from just a name.
Create a node
create_prog makes a new studio node from a menu_type of twelve: table, component,
folder, globals, get_data, set_data, batch, alert, javascript, route, api or
ai_agent, using the same factory Studio itself uses.
Validate before you save
validate_prog runs Xuda's own checker, structure, cross-references, workflow actions,
expressions, plus a landmine scan for AI-typical mistakes (a stray quote inside xu-script, an
xu-on: handler that is not an array). It writes nothing, so call it as often as you like.
Save
save_prog recompiles and persists the node. get_prog reads one back, including the _rev a
following save_prog needs.
get_studio_guide returns the authoring guide by topic, and get_prog_examples searches worked
examples by pattern or node type. An AI agent authoring over MCP calls these first, the same guide
text ships as the MCP server's own instructions.
Reading and writing table data
dbs_read, dbs_create, dbs_update, dbs_delete and dbs_restore operate on a table's rows by
its table_id (the table node's own _id, never its display name), and get_table_counts reads
active and archived row counts. These are the same four methods a javascript or api program
calls at runtime through xu.dbs_read(...), see Xuda JavaScript Framework
for that angle on the same methods.
Building and releasing
build_app checks and compiles a numbered version (developer clearance), get_app_releases
lists past releases, and get_release_note_info and delete_release round out the release
lifecycle.
Project and app operations
Beyond authoring, get_app_info, get_app_config, turn_app_on / turn_app_off,
update_domain_setup, save_deploy_settings and the app-visibility and branding toggles cover a
project's own lifecycle. The VPS file and SSH families (vps_fs_*, vps_ssh_*) live on this same
microservice, see External VPS and Full Stack VPS for
that side of it.