Automation
Read spend, savings and alerts from a Make scenario, and use the numbers anywhere Make reaches.
Read your AI-coding spend, savings, allowance and cost alerts from a Make scenario, then send the numbers anywhere Make can reach: a Google Sheet, a Slack digest, a Teams message, an approval. Make's built-in HTTP module calls the Lineman API directly, so there is no app to install and nothing to keep updated. All fourteen reports are read-only, so a scenario can report on cost but never change a budget, dismiss an alert or edit a cost centre. A scenario sees only what the person who created the API key can see.
A scheduled scenario reads the spend breakdown and writes it into a Google Sheet, split by developer, repository, branch, ticket, model or cost centre. Spend reports take a window in days, up to 92, so a monthly run asks for 30. Company-wide figures need a key created by an administrator or an auditor. Finance gets the numbers without asking engineering to pull them.
Read the alerts report on the schedule you set and route budget breaches and cost spikes into a Slack channel or a Teams message. The alerts report needs an administrator's or an auditor's key: it returns an error to any other key rather than narrowing to one person's figures. A spike is seen when the scenario next runs, not at month end.
The allowance report gives how much of your plan's monthly tokens you have used. A filter in the scenario posts a warning once usage passes the level you set. You find out before the allowance runs out rather than after.
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideEvery integration in one place, searchable by name and filterable by what it does.
View all integrations