Internal tools across many models.
Several teams use different models, but the invoice should still be a single one. Each tool gets its own key and its own limit.
How it is built.
-
One key per tool
Each tool gets its own key with its own monthly limit and, if desired, its own per-minute limit.
Budgets -
Check models at runtime
At startup, the tool reads
ModelsGET /v1/modelsand notices when a model has been given a cutoff date. -
Cost per tool
GET /v1/usage?group_by=api_keyshows which tool used what. -
Look things up from the editor
Anyone working in an AI client can look up prices and usage through the MCP server. It only reads.
MCP
GET https://api.flowmodels.one/v1/usage?group_by=api_key&start=2026-11-01&end=2026-11-30
Authorization: Bearer $FLOWMODELS_API_KEY