The Playbook - PlatformDTC

The canonical autonomous flow, expressed in dtc_* tools. Each async step is followed by dtc_job_wait.

Build the store from a brief

dtc_create_store { name:"Aurora Skincare",
                   brief:"minimalist sage skincare, 6 products",
                   idempotency_key:<uuid> }
  → { job_id:J1 }
dtc_job_wait { job_id:J1 } → { status:"succeeded", result:{ project_id:P1, preview_ready:true } }

Populate the catalog

dtc_bulk_import_products { project_id:P1, products:[…6…], idempotency_key:<uuid> } → J2
dtc_job_wait { job_id:J2 } → succeeded

Find products to add with dtc_search_catalog.

Publish to live (spend-adjacent)

dtc_publish_project { project_id:P1, idempotency_key:<uuid> } → J3
dtc_job_wait { job_id:J3 } → { result:{ production_url:"https://aurora.…" } }

Requires store:publish; may return pending_approval.

Connect ads

dtc_connect_ad_platform { platform:"meta" } → { auth_url }   # human authorizes once

Create & send a campaign (spend)

dtc_create_campaign { type:"EMAIL", name:"Launch", subject:…, email_html_content:… } → { campaign_id:C1 }
dtc_send_campaign { campaign_id:C1, idempotency_key:<uuid> }
  → { status:"queued" }                # or "pending_approval" → tell the user, wait

Monitor ROAS and decide

dtc_get_dashboard_analytics { range:"7D" } → { revenue, orders, ad_spend, roas }
dtc_get_ad_insights { range:"7D" }         → per-account spend / ROAS

Use the numbers to choose the next action (scale, pause, restock).

This is the same sequence the launch blog post walks through. Every tool here maps to a real endpoint in the API Reference.