OpenPoly logo
Dashboard

Simulator

Use staging-only simulator launch and wallet tools.

Simulator

The dashboard exposes simulator tools only in staging or local development.

Dashboard paths

Operator Dashboard → Simulator → Simulator

Operator Dashboard → Simulator → Simulator Users

Required read scope: simulator:read

Mutation scope: simulator:write

Launch action scope: launch:write

Current simulator model

Simulator is user-scoped, not operator-wide.

The operator should keep its real integration mode, normally rest_v1, even in staging. Dedicated simulator-user APIs manage the server-side simulator classification; ordinary launch metadata cannot set or clear it. Normal staging users continue through the real wallet adapter path.

Simulator page

The Simulator page launches an existing dedicated simulator user into the real Mini App session flow.

Operators can:

  • pick a simulator user and inspect balance/locale;
  • choose opinion or enabled polyflight;
  • mint a single-use launch URL when the session has launch:write;
  • open the actual launched tab for Opinion or Polyflight UI drills.

Simulator Users page

The Simulator Users page manages staging-only users.

Operators can:

  • create simulator users with external ID, display name, email, locale, and starting balance
  • update display name, email, status, and locale
  • inspect recent sessions, trades, resolutions, balance operations, and simulator wallet operations
  • apply debit, credit, debit reversal, or credit reversal adjustments
  • inspect Polyflight purchase/ticket/payment, webhook, and wallet-operation evidence for the selected user

Safe usage rules

  • use staging-only users and external IDs
  • create and maintain simulator classification only through Simulator Users or its dedicated API; metadata.simulator sent to launch is ignored
  • do not switch the operator-wide rest_v1 adapter to simulator mode
  • exercise native Polyflight purchase, win/loss, full refund, compensation, and manual-review states through the launched client
  • do not inject cookies or substitute API-only calls for the launched-client UI workflow
  • do not treat simulator success as proof of real wallet readiness
  • run real REST v1 adapter contract tests separately against dedicated non-production infrastructure

Source API

Simulator dashboard pages use the endpoints listed in /docs/operator-api/simulator.

Copyright © 2026