# Immiscible documentation

> See what your company spends on AI, what it could save, and which keys nobody is watching. Then put every agent's model requests, payments and tool calls behind rules a person wrote, with a record anyone can check.

Source: https://immiscible.fly.dev/docs

Most companies cannot say what they spend on AI, which team spends it, or how much of it a cheaper model would have done just as well. Immiscible starts there. It reads your bills from OpenAI and Anthropic, or the traffic through its gateway, and tells you what went where, what could have cost less, and which keys nobody is watching. The savings are estimates, and every one shows how it was worked out.

The same workspace then governs the agents themselves. Immiscible is not an agent; it sits between your agents and anything consequential they do, so a model request, a payment or a tool call is decided against rules a person wrote, and a person is asked when a person should decide.

Where to start:

- [The AI check](https://immiscible.fly.dev/check): drop last month's usage export and see your spend and possible savings in a couple of minutes. No account needed.
- [For finance teams](https://immiscible.fly.dev/docs/finance.md): see your spend, set a budget, choose who approves. No code.
- [Add the analyst to Claude](https://immiscible.fly.dev/docs/analyst.md): ask what you spent, what is wasted and which keys are unwatched, in your own words.
- [Quickstart](https://immiscible.fly.dev/docs/quickstart.md): `npx immiscible init` in your agent's project, then your first decision, in five minutes.
- [API reference](https://immiscible.fly.dev/docs/api.md): every route the server answers, generated from the router, with curl, Node and Python.

How the pieces fit together, the four ways an agent reaches the gate and the conventions these docs use are on [How it fits together](https://immiscible.fly.dev/docs/concepts.md).