Configure
Path settings
Every field under Settings → Path and what the runner does with it.
Updated
Settings → Path describes the four steps on your app. Each card saves on its own, and the signup and upgrade pages get a live check while you type.
Signup
- Signup page
- The path of your signup form, for example
/signupor/auth/signin?intent=signup. Locale-routed apps should point at the page that renders the form, not a redirect. - Method
- Password, magic link, or Google. Password means the form has a password field; magic link means submitting the email is enough.
- Welcome-email window
- How long to wait for the email before the step is uncertain. Two minutes is a good default; five if your provider queues.
Pay
- Upgrade page
- Where a fresh account starts checkout. Set it if your upgrade button is not on the dashboard or a pricing page. The runner also honours
data-mystra="upgrade": see Marking the path. - Stripe price id and plan name
- The price Mystra expects to see on Checkout. Reported on the run; a mismatch does not fail it.
- Payment proof
- One mode today: reach Checkout, never pay. See Payment proof.
Access
- Page + selector
- A path and a CSS selector that only paying accounts see, for example
/dashboardand[data-plan="pro"]. - API + field
- A JSON endpoint called with the run's session and the boolean field to read.
Cleanup
The cleanup webhook URL, so your app can delete the throwaway account after each run. See Cleanup webhook.