Concepts
Workspace, twin, and route
The three objects you work with, and what a plan limits.
A workspace is the billing and people boundary. The plan limits the whole workspace, not one twin. Free is 3 twins, 30 routes, 1 seat, and 5,000 calls a month. Developer is 10 twins, 100 routes, 1 seat, and 50,000 calls. Team is 40 twins, 400 routes, 10 seats, and 200,000 calls. Enterprise is 200 twins, 2,000 routes, 50 seats, and no call cap. A yearly Developer or Team plan also has no monthly call cap.
A twin is one mock. It has a name, a slug that becomes the invoke URL, a protocol label from the preset you picked, visibility, an active scenario, and one state document. Routes belong to that twin.
A route is one stub. It matches a method and a path, optionally extra header, query, body, or path rules, and returns a status and a body. Several routes may share a path when the method or the match rules differ. The higher priority number wins. When priority ties, a route is chosen in proportion to its weight. A weight of 0 is left out of that draw while another tied route still has weight.
Roles are Owner, Editor, and Viewer. Free has one seat, so only the owner edits. Editors need a paid plan. Viewers can read the workspace and cannot change routes.