Skip to main content

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.

Every public module's API, with signatures and defaults: Python SDK reference.

Metadata

Release files for intutic-clawde 2.5.1

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

Source distribution (sdist)

Source distribution for intutic-clawde 2.5.1
File Size Uploaded
intutic_clawde-2.5.1.tar.gz 121.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for intutic-clawde 2.5.1
File Interpreter ABI Platform
intutic_clawde-2.5.1-py3-none-any.whl Python 3 none any Details

Total release size: 268.6 kB

Release files / intutic_clawde-2.5.1.tar.gz

Download URL intutic_clawde-2.5.1.tar.gz
Size 121.3 kB
Tags Source
SHA-256 checksum
How to use checksums
8021241269657fc042312a511bcc8e3d878102859ba67d5f4775b7436fc95950
BLAKE2b-256 checksum
How to use checksums
e3c76730e0ef6cc1b6d30015d4f0a51dc8693c99f04fcbf7c3dae6699d631e7f
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 14, 2026.

Transparency log

Release files / intutic_clawde-2.5.1-py3-none-any.whl

Download URL intutic_clawde-2.5.1-py3-none-any.whl
Size 147.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
85d0e4edf0916f4c11485b81da3ee824716bdb0352d667ba7f25daabbb5a8c21
BLAKE2b-256 checksum
How to use checksums
aef3b7a4d105886a02583877c6c8411a734c5d5b4a44f6a30a32514f2d220474
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 14, 2026.

Transparency log

Release history Release notifications | RSS feed

2.7.0

2 release files

2.6.0

2 release files

This release

2.5.1 This release

2 release files

2.5.0

2 release files

2.2.0

2 release files

2.1.0

2 release files

2.0.0

2 release files

1.10.1

2 release files

1.8.0

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