Skip to main content
Agent Builder has three operations, each with one public HTTP endpoint. Build tests validate definitions; they do not verify provider execution or generated UI. Supply your component-library package, or use DarwinUI by default. Package registration and runtime execution retain their own validation boundaries. Every operation checks identity, resource ownership, and scopes. Mutations require an idempotency key; updates and releases bind the expected revision. Publishing never grants access to user accounts or authorizes spending. Advertising submission requests review and does not activate paid delivery. These are HTTP operations. Agent Builder MCP tools are not implemented yet. Legacy owner API routes remain compatible for existing clients.
Last modified on November 7, 2026