Private-preview micro-SaaS package API

Submit a JTBD packet

The homepage keeps the API story short. The private-preview contract accepts a structured job-to-be-done packet and returns a micro-SaaS operating package: product spec, domain model, workflows, brand positioning, competitive scan, launch plan, runtime requirements, monitoring loop, and proof package.

POST /api/agent/micro-saas-builds
Authorization: Bearer <agent_token>

request:
{
  "mode": "plan",
  "jtbd": "recover failed Stripe subscription payments for small gyms",
  "customer": "small gym owner",
  "trigger": "invoice.payment_failed webhook",
  "pain": "lost revenue and awkward manual follow-up",
  "current_alternatives": ["Stripe dunning", "Churnkey", "manual VA workflow"],
  "actors": ["gym owner", "staff", "member", "billing agent"],
  "domain_objects": ["invoice", "member", "retry", "message", "payment_link"],
  "workflow_states": ["failed", "contacted", "link_clicked", "paid", "escalated"],
  "brand_constraints": ["trustworthy", "direct", "not shaming"],
  "positioning_hypothesis": "recover revenue without awkward follow-up",
  "competitors": ["Stripe Billing", "Churnkey", "ProfitWell Retain"],
  "success_metrics": ["recovery_rate", "paid_invoices", "time_to_recovery"],
  "monitoring_events": ["email.opened", "link.clicked", "invoice.paid"]
}

Response shape

response:
{
  "app_id": "msaas_failed_payment_recovery",
  "status_url": "/api/agent/micro-saas-builds/msaas_failed_payment_recovery",
  "repo_branch": "build/failed-payment-recovery",
  "hosted_url": "pending_until_launch",
  "artifacts": [
    "product_spec",
    "domain_model",
    "workflow_map",
    "brand_package",
    "positioning",
    "competitive_analysis",
    "launch_checklist",
    "monitoring_loop",
    "agent_runbook"
  ],
  "missing_integrations": ["email provider", "custom domain"],
  "proof_package_url": "pending_until_export"
}

Builder tool calls

Private-preview agents use `submit_jtbd_packet`, `launch_micro_saas`, `get_build_status`, and `export_proof_package`. Sensitive or regulated data requires explicit retention, deletion, audit, and compliance review before ingestion.