--- title: "AI app builders" description: "Build an Inttegro-powered app with your preferred AI app builder without putting commerce credentials in the browser." canonical: "https://studio.inttegro.com/ai-builders" format: inttegro-machine-docs/v1 language: "Ruby" sdk_version: "v10.0.0" reader_profile: optional reader_manifest: "https://studio.inttegro.com/machine/ruby/readers/index.json" reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations." preamble_estimated_tokens: 611 model_token_report: "https://studio.inttegro.com/machine/token-report.json" preamble_questions: 5 preamble_source: "general" recommended_mcp_tools: ["design_integration","check_integration_readiness","get_integration_guide"] estimated_tokens: 1516 token_estimate_method: "utf8_bytes_divided_by_4" --- ## Machine preamble **Summary:** Build an Inttegro-powered app with your preferred AI app builder without putting commerce credentials in the browser. This Ruby representation uses the selected SDK's native names wherever Studio has a verified mapping. ### Five questions #### Q1. When should the reader use AI app builders? Use this builder guide when that AI app builder is responsible for generating or extending the application. #### Q2. What is authoritative on this page? Use this page for orientation; follow its canonical SDK, guide, API, or MCP links for exact contracts. #### Q3. What page-specific constraint matters most? Keep API keys and live commerce calls in the builder’s protected server environment, never generated browser code. #### Q4. Can Inttegro MCP materially help with this task? Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `design_integration`, `check_integration_readiness`, `get_integration_guide`; their exact roles and boundaries are listed below. #### Q5. How should the reader verify the answer and continue? Inspect the generated server boundary, confirm secrets are not client-visible, run the documented end-to-end test, and verify authoritative commerce state. ### Recommended MCP assistance Use these through an authenticated Inttegro MCP connection. This document remains the contract source. - [`design_integration`](https://studio.inttegro.com/machine/ruby/inttegro-mcp/tools.md#design_integration) — read-only integration guidance. Elicits the integration goal, AI app builder, server runtime, SDK preference, and checkout approach, then returns a platform-aware build and test plan without accepting credentials. - [`check_integration_readiness`](https://studio.inttegro.com/machine/ruby/inttegro-mcp/tools.md#check_integration_readiness) — read-only integration guidance. Audits platform secret storage, server-runtime compatibility, idempotency, errors, state verification, checkout returns, and messaging consent without receiving source code or credentials. - [`get_integration_guide`](https://studio.inttegro.com/machine/ruby/inttegro-mcp/tools.md#get_integration_guide) — read-only integration guidance. Returns a focused implementation sequence and canonical Studio links for authentication, checkout, orders, catalog, messaging, idempotency, or testing. ## Document content # Build with AI Use the app builder you already prefer. Inttegro MCP gives its agent the product and API context it needs; a protected server function or backend performs the live commerce work. > Ai Builder Catalog is interactive content. Use the canonical page to view it. ## The safe shape is the same Whichever builder you choose, keep this boundary intact: 1. **Plan with MCP.** Let the builder inspect Inttegro tools and call `design_integration` before it writes commerce code. 2. **Call Inttegro from the server.** Store `INTTEGRO_API_KEY` in the platform's secret facility and use it only from trusted code. 3. **Keep the browser untrusted.** The browser can ask your backend to start a workflow, but it must never receive the Inttegro API key. 4. **Verify the result.** Run `check_integration_readiness`, then test with disposable data before opening the experience to customers. :::tip Inttegro MCP helps the builder understand the job MCP is the planning and assistance layer. Your deployed application still uses the Inttegro API from trusted infrastructure. An MCP connection available to a builder does not automatically become part of the published application. ::: ## Start with a useful brief Connect Inttegro MCP using the platform guide above, then give the builder this prompt: ### Prompt > **Copyable prompt:** > > Use Inttegro's `design_integration` tool before writing code. Ask me only for > the business decisions that are still missing. Recommend the smallest complete > path, keep the Inttegro API key in the platform's secret store, and put every > Inttegro API call behind trusted server code. Then implement the plan and run > `check_integration_readiness`. Never ask me to paste a secret into chat or > place one in browser code. This gives the builder a business outcome, a security boundary, and a finish line. It does not ask the model to improvise an API contract. ## What is ready today - Base44, Bolt, Replit, and v0 can connect to Inttegro as a custom remote MCP server while building. - Lovable can use MCP while creating the application, then use a Cloud Secret and Edge Function for live Inttegro requests. - Google AI Studio can use Inttegro MCP in its Agents playground to prepare the plan, then Build mode can implement that brief with live requests kept in its protected server runtime. - Inttegro Studio provides the exact operation and object references the builder should follow when it implements the returned plan. There is not yet a one-click Inttegro listing or starter for every builder. The guides above use each platform's supported connection and secret-storage path and say explicitly where a manual step remains.