MetricAI SDK

Financial rails for your AI agents

Route your LLM, voice, and tool calls through the MetricAI proxy. Meter token/usage/outcome cost in INR and emit telemetry — without changing your provider code.

PyPI

pip install metricai

BYOK

bring your own keys

fail-open

telemetry never blocks agents

INR

wallet-native billing

Copy-paste quickstart

Install: Installation. Full walkthrough: Quickstart.

Python

import os
import metricai
from openai import OpenAI
from dotenv import load_dotenv

load_dotenv()

metricai.init(
    api_key=os.getenv("METRICAI_API_KEY"),
    auto_instrument=True,
    default_agent_id="weather-bot",
    default_user_id="user_123",
    llm_keys={"openai": os.getenv("OPENAI_API_KEY")},
)

client = OpenAI()
resp = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "What is the current weather in Tokyo?"}],
)
print(resp.choices[0].message.content)

Core concepts

Concept	What it is
Proxy routing	Calls go to `…/v1/proxy/{provider}` for server-side metering.
BYOK	You keep provider keys; MetricAI forwards via `X-*-API-Key` headers. Default (`mode="byok"`).
Managed	MetricAI-managed provider keys; opt in via `mode="managed"`.
Attribution	`agent_id`, `user_id`, `session_id`, workflow ids for cost breakdowns.
Telemetry / track()	Events POST to `/v1/sdk/events`. Fail-open by default.
Outcome billing	Charge per business outcome (e.g. booking confirmed) alongside tokens.
Sessions	Group turns under one `session_id` with aggregates and budget caps.