For teams
Different agents.One team setup.
CoreSpeed gives a team one setup for every agent its people use. Share the app connections the team needs while personal ones stay private, write approval policies in plain English, and review each tool call through CoreSpeed, with its cost, in one activity trail and ledger, whether a teammate works in Claude Code, Codex or Cursor.
Give this to your agent
set up https://corespeed.io/SKILL.mdStart with CoreSpeed. Set up sharing and policies in your dashboard.
Let the team work.Keep the oversight.
Three things a team sets up once. The examples are illustrative.
Connectors
- Team SlackProject conversationsPrivateShared
- Company GitHubRepositories and issuesPrivateShared
- Personal GmailOnly its ownerPrivateShared
Share access, not credentials
Personal connections stay private
Approval requestWaiting
Claude Code for Jessica
slack__post_message
“Here’s what changed in this week’s release…”
Policy: Ask before posting to a public channel.
ApproveDeny
Put a person before the action
The action waits for a person
This month
- Connector calls1,204
- Web search312
- Media generation86
Key cap42% of this key’s cap
Keep tool spend in view
Usage across your team’s agents
An agent can ask.A person decides.
Write in plain English what needs a sign-off. When an action through CoreSpeed needs approval, it waits for the responsible person.
Reads fromCoreSpeed policy
Approvals for agent actions →Post this week’s release notes to #community.
notion__get_page_contentok
This week’s release notes, four changes
Their agent.Your team’s rules.
Claude Code, Codex, or Cursor. Your team does not have to pick just one.
- 1
Create your team organization
Set up CoreSpeed and invite teammates on Pro.
- 2
Choose the shared setup
Share the connections the team needs. Turn on approvals and write your policy.
- 3
Review activity and tool spend
Use the organization’s activity trail and ledger. Set monthly caps on API keys.
Setup guidesClaude CodeCodexCursor