Simulator
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. Simulator behavior applies to operator users with metadata.simulator = true while normal staging users continue through the real wallet adapter path.
Simulator page
The Simulator page launches existing simulator users into the Mini App.
Operators can:
- pick a simulator user
- inspect that user's balance and locale
- mint a launch URL when the session has
launch:write - open the launch URL for manual trade or redemption 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
Safe usage rules
- use staging-only users and external IDs
- keep simulator metadata on dedicated users only
- do not treat simulator success as proof of real wallet readiness
- run wallet adapter contract tests separately before production
Source API
Simulator dashboard pages use the endpoints listed in /docs/operator-api/simulator.
