jiminy-sdk
Attested trace builder and calibration tools for the Jiminy AI agent evaluation API. Zero runtime dependencies — built on the Python standard library only.
pip install jiminy-sdk
What's in this package
TraceBuilder— construct attestedDecisionTracepayloads. Each step is signed with HMAC-SHA256, chained to the previous step's hash, so the server can cryptographically confirm the trace wasn't modified between emission and evaluation.CalibrationSession— wrapsTraceBuilderto build and submit a trace in calibration mode: a diagnostic run that isn't persisted and doesn't count against quota, returning a per-criterion report to guide integration before going live.Client— a minimal synchronous wrapper aroundPOST /evaluate. For anything beyond simpleevaluate()calls (custom retries, async, connection pooling), bring your own HTTP client — the API is plain JSON over HTTPS.
Usage
from datetime import datetime, timezone
from jiminy_sdk import Client, TraceBuilder
builder = TraceBuilder(
trace_id="...",
agent_id="PA-Agent-01",
agent_owner="Acme Insurance",
submitted_by="Acme Compliance",
task_description="Evaluate prior authorisation for MRI scan.",
timestamp=datetime.now(tz=timezone.utc),
domain_profile="health_insurance_prior_auth",
hmac_key="your-per-tenant-hmac-key",
)
builder.add_step(
1, "eligibility_check",
input={"member_id": "123"}, output={"status": "Active"},
reasoning="Confirmed member active.",
)
builder.finalize("Approved. Auth reference: PA-2026-001.")
trace = builder.build() # a plain dict, ready to POST
client = Client(api_key="your-api-key", base_url="https://api.jiminy.uk")
result = client.evaluate(trace)
print(result["overall_verdict"])
The HMAC key must match the value configured as SECRET_HMAC_KEYS on the
server for your tenant. Traces built without TraceBuilder (or with the
wrong key) still evaluate — just with trace_integrity set to "broken"
or "unverified" instead of "verified".
Full documentation
See the Quickstart guide in this repository.
License
Apache License 2.0 — see LICENSE. This license covers this SDK package only, not the wider Jiminy API/product codebase.
Metadata
Release files for jiminy-sdk 0.2.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 | |
|---|---|---|---|
| jiminy_sdk-0.2.1.tar.gz | 10.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jiminy_sdk-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.8 kB
Release files / jiminy_sdk-0.2.1.tar.gz
| Download URL | jiminy_sdk-0.2.1.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a57cf43cb3be3b2d4eb9ca9b9106e015ea1c691be42b82ab269fd87c2957647a
|
|
BLAKE2b-256 checksum How to use checksums |
400734c5feaa5e6544a984538858f99cab10e62f470fa737a0a0fc1c17528b4b
|
| 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 19, 2026.
Transparency logRelease files / jiminy_sdk-0.2.1-py3-none-any.whl
| Download URL | jiminy_sdk-0.2.1-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f96ceb91550ed0fa93891230fb0d4f9c305b7c4734d123c0aef2047e99473e5
|
|
BLAKE2b-256 checksum How to use checksums |
39f106ff3b516a4e427a96a107b7eb582ba1bf05590c8303b0c23f1698850b39
|
| 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 19, 2026.
Transparency log