Skip to main content

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 attested DecisionTrace payloads. 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 — wraps TraceBuilder to 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 around POST /evaluate. For anything beyond simple evaluate() calls (custom retries, async, connection pooling), use the generated jiminy-api-client package instead, or bring your own HTTP client.

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 and Self-Serve SDK Spec in the main 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.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jiminy-sdk 0.2.0
File Size Uploaded
jiminy_sdk-0.2.0.tar.gz 13.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for jiminy-sdk 0.2.0
File Interpreter ABI Platform
jiminy_sdk-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 29.3 kB

Release files / jiminy_sdk-0.2.0.tar.gz

Download URL jiminy_sdk-0.2.0.tar.gz
Size 13.7 kB
Tags Source
SHA-256 checksum
How to use checksums
0615c716060f5cd1edeaffaf3ba1c868d4fa83e7654d9d93bab63a4725e4a9aa
BLAKE2b-256 checksum
How to use checksums
e1919b6bc1635f39ca41a46cdddfe62a63c78288478af24e2006029dddf232d0
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 18, 2026.

Transparency log

Release files / jiminy_sdk-0.2.0-py3-none-any.whl

Download URL jiminy_sdk-0.2.0-py3-none-any.whl
Size 15.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4baf1acbf79804f08a64ebbd62d2a5e4aa8f989ff223b457c626f54d50bc7401
BLAKE2b-256 checksum
How to use checksums
ee80a9649feaf1d8557c7594affa80d2f5efde1ebfdd63d479e79042fc81540e
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 18, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.0

2 release files

0.2.1

2 release files

This release

0.2.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page