Respan Exa instrumentation (Python)
Native OpenTelemetry instrumentation for the official exa-py SDK.
Requires Python 3.11 through 3.13 and exa-py>=2.20.0,<3.0.0.
The package traces the stable 2.20 API surface that carries AI work:
ExaandAsyncExasearch, contents, answer, and streaming calls- deprecated search/similarity compatibility methods still shipped by Exa 2.x
- Agent run create, stream, wait, poll, stop, and lifecycle operations
- the legacy Research client for compatibility (Exa recommends deep search for new research flows)
- executable provider-neutral, OpenAI, and Anthropic search/contents helpers through the core SDK methods they invoke
Websets, Search Monitor CRUD, and beta Agent Monitor operations are intentionally not patched in the first release. They are long-lived control-plane APIs rather than in-process SDK operations.
Install
pip install respan-ai respan-instrumentation-exa exa-py
exa-py>=2.20.0,<3.0.0 is the declared and tested range. Python 2.20 is required because it is the first stable release with the get_contents tool helpers.
Use
from exa_py import Exa
from respan import Respan
from respan_instrumentation_exa import ExaInstrumentor
respan = Respan(
api_key="respan-key",
instrumentations=[ExaInstrumentor()],
)
exa = Exa(api_key="exa-key")
result = exa.search(
"recent advances in retrieval",
type="auto",
contents={"highlights": True},
)
respan.shutdown()
The integration is explicit-only. Exa is a search/tool/agent SDK and can overlap with OpenAI or Anthropic instrumentation when its tool adapters are used, so it is not direct-LLM auto-instrumentation.
Set capture_content=False on ExaInstrumentor, or set TRACELOOP_TRACE_CONTENT=false, to omit query, result, prompt, completion, and stream payloads while retaining operation/status metadata. API keys and authorization-like fields are always redacted.
Entity names are provider-neutral: tools use names such as search and get_contents, answers use answer, Agent runs use run, and legacy Research uses research. Native SDK operation names, stream state, result counts, request IDs, cost, citations, and legacy markers are stored only in the canonical respan.metadata JSON object. Answer spans set gen_ai.request.model only when the SDK request or response supplies a model; otherwise semantic naming resolves to bare llm.
Streaming spans end when the iterator is exhausted, fails, or is explicitly closed. Applications that abandon a stream without closing it cannot produce an exact completion timestamp; use the stream as a context manager where supported or close it explicitly.
Metadata
Release files for respan-instrumentation-exa 0.1.0
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 |
|---|---|---|---|---|
| respan_instrumentation_exa-0.1.0.tar.gz | 11.3 kB | Without provenance | Details for respan_instrumentation_exa-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| respan_instrumentation_exa-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for respan_instrumentation_exa-0.1.0-py3-none-any.whl |
Total release size: 24.1 kB
Release files / respan_instrumentation_exa-0.1.0.tar.gz
| Download URL | respan_instrumentation_exa-0.1.0.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a133c66a46c23788eb2c068238d1dbcf5d9eea495f94ccad5e7f1ce7b987a00
|
|
BLAKE2b-256 checksum How to use checksums |
78a09e16a7ddc8064232fbe5d8acf969d773d8a0910ab84c3c0594a4c85b274a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / respan_instrumentation_exa-0.1.0-py3-none-any.whl
| Download URL | respan_instrumentation_exa-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f91146fab7b0be3d6a54c00568082935dfff0d6acf87caeeb3d2b7a4cac5872
|
|
BLAKE2b-256 checksum How to use checksums |
3b6df72486301de4ae28bd52d86c013ecd3cfaacc414715b0ab5c3b337ee6181
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Security for respan-instrumentation-exa 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.