Start with your application
Keep your brand, sign-in, business rules, and customer relationships. Integrate from your server using a small HTTP resource model.
Build the experience your customers know. Give it agents that can do useful work—with permissions, durable results, and costs you can inspect.
Mystro is the infrastructure underneath your product: execution, isolated workspaces, tools, events, and measured usage. Chat is a native interface. A web application, operations dashboard, or backend workflow can use the same resources.
Developer preview: this documentation describes the proposed paid-pilot contract. It is available for integration design, not production execution. Every example uses a reserved .invalid origin. Signup, provisioning, and a real API origin must be verified before a first live run.
The pilot targets product engineering teams building a bounded workflow: read a support ticket, draft a useful follow-up, ask its owner to approve, then record the note. Dedicated tenant/environment cells keep execution separate. Your application supplies the UI and decides who may access a ticket or approve its update.