Teams & Projects

Share a Project

The console manages Environments, Runs, models, usage, billing, API keys, Teams, and Projects. Environment details open on a Work view for selecting Sessions and submitting tasks; Configuration contains Skills, schedules, MCP, inbound webhooks, agents.md, workspace state and deletion. Run details open on readable execution activity, with separate Result, Files, Costs and raw Events views. Personal resources remain separate from Team Projects. A Team owner adds existing Sandpi users as admins or members. Admins manage members, Team Sandbox budgets, and Project keys; members use shared Environments and Runs. The Team owner's prepaid wallet funds Project Sandbox runtime. A personal key cannot access a Project, and each Project key has one immutable Project scope. Membership changes do not automatically revoke issued Project keys.

A Team can set a monthly Sandbox budget across all its Projects. Each Session can also set a lifetime execution allowance expressed in USD. Environment runtime is charged once; Session allowance consumption does not create another charge. Existing Project Sandbox limits migrate to their Team's aggregate limit. See Sandbox budgets.

Choose the correct key

Use a Project key in your server-side integration. Its scope is attached to the key, so requests use the same API paths as personal requests. Create the Environment with that key and use it for its Sessions, Runs, schedules and webhook definitions. A personal key cannot access those resources.

Remove access

Removing a Team member does not revoke previously issued Project keys. Revoke keys separately in the console, then update integrations that still need access.

See authentication and billing and budgets.