Assay Python Bindings
assay-it is the Python package for the assay import namespace.
It currently provides a small, bounded surface on top of Assay core:
AssayClientfor writing JSONL trace records from PythonCoveragefor policy coverage analysis against trace/tool-call inputsExplainerfor rule-by-rule explanation of a single trace- a
pytestfixture plugin exposed asassay_client
Install
pip install assay-it
Import path:
from assay import AssayClient, Coverage, Explainer, validate
What It Is
This package is for Python-side trace capture and lightweight policy-analysis helpers. It is useful when you want to:
- append structured trace events to a JSONL file from Python
- analyze tool-call traces against an Assay policy
- explain why a given trace matched or violated policy rules
- use a simple pytest fixture around the Python client
What It Is Not
This package is not the full Assay CLI or the full trust-compiler surface. It does not replace:
assay mcp wrapand runtime MCP enforcement- evidence bundle generation and verification workflows
- Trust Basis / Trust Card generation
- the GitHub Action or release-binary install path
Those outward-facing product surfaces live in the main Assay CLI and repository docs.
Example
from assay import AssayClient, Coverage, Explainer
client = AssayClient("traces.jsonl")
client.record_trace({"tool": "ToolA", "args": {"q": "weather"}})
coverage = Coverage("assay.yaml")
report = coverage.analyze([[{"tool": "ToolA", "args": {"q": "weather"}}]])
explainer = Explainer("assay.yaml")
details = explainer.explain([{"tool": "ToolA", "args": {"q": "weather"}}])
Repository
- Main project: https://github.com/Rul1an/assay
- Current CLI and trust-compiler docs: https://github.com/Rul1an/assay/blob/main/README.md
1 maintainer
Release files for assay-it 5.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| assay_it-5.2.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.17+ x86-64 | Details |
| assay_it-5.2.0-cp312-cp312-macosx_11_0_arm64.whl | CPython 3.12 | CPython 3.12 | macOS 11.0+ ARM64 | Details |
| assay_it-5.2.0-cp312-cp312-macosx_10_12_x86_64.whl | CPython 3.12 | CPython 3.12 | macOS 10.12+ x86-64 | Details |
Total release size: 3.6 MB
Release files / assay_it-5.2.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | assay_it-5.2.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
62381777b47ea92000ac0c0c92ab8ef3d5e950088bdd35af249d035666f93aca
|
|
BLAKE2b-256 checksum How to use checksums |
d4a30fefaffc397eaf2431cd0ec502d9b446d9548a6e599de15d4f66647e22ae
|
| 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 Aug 14, 2026.
Transparency logRelease files / assay_it-5.2.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | assay_it-5.2.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 818.2 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
394c2d67fff9d528b42db166b97a37a6e6dde606f5b0e55f247c2d55b1c6c87b
|
|
BLAKE2b-256 checksum How to use checksums |
6a484d98684ec78660704e002f820f6340dcfe86a754b853528adcd0e7ad466d
|
| 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 Aug 14, 2026.
Transparency logRelease files / assay_it-5.2.0-cp312-cp312-macosx_10_12_x86_64.whl
| Download URL | assay_it-5.2.0-cp312-cp312-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.12 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
02fefd5f8f600c9fa136f9b9a7282c30e67096c72c385da49d61b91514fc16bf
|
|
BLAKE2b-256 checksum How to use checksums |
53ef8dae6151c39ca55698bbdb8e273174ab33f9b285b0c2fb90a7689aa6d834
|
| 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 Aug 14, 2026.
Transparency log
