Manage integrations in the Requesty Console.
Overview
Connecting a platform gives you one place to review who has access to which AI platforms and where spend is going:- API keys from the platform appear in the same table as your Requesty keys.
- Users from every platform are listed together, merged by email.
- Workspaces (Claude Platform) and projects (OpenAI Platform) appear as groups.
Connect a platform
Each integration needs an admin API key from the platform. Create the key in the platform’s console, then add it in Admin Panel > Integrations.- Claude Platform
- OpenAI Platform
Create an Anthropic Admin API key. Admin keys start with
sk-ant-admin-.See Anthropic’s Admin API documentation for how to create one.1
Create an admin key
Create the admin API key on Claude Platform or OpenAI Platform as described above.
2
Open Integrations
Go to Admin Panel > Integrations in the Requesty Console.
3
Add the key
Paste the admin API key for the platform you want to connect.
Where platform data appears
API Keys
In Admin Panel > API Keys, platform keys appear in the same table as your Requesty keys. The Source column shows a Claude Platform or OpenAI Platform badge, and a Platform filter sits next to All keys, Mine, and Service accounts. For each platform key you can see the owner’s email, the created date, and the status (active or expired). Per-key spend is shown for OpenAI Platform keys only. Claude Platform keys show no usage.Users
In Admin Panel > Users, users from Requesty and every connected platform are merged into one row by email. The Platforms column shows a badge for each platform the user belongs to: Requesty, Claude Platform, or OpenAI Platform. Use the Platform filter to narrow the list. Per-user spend is shown for OpenAI Platform only. See User Management for everything else on this page.Groups
In Admin Panel > Groups, Claude Platform workspaces and OpenAI Platform projects appear as groups. The Source column shows the platform badge, and each row shows the member count, created date, and group spend. Use the Platform filter to narrow the list. Platform groups can’t have budgets, access lists, guardrails, or labels, so those columns stay empty for them. See Groups Management for Requesty groups.Spend visibility
Data freshness and security
- Fetched live. Requesty fetches platform data from the platform each time an admin page loads. There is no sync schedule and no manual sync.
- Nothing cached. Requesty doesn’t cache or store the platform’s users, API keys, workspaces, projects, or spend.
- Admin key stored encrypted. The admin API key is the only thing Requesty stores. It’s encrypted and only ever shown masked.
- Disconnecting deletes the key. When you disconnect an integration, Requesty deletes the stored admin API key.
Limitations
- Platform users, API keys, and groups are read-only. You can’t edit them from Requesty.
- They have no Requesty spending limits, access lists, or guardrails.
- They don’t route traffic through Requesty.