Skip to main content
TrueFoundry is an enterprise AI gateway — one OpenAI-compatible endpoint that fronts 1000+ models across 40+ providers (OpenAI, Anthropic, Bedrock, Vertex AI, Mistral, and more) with governance, budgets, and guardrails. The endpoint at https://gateway.truefoundry.ai mirrors OpenAI’s schema, so any OpenAI client works with base_url set to the gateway. Arize AX captures every gateway call via the openinference-instrumentation-openai package — the same instrumentor that covers OpenAI’s hosted API.
This guide instruments your application’s calls to the gateway. TrueFoundry can also export traces for every gateway request to Arize directly, with no application code — see the TrueFoundry platform integration.

Prerequisites

  • Python 3.9+
  • An Arize AX account (sign up)
  • A TRUEFOUNDRY_API_KEY — a Personal Access Token or Virtual Account Token from the Access section of TrueFoundry

Launch Arize

  1. Sign in to your Arize AX account.
  2. From Space Settings, copy your Space ID and API Key. You will set them as ARIZE_SPACE_ID and ARIZE_API_KEY below.

Install

Configure credentials

Setup tracing

Run TrueFoundry

Expected output

Verify in Arize

  1. Open your Arize AX space and select project truefoundry-tracing-example.
  2. You should see a new trace within ~30 seconds containing a ChatCompletion LLM span with the prompt, response, and token usage attached. The model name on the span will be the resolved model the gateway routed to (e.g. gpt-4.1-mini-2025-04-14).
  3. If no traces appear, see Troubleshooting.

Check from the skill, CLI, or SDK

Confirm spans are actually reaching your Arize AX project. Use whichever fits your workflow — the skill and CLI work for any framework; the SDK check is shown for each language.
Install the Arize Skills plugin and let your coding agent check for you:
Then prompt your agent:
Use the arize-trace skill to export and analyze recent traces from my project. Confirm spans are arriving, and summarize any errors or latency issues.

Troubleshooting

  • No traces in Arize. Confirm ARIZE_SPACE_ID and ARIZE_API_KEY are set in the same shell that runs example.py. Enable OpenTelemetry debug logs with export OTEL_LOG_LEVEL=debug and re-run.
  • TrueFoundry spans missing but other spans present. OpenAIInstrumentor().instrument(...) must run before any import openai. Make sure instrumentation.py is the first import in your entry point.
  • 401 from TrueFoundry. Use a TrueFoundry token (Personal Access Token or Virtual Account Token from the Access section), not your OpenAI key. Pass it as the api_key — the OpenAI client sends it as a Bearer token.
  • Model not found. Use the provider-account/model-name identifier from your gateway (e.g. openai/gpt-4.1-mini). The prefix is the provider account name configured in your TrueFoundry workspace, not a fixed value — copy the exact model ID from the Playground Code Snippets tab.

Resources

TrueFoundry AI Gateway Documentation

OpenInference OpenAI Instrumentor (used for TrueFoundry)

TrueFoundry AI Gateway