by AtlasBurnCommunityAsk AgentOne about your AI spend: cost by model and feature, forecasts, guardrails and runaway agents. Set up from chat with your approval.
AtlasBurn connects AgentOne to your real AI usage and cost data, so you can ask where your LLM spend is going and catch problems before they become a large bill.
What you can ask:
Set up AtlasBurn from AgentOne by asking "Set up AtlasBurn in this project." AgentOne requests a key, and you approve it in your browser with a fresh sign-in. The AtlasBurn CLI receives the new key and writes it to your project's env file. The key never passes through AgentOne or the chat, and your existing keys are never changed.
AtlasBurn works across 13 providers, including OpenAI, Anthropic, Google Gemini, Vertex AI, Azure OpenAI, AWS Bedrock, Mistral, Groq, DeepSeek, xAI and OpenRouter. Usage data comes from the open-source AtlasBurn SDK (Node.js/TypeScript) or from the AtlasBurn proxy for any other language.
The connector is content-blind: it never sees your prompts or model outputs. The data tools are read-only and cannot change your settings, budgets or guardrails. The only writes are a pending key request and a one-time setup code, and nothing is created without your approval. Sign-in uses OAuth with your AtlasBurn account, and access is limited to your own workspace's data.