Private Builder preview. Account persistence requires the Builder migration. Tests require a configured isolated runner. Generation, managed resources, and custom-component compilation are not yet connected.
POST /api/v3/build with an action:
import_source: normalize supported JSON or Markdown source without executing it.save_draft: save the full draft withexpectedRevision(0 for a new draft). Reuse the returneddraftIdand revision for edits.get_draft,list_drafts,check_slug: inspect your private drafts or check a name. Checking does not reserve a slug.validate_draft,export_draft: check a saved definition or export it.start_test: create a test for a saved revision and operation.resume_jobruns it;get_jobreads it andcancel_jobcancels it.
builder:read; saves and test mutations require builder:write. Saves and starting tests require Idempotency-Key. Keep the key unchanged when retrying the same request. A stale revision returns a conflict instead of overwriting your work.
Tests support TypeScript without private connections, third-party dependencies, or network access in the initial isolated runner. Unsupported adapters fail explicitly. Structural validation does not prove that an operation works.
MCP exposes the same commands through build, with command and idempotencyKey. A component manifest is preserved in the draft; it is not proof that a custom component package has compiled or rendered.
Legacy agent-definition commands remain available with their existing resource scopes. Their test_agent and test_operation actions only validate definitions.
When ready, use Publish to prepare a saved revision.
Use list_templates and get_template (with slug) to start from the shared built-in definitions. Templates preserve operation metadata but do not activate missing execution adapters. Manage lists account drafts and prepares private updates.