Teams

Share gateway memory and pool credits with your team: roles, per-member sharing controls and how the credit pool is calculated.

Last updated Sep 12, 2026

A team gives several people one shared context: agents that remember together and, if you want, a shared credit budget. You create a team under Team and invite members by mail. Roles are owner, admin and member; owners and admins manage members and the team switches.

Shared memory#

Team memory is deliberately conservative. Three switches have to line up before anything is shared:

1. The team has memory sharing switched on at all.
2. Your membership allows it, separately for reading team facts and writing them.
3. The agent marks the individual fact with share_with_team: true in tulimoa__remember.

So nothing you or your agent stores privately ever reaches the team by accident. Shared facts show up in tulimoa__recall for every member whose membership allows reading.

Credit pooling#

Optionally, a team can pool credits. The pool is the sum of the monthly credit limits of every member who contributes, and it only forms when the team has pooling switched on and the member has opted in to contribute. Calls made by team agents draw from the pool and are blocked at the pool, not at any personal limit; personal credit balances stay untouched. The pool resets monthly, and the team page shows the shared meter.

Team agents#

An agent runs for the team when its API key is assigned to the team. Team agents are listed on the team page, and with pooling enabled their calls bill against the shared pool.