Attribution integrations for AI Cost Management

Uses: AI Cost Management AI Gateway

Integrations

The following integrations are available in AI Cost Management. Clicking a tile opens the integration in your Konnect org, where you can follow the setup instructions.

Coding agents

Tools developers run in a terminal or an editor.

GitHub Copilot in VS Code

Cline

Aider

CI and source control

Jobs that run an AI tool on a change, a pull request, or a schedule.

Chat apps

Bots you build for your team’s chat.

Slack

Microsoft Teams

Discord

Issue trackers

Bots and agents that work on issues and incidents.

Jira

Linear

PagerDuty

GitHub and GitLab issues

Agent frameworks

Libraries your applications build agents with.

OpenAI Agents SDK

LangChain and LangGraph

Other AI gateways

Clients that still send another AI gateway’s tag headers.

Helicone

Portkey

Cloudflare AI Gateway

Your applications

Your own services that call models through your gateway.

Your own code

Tag reference

Integration	Sends automatically	Add with `ai-cost-<key>` headers
Claude Code	`agent-session` `agent-id` `agent-parent` `agent-request-kind` `agent-type`	`scm-provider` `scm-repository` `scm-branch`
Codex CLI	`agent-session` `agent-request-kind` `scm-repository` `scm-provider` `scm-commit` `agent-id` `agent-parent` `agent-type`	`scm-branch` `project`
OpenCode	`agent-session` `agent-id` `agent-parent`	`scm-provider` `scm-repository` `scm-branch`
Gemini CLI	None	`scm-provider` `scm-repository` `scm-branch`
GitHub Copilot in VS Code	`agent-request-kind`	`project`
Cline	None	`project`
Aider	None	`project` `scm-provider` `scm-repository`
GitHub Actions	None	`scm-provider` `scm-repository` `scm-branch` `scm-pull-request` `scm-commit` `ci-provider` `ci-pipeline` `ci-run`
GitLab CI	None	`scm-provider` `scm-repository` `scm-branch` `scm-pull-request` `scm-commit` `ci-provider` `ci-pipeline` `ci-run`
Jenkins	None	`scm-provider` `scm-repository` `scm-branch` `scm-pull-request` `scm-commit` `ci-provider` `ci-pipeline` `ci-run`
Buildkite	None	`scm-provider` `scm-repository` `scm-branch` `scm-pull-request` `scm-commit` `ci-provider` `ci-pipeline` `ci-run`
CircleCI	None	`scm-provider` `scm-repository` `scm-branch` `scm-pull-request` `scm-commit` `ci-provider` `ci-pipeline` `ci-run`
Slack	None	`chat-provider` `chat-organization` `chat-workspace` `chat-channel` `chat-channel-id` `chat-channel-type` `chat-trigger` `chat-command` `agent-name` `agent-session` `workflow-run`
Microsoft Teams	None	`chat-provider` `chat-workspace` `chat-channel-id`
Discord	None	`chat-provider` `chat-workspace` `chat-channel-id` `agent-session`
Jira	None	`ticket` `project`
Linear	None	`ticket` `project`
PagerDuty	None	`ticket`
GitHub and GitLab issues	None	`scm-issue` `scm-repository`
OpenAI Agents SDK	None	`workflow-name` `workflow-run` `agent-session`
LangChain and LangGraph	None	`workflow-name` `workflow-run` `agent-session`
CrewAI	None	`workflow-name` `workflow-run`
LlamaIndex Workflows	None	`workflow-name` `workflow-run`
n8n	None	`workflow-name` `workflow-run` `agent-session`
Vercel AI SDK	None	`workflow-name`
Helicone	`agent-session` (from `Helicone-Session-Id`) Any `Helicone-Property-<Name>` header becomes a tag named `<name>`.	None
Portkey	Each key in the `x-portkey-metadata` JSON object becomes a tag of the same name.	None
Cloudflare AI Gateway	Each key in the `cf-aig-metadata` JSON object becomes a tag of the same name.	None
Your own code	None	`project` `environment` `use-case` `feature` `customer-account`