Cost beside your traces
Put AI-coding spend on the same Honeycomb boards as the request data your team already works from, rather than in a separate tool nobody opens.
Automation
Lineman and Honeycomb
Ship spend and token metrics into Honeycomb over OTLP. Receiving metrics needs a Pro plan or above.
What this gets you
Your AI-coding spend, savings and token counts land in Honeycomb as OTLP metrics, next to the traces and events you already send. Company totals arrive with per-developer and per-repo breakdowns, so cost sits on the same boards you debug from. Honeycomb receives metrics on a Pro plan or above; on a free plan the export cannot be received and the failure is quiet, so check your plan before connecting.
What people use it for
Split spend by developer and repo
Company totals arrive alongside per-developer series, labelled by email, and per-repo series. Token counts carry a token.type label of input, output or cache.
Track what Lineman avoided
The savings series records the token spend Lineman avoided in each period, so the value of the tool is a line on your own dashboard rather than a claim in ours.
More in Automation
- n8nBuild your own workflows on Lineman data with the community n8n node.
- ZapierTrigger Zaps from spend events and pull cost data into thousands of apps.
- Power AutomateDrive Power Automate flows from Lineman alerts and usage.
- MakeRead spend, savings and alerts from a Make scenario, and use the numbers anywhere Make reaches.
Set up Honeycomb
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideLooking for something else?
Every integration in one place, searchable by name and filterable by what it does.
View all integrations