cortad
Every model call your app makes, as it happens, sent to Cortad.
pip install cortad
import os
from cortad import cortad
bl = cortad(key=os.environ["CORTAD_INGEST_KEY"], capture_content=True)
bl.install()
The key is read from the environment, never written into code. The SDK records which version of your app answered each conversation: it reads your host's deploy variable where there is one, and the commit of the checkout you are running from where there is not.
1 maintainer
Metadata
1 maintainer
Release files for cortad 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cortad-0.3.1.tar.gz | 21.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cortad-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.3 kB
Release files / cortad-0.3.1.tar.gz
| Download URL | cortad-0.3.1.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf3205a18f02d946ffaf3b50a7593fb84e26733eeebbe613734518c6c769311a
|
|
BLAKE2b-256 checksum How to use checksums |
6522d565701bd3faeeca05b6ee9dab6e6f46dff8aa12eaa20f1fef74173381ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 18, 2026.
Transparency logRelease files / cortad-0.3.1-py3-none-any.whl
| Download URL | cortad-0.3.1-py3-none-any.whl |
|---|---|
| Size | 21.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66811f8309e85c3243e27aab58d8aefa3089b5c339c20706b6364cc29f6f456e
|
|
BLAKE2b-256 checksum How to use checksums |
512f5bd583e2233f7fca8181eacc0ba35423e75bc64e481e2cdcc79cc73b063f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 18, 2026.
Transparency log
