Quick Start

Use this path when a human buyer has finished checkout and wants a coding agent to start the integration.

What you need

• API key from the MaaS success page
• Base URL: https://maas.nunchiai.com/v1
• X-Workspace-Id for the target environment
• A service_source chosen during checkout

Step 1. Create the checkout session

curl -X POST https://maas.nunchiai.com/api/v1/billing/maas/checkout-session \
  -H 'Content-Type: application/json' \
  -d '{
    "company_name": "Acme Studio",
    "admin_email": "[email protected]",
    "pricing_model": "enterprise_usage",
    "service_source": "enterprise-tutor"
  }'

{
  "checkout_session_id": "cs_test_123",
  "url": "https://checkout.stripe.com/c/pay/cs_test_123",
  "success_url": "https://maas.nunchiai.com/billing/maas/success?checkout_session_id={CHECKOUT_SESSION_ID}",
  "cancel_url": "https://maas.nunchiai.com/billing/maas/cancel",
  "service_source": "enterprise-tutor",
  "pricing_model": "enterprise_usage",
  "contract_version": "2026-03-01"
}

Errors

• 400 Bad Request — company_name, admin_email, pricing_model, or service_source is invalid.
• 402 Payment Required — billing is paused for the hosted service.
• 500 Internal Server Error — Stripe price configuration is missing.

Step 2. Complete checkout and open the success page

The buyer completes Stripe checkout and returns to:

https://maas.nunchiai.com/billing/maas/success?checkout_session_id=cs_test_123

The success page provisions the tenant automatically and shows:

• organization slug
• service source label
• workspace id
• first API key
• AHOP handoff block

Step 3. Make the first runtime call

Use the issued key and workspace id immediately.

curl -X POST https://maas.nunchiai.com/v1/memory/recall \
  -H "Authorization: Bearer mk_maas_example" \
  -H "X-Workspace-Id: acme-prod" \
  -H 'Content-Type: application/json' \
  -d '{
    "anchor_id": "smoke-test",
    "query": "hello"
  }'

{
  "items": [],
  "session_id": "c67d4f42-0b6d-4f94-beb8-22eb24a8a6df",
  "service_source": "enterprise-tutor",
  "workspace_id": "acme-prod"
}

Errors

• 400 Bad Request — API key is invalid or X-Workspace-Id is missing.
• 402 Payment Required — billing account is blocked.
• 403 Forbidden — access policy denies this workspace/key combination.
• 429 Too Many Requests — retry with backoff.

What to do next

• Read API Reference for the full surface.
• Read Character Chat if the buyer chose enterprise-tutor.
• Read Editorial / Content if the buyer chose maas-enterprise.