Appearance
Getting started
Mystro is live with invite-led developer access. Bring one customer workflow and the product you want to connect.
1. Request developer access
Describe your product, the task agents should perform, the data they need, and any privacy requirements. Access and integration details are confirmed with the Mystro team; this guide does not promise immediate provisioning or self-service signup.
2. Confirm your route and boundaries
Agree on a supported model route and whether it provides TEE execution and E2EE for your use case. Identify where encryption starts and ends, what leaves inference through tools, and which storage or retention requirements must be confirmed. Read model routes and data boundaries.
3. Define one customer workspace
Map the customer, authorized users, allowed data, and tool permissions before connecting your UI. Keep authentication and business authorization in your product. Use the environment details supplied during onboarding; do not substitute the legacy reference's .invalid origins.
4. Validate one bounded workflow
Start with non-sensitive sample data. Read a support request, generate a draft, require owner approval, and record only the approved result. Confirm denial, failure, and uncertain outcomes before expanding access. Follow the support workflow.
The legacy first-run walkthrough remains available as a proposed contract example. Its endpoints, keys, and provisioning sequence are not live onboarding instructions.