Agent unit economics · Margin protection
Know what your AI costs and whether it pays off.
Every agent run adds token and tool costs. Your subscription price may stay the same. See what each customer costs to serve, so you know what to optimize, limit, or charge for.
Agent workflow metadata only · No prompts or responses required · No proxy
14 days · No credit card required
The silent failure mode
Usage looks healthy. Customers are happier. The economics are getting worse.
A product team adds longer context, stronger retrieval, MCP tools, and a premium model for difficult requests. Quality improves and revenue stays fixed—but every tool can trigger more planning, retrieval, validation, retries, and model calls.
The provider bill shows $80 of spend. Ganivra shows which customer caused it, which workflow changed, and what to do next.
MCP cost attribution
The tool call is only one line on the trace. The cost can keep growing after it returns.
MCP gives agents access to data and actions. It also creates hidden cost paths: a single tool decision can trigger retrieval, follow-up generation, validation, and retries. Ganivra joins the server, tool, and every downstream model call under one execution.
- 01Agent plansGPT-5$0.040
- 02search_accountsMCP · crm-server$0.002
- 03Agent summarizesGPT-5$0.110
- 04Validation retryGPT-5 mini$0.060
0.2¢ direct tool cost became 21.2¢ of execution COGS. The protocol is not the problem; invisible fan-out is.
One MCP lookup triggered three model calls. At scale, that pattern erases $11K/month in margin.
The search_accounts tool itself cost only 0.2¢. Planning, follow-up generation, and a retry pushed this support execution for Northstar Health to 31¢—3.4× the workflow baseline.
Inspect the four linked steps →AI revenue
$6,420Example revenue metadataAI cost
$1,842.67Model + MCP-linked COGSGross margin
71.3%$4,577 after AI costCost / execution
$0.048Workspace averageBelow target margin
3Illustrative customersPrompt-level unit economics
Know which prompt versions make or lose money.
ticket_resolution / prompt:v17Prompt v17 added more context and longer outputs. Cost rose from 4.8¢ to 6.1¢ while gross margin fell eight points.
No prompt content stored. Ganivra attributes cost using customer-supplied prompt_id and prompt_version metadata.
The profitability gap
Your AI bill cannot tell you whether your AI product is profitable.
Provider spend is a total. Margin is a decision.
AI agents across industries
Find where your AI workflows lose margin.
Protect fixed-fee margins
Inspect repeated calls and growing token usage in support workflows. See which customers cost more to serve than their contracts earn.
Explore customer support →See the cost of every document workflow
Compare model and prompt-version costs, including reported cached tokens. Identify expensive extraction workflows before changing models or prompts.
Explore LegalTech →Price the full research workflow
Link model calls and MCP tool steps to one research report or audit execution. See the tracked cost beyond the initial query.
Explore financial services →Inspect expensive agent runs
Follow model steps, token usage, and reported retries through a coding workflow. Find where repeated generation and testing add cost.
Explore coding agents →Know your cost per customer
Use existing tenant IDs to compare usage, revenue, and margin. See where customer pricing or usage limits need a closer look.
Explore B2B SaaS →Share usage facts, not sensitive content
Send model names, tokens, latency, and pseudonymous IDs. No prompts, responses, PHI, or customer contact details required. No Ganivra proxy.
Explore regulated enterprises →Breakdowns
Where cost-to-serve accumulates
By model
CostBy MCP tool · linked COGS
CostBy workflow
CostBy feature
CostBy account
CostMargin risk queue
Executions eroding margin
| Execution | Workflow | Account | Calls | Tokens | Cost | Latency | Timestamp |
|---|---|---|---|---|---|---|---|
| exec_demo_72f1 | inbound_support_call | Northstar Health | 4 | 22K | $0.31 | 7.20s | Aug 07, 2026 · 12:00 UTC |
| exec_demo_91ac | ticket_resolution | Atlas Logistics | 5 | 29K | $0.284 | 11.92s | Aug 07, 2026 · 11:42 UTC |
| exec_demo_0bd4 | document_processing | Meridian Financial | 4 | 22K | $0.247 | 8.64s | Aug 07, 2026 · 11:18 UTC |
| exec_demo_c822 | sales_follow_up | Summit Retail | 6 | 19K | $0.219 | 14.32s | Aug 07, 2026 · 10:51 UTC |
| exec_demo_f10e | inbound_support_call | Northstar Health | 3 | 9.7K | $0.183 | 5.84s | Aug 07, 2026 · 10:37 UTC |
Frequently asked questions
What teams ask before instrumenting.
Straight answers about data, integrations, and getting started.
01What is Ganivra?
Ganivra is an AI and MCP unit economics platform for teams building agentic products. It connects model and tool cost to the customer, feature, workflow, prompt version, MCP server, and MCP tool that caused it.
02How does Ganivra calculate AI unit economics?
Ganivra attributes each paid model call, MCP tool step, retry, token, and workflow step to product metadata such as customer, feature, workflow, prompt ID, server, and tool. With revenue metadata, teams can compare the full execution cost-to-serve with revenue and gross margin.
03Why does MCP cost tracking matter?
An MCP tool call may be free or inexpensive by itself, but it can trigger planning, retrieval, validation, retries, paid APIs, and additional model calls. Ganivra joins those steps under one execution so teams can see the true cost of each server and tool instead of only the direct tool fee.
04Does Ganivra store prompts or responses?
No. Ganivra is designed to collect execution metadata rather than prompt or response bodies. Prompt-level economics use customer-supplied prompt IDs and version labels.
05Which AI providers does Ganivra support?
The Python SDK automatically instruments OpenAI Responses calls and can record MCP tools with ganivra.mcp_call. The same REST API accepts model and MCP events from any backend, with versioned catalog pricing for OpenAI, Google Gemini, Anthropic Claude, and Perplexity Sonar. Unknown costs remain explicitly unpriced until a catalog, contract, or provider-reported rate is available.
06How do I get started?
Start a 14-day full-product trial, copy your SDK key, and instrument one real workflow. Your first execution will appear in the dashboard with attributed cost.
Start your full trial
Your first workflow is enough to start finding value.
Connect one workflow to inspect its model and tool costs. Add customer IDs to see who drives the spend, then connect revenue to understand margin. No sales call or credit card required.
import ganivra
ganivra.init(api_key="your_key")See your first real execution
Already have an account? Sign in