softprobe (Python)
Softprobe Agent QA Python SDK — LLM / agent observability via OTLP to Softprobe Explorer.
pip install softprobe
# LangChain:
pip install 'softprobe[langchain]'
Docs: Agent QA → LangChain · Quick start
Examples
| Script | Path |
|---|---|
Basic from_env() |
examples/basic.py |
| LangChain best path | examples/langchain_agent.py |
See examples/README.md.
export INGESTION_KEY="<Ingestion Key>"
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://explorer-staging.softprobe.ai/api/thelake/v1/traces"
export OTEL_EXPORTER_OTLP_TRACES_HEADERS="Authorization=Bearer ${INGESTION_KEY}"
export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL="http/protobuf"
export OTEL_RESOURCE_ATTRIBUTES="deployment.environment.name=staging"
python examples/basic.py
The Ingestion Key is the bearer value in the standard OTLP headers. The full
trace endpoint selects where traces go. Set SOFTPROBE_BASE_URL only when
explicit score writes should use a non-production API; it does not affect trace
export. Without an OTLP endpoint, the SDK uses the production trace URL. You can
pass the trace settings directly:
Without a custom endpoint, the SDK exports traces to
https://explorer.softprobe.ai/api/thelake/v1/traces.
import os
from softprobe import SoftprobeClient
client = SoftprobeClient(
ingestion_key=os.environ["INGESTION_KEY"],
otlp={
"traces_endpoint": "https://explorer-staging.softprobe.ai/api/thelake/v1/traces",
"protocol": "http/protobuf",
},
resource_attributes={"deployment.environment.name": "staging"},
)
base_url is optional here; it defaults to the production score API. Set it
separately if score writes should use staging. It never changes the trace
destination. Without an OTLP endpoint, traces use the production trace URL.
Develop
uv sync --extra langchain --extra openai --extra dev
uv run pytest -q
uv run mypy src/softprobe
Publish
Create a GitHub Release with tag vX.Y.Z. The release workflow publishes to PyPI via Trusted Publishing (OIDC).
Note: The older public repo
softprobe/softprobe-python(Hybrid/replay SDK) is archived. This repo is the Agent QA / LLM package.
Metadata
Release files for softprobe 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| softprobe-0.1.2.tar.gz | 47.7 kB | With provenance | Details for softprobe-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| softprobe-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for softprobe-0.1.2-py3-none-any.whl |
Total release size: 84.3 kB
Release files / softprobe-0.1.2.tar.gz
| Download URL | softprobe-0.1.2.tar.gz |
|---|---|
| Size | 47.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05e249b4df27cceb5cc7e4ed39a5773eabbd43d2e017811c47a23df8a61bcc56
|
|
BLAKE2b-256 checksum How to use checksums |
55266275b6798ca56c3aecd0b34a483fceaa93fa9e4e22feb5e5f5309109ff37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logRelease files / softprobe-0.1.2-py3-none-any.whl
| Download URL | softprobe-0.1.2-py3-none-any.whl |
|---|---|
| Size | 36.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
898c143847f288474c0cf707544959683f87d70244fb2a2e535d7f6926edd8c4
|
|
BLAKE2b-256 checksum How to use checksums |
1a583c2ccd7addd298460d6486196c45e8810288f71e5cbfde533fe6d4ebf3ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logSecurity for softprobe 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for softprobe-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.