Resource model

Every environment resource lives under /v1/tenants/{tenant_id}/environments/{environment}. The environment is sandbox or production. IDs are opaque: never derive storage paths, identities, or permissions from their format.

Resource	Purpose and boundary
Tenant	The paying B2B organization
Environment	Independent sandbox or production execution and data
User	An opaque mapping of your app's external user ID within one environment
Service actor	A backend identity, stable across key rotation
Workspace	Exactly one owner actor; one workspace per actor/environment in the pilot
Agent / revision	Mutable agent identity and immutable instructions, model, tool references, limits
Conversation	Workspace-owned history pinned to an agent revision
Run	Immutable work input and authorization snapshot, with durable events
Connection / tool	An owner-bound reviewed HTTPS integration and immutable operation definition
Approval	One exact proposed operation, input hash, actor, run, tool revision, and connector generation
File	Quarantined input or artifact with authenticated access
Usage record	Immutable measured costs, rated charges, or explicit adjustments

What you build

Your app owns branding, sign-in, membership, domain data, business permissions, and approval UI. Its endpoint must enforce live business rules before a tool writes. Financial transaction execution stays in your app, outside the pilot tool catalog.

What you configure

Configure agent instructions and model profile, reviewed HTTPS tools, per-run limits, budgets, retention, and webhook destinations. Mystro owns execution containment, durable runs, tool dispatch enforcement, events, file boundaries, and metering.

The pilot intentionally has no arbitrary shell, customer code, unrestricted MCP servers, or plugin marketplace. Scheduled jobs, managed Google Drive OAuth, and explicit agent-scoped memory are future features. Existing Mystro-powered products keep their current integrations during the transition.