intutic-clawde
Python SDK for Intutic Agentic AI Governance proxy wrappers.
ClawdeClient.chat() sends a request through the Intutic proxy and returns the completion with verdict set to "allow". A governance refusal (policy block, reask, loop run held for review, spend cap, DLP block) raises ClawdeBlockedError with the proxy's verdict, code, rule_id (when the proxy names the rule) and reason, fires the matching kill / reask / hold event, and is never retried; transport failures and 5xx answers are retried. See Verdicts and Errors for every refusal code.
When the proxy withholds a tool call from the model's answer (a tool an SOP denies, the SSO group policy, destructive SQL, sensitive output), the answer arrives as a 200 that names the refusal in the x-intutic-refusal and x-intutic-refusal-rule headers; chat() raises ClawdeBlockedError for it too. For a stream you read yourself, pass each line to stream_refusal().
With an Intutic virtual key, in a git repository, the first chat() registers a session with the control plane carrying the repository (the origin remote as host/path, credentials removed), the branch and the HEAD commit, so the calls count in cost per branch, commit and pull request. This is on by default; pass auto_context=False to send none of it. See Git context and cost attribution.
ControlPlaneClient covers the operator APIs the CLI exposes: org and workspace setup, gateways, settings and provider credentials, the MCP registry, notification rules, SIEM destinations, usage, the AI inventory, compliance evidence, policy guardrails, held decisions and loop runs, findings, traces, trace integrity, policies and SOPs, with the TypeScript SDK's methods in snake_case. verify_evidence_archive() checks a compliance evidence archive offline and verify_integrity_root() a sealed trace root's signature; both signature checks need pip install 'intutic-clawde[compliance]'. See the SDK reference.
The intutic_clawde.gate subpackage is the pre-execution tool gate for Python agent frameworks; see the Gate SDK reference. Its GateClient fails closed by default (fail_closed=True): when the control plane's hook gate cannot be reached, or answers GOVERNANCE_UNAVAILABLE because a check it runs could not complete, the call is refused. Pass fail_closed=False to let calls through during such an outage. A request the hook gate cannot read (HTTP 400, INVALID_REQUEST) is refused whatever fail_closed says. See Fail-closed defaults.
Metadata
Release files for intutic-clawde 2.5.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 | |
|---|---|---|---|
| intutic_clawde-2.5.0.tar.gz | 117.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| intutic_clawde-2.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 261.0 kB
Release files / intutic_clawde-2.5.0.tar.gz
| Download URL | intutic_clawde-2.5.0.tar.gz |
|---|---|
| Size | 117.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f795f8d150c04116f32d741fe4c3c600fe9b99546c8aa1158b97195e29ea3160
|
|
BLAKE2b-256 checksum How to use checksums |
a528a3d13a77d9a22d96294c257eb0122197e833fbcb12126fd989879123009f
|
| 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 13, 2026.
Transparency logRelease files / intutic_clawde-2.5.0-py3-none-any.whl
| Download URL | intutic_clawde-2.5.0-py3-none-any.whl |
|---|---|
| Size | 143.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
62cc1c6545a4b8c7b5d81a69cd43a5f7291336f2bcd89daf7273b4d6eee12609
|
|
BLAKE2b-256 checksum How to use checksums |
a053f63640a5df78a7e3df46b4485eb80c799a6351188ddcdc8e0a06baadeb99
|
| 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 13, 2026.
Transparency log