ai-cur Contact for more details
Coming soon. Contact for more details.
Questions

The questions buyers ask, answered straight.

The quick ones first. Then the hard ones, where each answer starts with the part of the objection that is true and every market figure carries its source and date.

The quick ones

Before you get started.

How can we get started?

Public access and downloads are coming soon. Contact us for product details, availability and your team's requirements.

Do you read our code, prompts or tickets?

No. Every connector reads amounts, people, dates and states. The desktop client reads usage from files your tools already write, and session text stays in those files.

Is this a way to watch individual employees?

No, and the database is built so it cannot be. People see their own numbers, leads see their own team, and leaders see groups above a minimum size. Comparisons are withheld when a team is too small.

What does it cost?

Coming soon. Contact for more details.

Which systems do you connect to?

Implemented and planned connections are listed on the integrations page. If yours is missing, tell us.

Can it run inside our own environment?

The portfolio is designed for standalone, Databricks and ServiceNow deployment profiles. Availability and acceptance differ by profile; public access is coming soon. Security and deployment.

Can we leave, and take our data?

Export everything held about you at any time. Deleting an account starts a governed deletion with a grace period in which you can change your mind.

The hard ones

"We already have something for this."

01

Doesn't each vendor's own dashboard already show this?

Partly, and some of those dashboards are very good. Anthropic and Cursor each report cost per person13, OpenAI reports billed amounts by project, line item or API key2, and GitHub's Copilot usage metrics API carries no cost at all4.

That is four cost models that do not line up, and each vendor dashboard is built around its own tools. ai-cur puts them on one page, in one currency, beside the same people.

02

LiteLLM already tracks our spend. Why pay for this?

LiteLLM is a strong gateway: spend per key, user and team, routing, caching and hard budget limits, self-hosted, with no licence price5. Running it still costs you operations time.

A gateway sees the traffic that passes through it. Seat invoices reach you by email, not through a proxy, and neither do your merged pull requests. ai-cur is built to read both, and serves a cap decision that LiteLLM or any gateway can enforce.

03

Our DevEx platform already reports AI impact.

Several do, and some at token level. What we did not find in the public documentation we reviewed is that impact reconciled to the invoice, with seats, credits and discounts in it.

That is absence of evidence rather than proof, so ask your vendor where credits and discounts appear. If they can show you, you may not need us for that part.

04

Our FinOps tool already covers AI spend.

It may well see individual developers. Vantage breaks Cursor spend down by developer6, and CloudZero splits Anthropic Enterprise spend by user, separating Claude Code from chat7.

CloudZero also positions its platform around AI cost allocation, unit economics and outcomes. Git AI and Exceeds connect engineering activity with AI usage too. Compare the evidence and scope you actually need, not a claim that those categories cannot do it. ai-cur brings local usage visibility, utilization and cost-to-work reporting into one product path. See Git AI, Ink and CloudZero for their current scope.

05

Why not wait for the platforms to build it?

They will build more. Gartner's 2026 evaluation of AI coding agent vendors counts cost controls among the capabilities it expects8, and vendor analytics already come with the plan.

The most capable platform budget we reviewed, Unity AI Gateway on Databricks, leaves provisioned throughput and inference on outside models untracked9. A platform's controls end where spend on other vendors begins, and that is where your waiting would leave the gap.

What we claim

"How do you know?"

06

How accurate is your attribution?

We have no accuracy figure to give you. None of the vendors we reviewed publishes one either, and a number without a method would be worse than none.

ai-cur makes no attribution claim: it sets a person's settled spend beside the same person's merged work and never says a tool wrote it. If we ever publish attribution, we will publish how it was measured, how wrong it can be, and where it is blind.

07

Has the cost record passed FOCUS validation?

No. The record is aligned with FOCUS version 1.4, ratified on 4 June 202610, and keeps model and input and output tokens apart where the vendor reports them.

It has not been through a validator, and a FOCUS certification needs Foundation membership and credentials we do not hold. Until then, alignment is the whole claim.

08

What percentage will it save us?

We will not name one. Anyone who quotes a percentage before reading your bill is guessing.

What you get is the bill laid out so you can find the idle seats, the overruns and the plans that no longer fit. Any saving is yours to measure, in your own records.

Fit and incentives

"Is this built for a company like ours?"

09

If you charge on our spend, don't you want us to spend more?

That is a fair worry about incentives. A price that grows with your spend would reward us when you spend more, and a cut of savings would make every saving an argument.

Commercial terms are not published yet. Contact us to discuss the scope and pricing basis before making a commitment.

10

We are not a software company. Is this for us?

Engineering is where the work record is richest today, so that is where the numbers are deepest. The chain is the same for any team: AI spend on one side, and on the other the work items that team already records, such as ServiceNow incidents and changes, Salesforce opportunities and cases, or support tickets.

Connectors for GitHub, Jira, GitLab, Linear, ServiceNow and Salesforce are built and tested, and none has yet run against a real account. If the system your teams work in is not there, tell us: the join needs a work item with a person and a date on it.

  1. 1Anthropic, Claude Code analytics, code.claude.com, read 8 August 2026.
  2. 2OpenAI, Costs endpoint reference, developers.openai.com, read 8 August 2026.
  3. 3Cursor, Admin API, cursor.com, read 8 August 2026.
  4. 4GitHub, Copilot usage metrics API, docs.github.com, read 8 August 2026.
  5. 5LiteLLM, pricing, litellm.ai, read 8 August 2026.
  6. 6Vantage, Cursor integration, vantage.sh, read 8 August 2026.
  7. 7CloudZero, Anthropic Enterprise connector, cloudzero.com, read 8 August 2026.
  8. 8Virtualization Review, coverage of Gartner's 2026 report on AI coding agents, virtualizationreview.com, read 8 August 2026.
  9. 9Databricks, Unity AI Gateway budgets, docs.databricks.com, read 8 August 2026.
  10. 10FinOps Foundation, Introducing FOCUS 1.4, finops.org, read 9 August 2026.

Ask us the one that isn't here.

Or check the answers against your own month first.