Skip to main content
This project lives at examples/projects/investor-booking-web. It gives you a practical ingress harness:
  • browser UI for message testing
  • local proxy that keeps runtime key server-side
  • event forwarding to app runtime ingress
  • diagnostics panel for payloads, IDs, and timing

​
Architecture

Browser (index.html) -> Local proxy (server.py) -> Ara API (/v1/apps/.../events) -> App runtime

​
1) Deploy the app first

From examples/python-sdk: 
./ara deploy meeting_swarm_subagent_modal_minimal.py --warm true
This writes the runtime key to examples/python-sdk/.runtime-key.local.

​
2) Start the web proxy

From examples/projects/investor-booking-web: 
python3 server.py \
  --api-base http://127.0.0.1:4000 \
  --project-name investor-meeting-booking \
  --runtime-key-file ../../python-sdk/.runtime-key.local \
  --port 8787
Open http://127.0.0.1:8787.

​
3) Validate with scenario flow

Run these chat prompts:
  1. Need 3 slots next week for Alex VC.
  2. Let's narrow to Tue/Wed mornings only.
  3. Please send a follow-up nudge if not confirmed.
Expected technical behavior:
  • each request returns HTTP 200
  • response includes ok: true
  • response includes workflow_id and event_id
  • diagnostics panel shows request/response JSON and event metadata

​
Notes

  • The proxy keeps ak_app_* out of frontend code.
  • Use this project as a reusable integration harness for any inbound-event app.
  • For SDK command and decorator details, see /sdk/reference.