Compatibility Matrix
Which SDKs, gateways, and frameworks emit GenAI traces natively for AI Cost Management trace attribution.
Trace attribution needs OpenTelemetry traces with GenAI semantic conventions. The tables below show which model SDKs, gateways, and frameworks emit those attributes natively, and which are supported by the Harness instrumentation SDK.
Use this matrix to decide your setup path: if your stack already emits GenAI traces, route them to Harness; if not, add instrumentation. Go to AI Cost Management Quickstart for the steps.
Model Client SDKs
Used for LLM inference.
OpenAI Python SDK
✅ Yes (most mature)
✅ Yes
Anthropic SDK
✅ Yes
✅ Yes
Google GenAI / Vertex SDK
✅ Yes
✅ Yes
AWS Bedrock
✅ Yes
Coming soon
Gateways
LiteLLM
✅ Yes
✅ Yes
Envoy
❌ No
N/A
Agent Orchestration Frameworks
Google Agent Development Kit
✅ Native
OpenAI Agents SDK ("OpenAI ADK")
✅ Yes
Anthropic Agents SDK
✅ Yes
Microsoft Agent Framework ("Microsoft ADK")
✅ Native (partial)
Microsoft Semantic Kernel
✅ Native (opt-in)
AWS Strands Agents SDK
✅ Native
LangGraph / LangChain
⚠️ Not native
CrewAI
⚠️ Mixed
LlamaIndex
⚠️ Not native
Pydantic AI
✅ Native
AutoGen / AG2
⚠️ Partial
Haystack
⚠️ Not native
Smolagents
⚠️ Not native
Next Steps
Go to AI Cost Management Quickstart to connect a provider and see billed cost.
Go to the AI Cost Management Quickstart to instrument your application for trace attribution.
Go to the GenAI Span Attribute Reference to review the attributes CACM reads from each span.
Go to AI Cost Troubleshooting if data does not appear as expected.
Go to the AI Cost Management FAQ to review common questions.
Last updated
Was this helpful?