Funding-file chaos in. Review-ready structure out.View actionsPrivacy rulesTest console
Safe verification

Test the Workflow Without Testing Your Privacy Luck

Start with fictional metadata, verify the success contract, then run controlled negative tests using test-only values.

Use fictional metadata first.

!
Never test with a real credentialUse fictional names and test-only values for privacy-risk scenarios.

Expected success

  • HTTP 200
  • ok: true
  • Action echoed
  • Request ID echoed
  • Human review required

Expected errors

  • Unknown action → 400
  • Privacy risk → 400
  • Unsupported method → 405
  • Oversized JSON → 413

Recommended first test

{
  "action": "generate_folder_structure",
  "payload": {
    "business_name": "Ridgeway Electric LLC",
    "business_type": "contractor",
    "user_role": "business_owner",
    "funding_purpose": "equipment"
  },
  "request_id": "first-production-test-001"
}

Open the test console →

Local testing reality

python -m http.server serves the static site but not the Vercel function. Use a deployed endpoint or run Vercel locally.

Static preview

cd site
python -m http.server 8080