Prove useful work alone or with a small group.
Create the Play once. Keep the value moving.
Capture a successful agent execution as a reusable method. Run it with fresh inputs, keep it private, or publish it for others—without turning success into a usage bill.
Create unlimited public and private Plays. Every organization starts free with up to five members. Upgrade only that organization when it needs more people, a longer deleted-Play recovery window, verified identity, or stronger governance.
Choose the control around one organization.
All plans include unlimited, versioned public and private Plays. Move up for members, a longer deleted-Play recovery window, identity, governance, and support.
One useful Play keeps paying you back.
A Play preserves the method that worked—not a larger transcript. Its value grows each time the method is recalled, shared, verified, or repaired.
Recall the craft
The same proven tool path runs again with fresh inputs, so the agent does not rediscover the method from scratch.
Transfer the work
A Play URI moves a working method to a teammate, client, or another agent without separating instructions from execution.
See what holds
Runs add evidence. Drift has an owner. A repair can update the reusable method instead of every person learning the failure alone.
More useful Plays. More proven work retained.
That is product success—not a larger invoice.
Public, private, and organizational from day one.
Visibility decides who can access a Play. Ownership decides who keeps it. Neither choice turns the Play itself into a billing meter.
Share the method.
Publish from a personal or organization namespace. Anyone can assess it, pull its URI, and build execution evidence around the exact version.
Best for distribution, reputation, reusable community work, and methods safe to disclose.Keep your own work yours.
Capture sensitive work in your personal namespace without publishing it. The private Play remains available only to you.
Best for individual experiments, personal operations, and work not ready to share.Operate as a team.
An organization owns public and private Plays. Authorized members collaborate under its roles and policy; the work remains when somebody leaves.
Every organization starts free for up to five members. Each organization chooses its own plan.Plays compound. The bill stays predictable.
The thing you want more of is deliberately not the thing we meter.
More Plays mean more expert work survives the session and reaches the next person or agent.
Your invoice changes only when that organization changes plan. Several paid organizations appear as separate, predictable subscriptions.
The recovery window describes how long a deleted Play can be restored. It is not a Play, run, or storage-usage meter.
Company-wide control, scoped around your boundary.
For Rote becoming governed infrastructure across organizations, domains, regions, or regulated environments.
SSO starts in Growth. Advanced RBAC and approvals are in Business. Enterprise begins when identity lifecycle, multi-organization control, deployment topology, or an operational promise must be designed around your company.
Begin with your namespace and first free organization.
Create public and private Plays now. Add paid control only when an organization actually needs it.