Xinference Integration
Use this page when wiring Xinference to xtrace as the Langfuse-compatible observability backend.
Hosted Endpoint
- Documentation site:
https://xtrace.sh - Hosted API endpoint for Xinference:
https://api.xtrace.sh
1. Smoke Check The Hosted Service
These checks require no credentials:
bash
curl -sS https://api.xtrace.sh/healthz
curl -sS https://api.xtrace.sh/readyzExpected result:
/healthzreturns200 OK/readyzreturns{"status":"ready"}
2. Configure Xinference
Provide the trial key pair over a secure channel, then point Xinference at the hosted API:
bash
export LANGFUSE_HOST=https://api.xtrace.sh
export LANGFUSE_PUBLIC_KEY=pk-...
export LANGFUSE_SECRET_KEY=sk-...If you configure Langfuse through the Xinference settings UI or API, use the same values there.
3. Validate The Read Path Xinference Uses
Xinference reads xtrace through the Langfuse-compatible public API with HTTP Basic auth:
bash
curl -sS -u "$LANGFUSE_PUBLIC_KEY:$LANGFUSE_SECRET_KEY" \
https://api.xtrace.sh/api/public/projects
curl -sS -u "$LANGFUSE_PUBLIC_KEY:$LANGFUSE_SECRET_KEY" \
"https://api.xtrace.sh/api/public/traces?page=1&limit=10"
curl -sS -u "$LANGFUSE_PUBLIC_KEY:$LANGFUSE_SECRET_KEY" \
https://api.xtrace.sh/api/public/metrics/daily4. Recommended Xinference Test Flow
- Confirm
https://api.xtrace.sh/readyzis healthy. - Configure
LANGFUSE_HOST=https://api.xtrace.shin Xinference. - Apply the provided
LANGFUSE_PUBLIC_KEYandLANGFUSE_SECRET_KEY. - Trigger one real inference request from the Xinference environment.
- Open the Xinference trace list or call
/api/public/tracesdirectly. - Confirm the latest trace and daily metrics are visible.
5. What To Send To The Xinference Side
Provide the Xinference operator with:
- The hosted endpoint:
https://api.xtrace.sh - One trial
LANGFUSE_PUBLIC_KEY - One matching
LANGFUSE_SECRET_KEY - The smoke-check commands from this page
- The direct read-back commands from this page
Do not publish the trial keys in public documentation, screenshots, or tickets.