Developers

A policy in. Projected effects and the reasons out.

The product is in development. This page shows the shape we are building toward, so technical teams can see how a simulation request and its report fit together.

Run a simulation

Send a policy definition and a reference to a cohort of trader twins. The response is designed to list the projected change for each behavioral signal, next to the projected change in normal trading activity, plus the reasons behind the result.

Illustrative example: these are samples that show shape and field names, not measured output.

POST /v1/simulations
Host: api.playmindlabs.com
Authorization: Bearer sk_test_••••••••••••••
Content-Type: application/json

{
  "cohort_id": "cohort_example",
  "policy": {
    "type": "cooling_off",
    "trigger": { "losses": 3, "window_minutes": 60 },
    "pause_minutes": 30
  },
  "compare_to": "no_policy"
}

Data you send

Historical session data under a data agreement. Pseudonymous: no direct identifiers; tokenized account IDs only. No names, contact details, payment data or device identifiers.

Trades
Market, side, size and time.
Deposits
Amount and time.
Withdrawals
Amount and time.
Resolutions
Outcome and P&L per position.

Policy types

The policy types we are designing for first. Each takes its own trigger and settings.

  • deposit_limit
  • cooling_off
  • position_size_cap
  • loss_limit
  • reality_check
  • session_time_reminder

Simulations are designed to be deterministic: the same data and the same policy definition give the same result, and every result comes with its reasons.

Want to shape the API with us?

Design partners help decide what the simulation report needs to show.

Become a design partner