01.software Docs

Implementation Handoff

Choose SDK for application code, CLI for shell-capable agents, and narrower surfaces only when those defaults do not fit.

Implementation Handoff

Use this page after Quickstart or when you need a narrower implementation surface. Application runtimes should start with the SDK. Shell-capable coding agents should start with the Agent CLI. Use direct HTTP as an escape hatch and hosted MCP only for shell-less discovery. Credential, browser-origin, and launch checks remain required when your work reaches those boundaries; they are not a separate general approval path before the first call.

Choose An Entry Point

Implementation order

  1. Choose a new or existing app route in Build Options.
  2. Start product code with SDK; use API only when the SDK does not fit.
  3. Open Authentication & Keys and Integrations & Keys before handling credentials, browser origins, webhooks, or AI-agent access.
  4. Confirm enabled features in Feature Planning when your domain needs them.
  5. Return to Launch Readiness before production exposure.

Surface Selection

Use the domain SDK references for Customers, Ecommerce, Events, and Community; use the specialist integrations for Payments, Membership, Embedded Admin, and External Effects.

Do not put secret keys in browser code. Register a browser origin before a browser call, and complete launch readiness before production exposure.

Next Actions

  • New integration: open Authentication & Keys.
  • New or existing application project: choose Build Options.
  • App or product surface: start with SDK; use API when the SDK does not fit.
  • Shell-capable coding agent: open CLI.
  • Hosted, shell-less client: open MCP for read-only discovery.

On this page