# What the machines spend: read from the vendor itself

URL: https://www.orla.finance/en/product/machines/ai-spend
Markdown twin of that page. Append `.md` to any Orla page URL to get one.

Orla reads OpenAI's and Anthropic's own cost report every night. A monthly ceiling on a vendor stops the cards that pay it.

## How it works

- **An admin key, read only.** Paste the organisation's admin key, not a project key. Orla reads the cost report and the names behind it once a night, and never shows the key again.
- **Per day, per model.** The vendor's own figure lands beside the supplier's limit in Budgets: paid for and not yet used on prepaid credits, used and not yet billed on an invoice after the month.
- **Who spent it.** The last thirty days split by project and by API key at OpenAI, by workspace at Anthropic. Each list is its own cut of the same money.
- **A ceiling that stops.** A spend guard on the vendor watches the larger of what the book charged and what the vendor says was used. Past it, the agent cards fenced to that vendor freeze until a person thaws them.

## Questions

**Can Orla change anything at OpenAI or Anthropic?** No. The admin key is used only for read-only calls: the cost report and the names of projects, keys and workspaces. Orla never creates keys or spends anything at the vendor.

**Is the vendor's figure booked in our books?** No. The books stay what the card and the invoices say. The vendor's figure feeds the supplier's limit, the spend guard and the forecast.