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 a workspace owner has approved the feature scope, credential owner, and launch path. 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.
Choose An Entry Point
Build Options
Choose a new starter, supported existing-project setup, manual SDK wiring, or direct HTTP.
Authentication & Keys
Confirm key type, allowed origin, credential owner, and server boundary.
SDK
Build application runtimes with typed workspace reads, writes, and workflows.
CLI
Give shell-capable coding agents a machine-stable discovery and execution surface.
API
Use OpenAPI and direct HTTP when the SDK does not fit the runtime.
MCP
Give hosted, shell-less clients read-only workspace discovery.
Webhooks
Receive events after an owner, retry path, and observability plan are assigned.
Handoff Order
- Confirm enabled features in Feature Planning.
- Confirm key ownership, allowed origins, webhook ownership, and AI-agent scope in Integrations & Keys.
- Confirm launch criteria in Launch Readiness.
- Choose a project path in Build Options, then select the surface below at a routing level.
- Return to Launch Readiness before production exposure.
Surface Selection
| Need | Route to | Keep out of this page |
|---|---|---|
| browser reads or product UI | SDK after Publishable Key and allowed origins are approved | SDK import tables or generated type details |
| privileged server work | server-side SDK, or API when the SDK does not fit | endpoint-by-endpoint reference claims |
| shell-capable coding agent | CLI after scope and credentials are approved | interactive login or unstable text parsing in automation |
| hosted or shell-less AI client | MCP for three read-only discovery tools | collection CRUD or commerce workflows through MCP |
| event processing | webhooks after owner, retry, and observability responsibilities are assigned | provider-specific delivery guarantees not verified here |
Do not implement against a workspace before the workspace owner approves scope, credential ownership, and launch readiness criteria.
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.