Anthropic permissions
CloudYali reads your Anthropic organization with an Admin API key. The key can manage the organization as well as read it; CloudYali calls only the read endpoints below.
What CloudYali calls
| Anthropic Admin API | What CloudYali reads | Used for |
|---|---|---|
Organization (/v1/organizations/me) | The organization's ID and name | Checking the key is an Admin key, and naming the connection |
| Cost report | Daily cost by workspace and line item | Cost Explorer, budgets, anomalies |
| Usage report | Daily usage by model, workspace and API key | Cost by model and by key |
| Claude Code usage | Daily Claude Code activity, when available | Claude Code cost and usage |
| Workspaces, API keys, users, workspace members | Names, IDs, and users' email addresses | Naming what is behind each cost |
CloudYali does not read prompts or responses: the Admin API does not return them.
How the key is stored
| Storage | AWS Secrets Manager, encrypted; the CloudYali database holds only a reference |
| Shown in the console | The key's first and last characters, on the Connected tab |
| After Remove | CloudYali deletes the stored key |
Revoke access
Delete the key in the Anthropic Console under API keys → Admin keys. CloudYali can then no longer read the organization. To stop CloudYali trying, also select Remove on the connection.
Where you see it in CloudYali
Each Anthropic organization appears on the Connected tab of Integrations, with its name and key hint. To connect one, see Connect Anthropic.
Was this page helpful?