Quickstart
Send your first trace to SouthBase.
Not yet shippable
SouthBase is in early development. The ingest endpoint referenced below does not
accept traffic yet — this page is structure, written so the shape of the
integration is fixed before the code exists. Real steps land in Week 8; see
docs/planning/SPRINT-PLAN.md.
The integration is OpenTelemetry
There is no proprietary SDK to learn. SouthBase accepts OTLP, so if your application already emits OpenTelemetry traces through an OpenInference instrumentor, pointing them at SouthBase is a configuration change:
export OTEL_EXPORTER_OTLP_ENDPOINT="https://ingest.southbase.dev"
export OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer $SOUTHBASE_API_KEY"from openinference.instrumentation.anthropic import AnthropicInstrumentor
AnthropicInstrumentor().instrument()That is the whole integration. Your data stays portable: the same instrumentation points at any OTLP backend, so switching away costs you a configuration change too. That is deliberate.
Adding the agent
Running the SouthBase agent in front of the endpoint adds three things the direct path cannot:
- Redaction at the edge — sensitive payloads never leave your network
- Token normalization — provider usage fields mapped to the four buckets
- Cost enrichment — cost attached locally, so it survives an outage upstream