Guide

Flagship flow demos

These demos turn Atlas mechanics into business value: safe recovery, approval-guarded booking, and cited customer answers. Use them in sandbox before making production claims.

Abandoned order recovery

Recover an abandoned order without inventing discounts or bypassing approval policy.

Claim status: Staging sandbox mechanics proven; production flow staged.

curl -X POST "$ATLAS_API_BASE/atlas/v1/mcp" \
  -H "authorization: Bearer $ATLAS_TOKEN" \
  -H "content-type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "abandoned-order-recovery",
    "method": "tools/call",
    "params": {
      "name": "search_knowledge",
      "execution_mode": "commit",
      "idempotency_key": "abandoned-order-recovery-1",
      "arguments": {
        "query": "How should Atlas recover an abandoned order without inventing discounts?",
        "top_k": 3
      }
    }
  }'
  • sufficient knowledge state
  • abandoned order citation
  • approval before incentives
  • outbox-safe message

Booking or rescheduling with approval

Coordinate booking changes while preventing false customer confirmations.

Claim status: Approval mechanics proven in staging sandbox; production booking breadth staged.

curl -X POST "$ATLAS_API_BASE/atlas/v1/mcp" \
  -H "authorization: Bearer $ATLAS_TOKEN" \
  -H "content-type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "booking-reschedule-with-approval",
    "method": "tools/call",
    "params": {
      "name": "search_knowledge",
      "execution_mode": "commit",
      "idempotency_key": "booking-reschedule-with-approval-1",
      "arguments": {
        "query": "When should a booking or reschedule require approval?",
        "top_k": 3
      }
    }
  }'
  • approval policy citation
  • pending approval state
  • approval_request_id
  • no customer confirmation before approval

Customer Q&A with evidence and handoff

Answer only from cited knowledge and hand off when evidence is weak.

Claim status: Canonical sandbox corpus proven; broad production corpus staged.

curl -X POST "$ATLAS_API_BASE/atlas/v1/mcp" \
  -H "authorization: Bearer $ATLAS_TOKEN" \
  -H "content-type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "customer-qa-evidence-handoff",
    "method": "tools/call",
    "params": {
      "name": "search_knowledge",
      "execution_mode": "commit",
      "idempotency_key": "customer-qa-evidence-handoff-1",
      "arguments": {
        "query": "What are the sandbox cafe opening hours, menu, and prices?",
        "top_k": 3
      }
    }
  }'
  • sufficient knowledge state
  • source_url citation
  • answer from cited facts
  • handoff on gap_weak

Run the full gate

The Atlas E2E suite includes these flows plus auth, MCP discovery, dry-run, approvals, idempotency, webhooks, error recovery, tenant invariants, and canonical RAG queries.

Flow designDebugging