AI vendor integrations
Pull spend and usage straight from the AI vendors you already pay for.
AI vendor integrations connect the AI vendors your organization already pays for, so Proxon reports actual spend and usage straight from the vendor rather than only what the client-side observers can see. The numbers come from the vendor's own admin and billing data, which makes them the most accurate cost source. They also include usage that never touches an employee's machine, such as server-side or automated calls.
An admin connects each vendor once, from the Integrations page in Proxon. Nothing installs on anyone's device. Most vendors need a read-only credential that you create in the vendor's own admin console first, so you need admin access to the vendor you are connecting. Open Integrations, find the vendor under AI, and follow its Connect dialog. What each vendor needs is below.
Proxon stores these credentials encrypted at rest and in transit, and uses them only to read usage and spend. It never uses them to train models and never shares them with third parties.
Anthropic
Create an Anthropic Admin API key with organization-level access from the Anthropic Console, under Organization settings → Admin keys. An org owner or admin creates it. Paste the key, which starts with sk-ant-admin-, into the Connect dialog.
OpenAI
Create an OpenAI Admin API key in the OpenAI platform, under Organization settings → Admin keys, with its Permissions set to Read. Paste the key, which starts with sk-admin-, into the Connect dialog.
Microsoft 365 Copilot
Register an app in Microsoft Entra ID as a Global Administrator, under Entra ID → App registrations. Grant it these application permissions with admin consent: Organization.Read.All, User.Read.All, Reports.Read.All, and ReportSettings.Read.All. Then paste the app's Directory (tenant) ID, Application (client) ID, and a client secret into the Connect dialog. Copy the secret Value, not the Secret ID.
GitHub Copilot
Connect GitHub Copilot through its sign-in flow. Choose it on the Integrations page, authorize Proxon when GitHub asks, and you are done. There is no key to create.
Gemini for Workspace
Create a Google Cloud service account with a JSON key, then grant it domain-wide delegation for three read-only scopes: admin.reports.audit.readonly, admin.directory.user.readonly, and apps.order.readonly. Grant the delegation as a Super Admin, under Admin console → Security → API controls → Domain-wide delegation. In the Connect dialog, enter the service account email, the private_key value from the JSON key file including its BEGIN and END lines, and a delegated admin email. The delegated admin is a Super Admin in your Google Workspace for the service account to impersonate, not the service account itself. Leave Customer ID blank unless you are a reseller connecting a downstream tenant.
After you connect
Once a vendor is connected, its spend and usage flow into Proxon and roll up to your people. Open Cost Intelligence to see it.