asqav-pydantic 0.1.2

PydanticAI integration for asqav - cryptographic audit trails for AI agent tool calls

Governance for AI agents. Audit trails, policy enforcement, and compliance.

Website | Docs | SDK Guide | Compliance

Asqav for PydanticAI

Cryptographic audit trails for PydanticAI agent tool calls.

Uses PydanticAI's Hooks capability to sign every tool invocation with Asqav - producing verifiable records for compliance and governance.

Data handling

asqav-pydantic is a thin wrapper around the asqav Python SDK and inherits its mode behavior:

• Asqav cloud (*.asqav.com): the SDK hashes your action context locally and sends only the hash plus a small metadata bag (action_type, agent_id, session_id, model_name, tool_name). Raw prompts and tool arguments never leave your infrastructure.
• Self-hosted: the SDK sends the full context so the server can run policy checks, PII redaction, and richer audit views. Recommended when you control the deployment.

You can override per call:

import asqav

# Force hash-only against a custom URL
asqav.init(api_key="sk_...", base_url="https://api.asqav.com", mode="hash-only")

This is GDPR-aware data minimization by default for cloud deployments. See docs/fingerprint-spec.md in the SDK repo for the fingerprint spec and conformance vectors.

Install

pip install asqav-pydantic

Usage

import asqav
from pydantic_ai import Agent
from asqav_pydantic import AsqavHooks

asqav.init(api_key="sk_...")

hooks = AsqavHooks(agent_name="my-agent")
agent = Agent("openai:gpt-4o", capabilities=[hooks.capability()])

result = agent.run_sync("Search for the latest AI news")

Every tool call the agent makes will produce signed tool:start, tool:end, and tool:error events through the Asqav API. Signatures use NIST FIPS 204 ML-DSA cryptography server-side, producing tamper-evident audit trails for EU AI Act, DORA, and SOC 2 compliance.

How it works

AsqavHooks extends the Asqav adapter base class and builds a PydanticAI Hooks capability with three registered hooks:

• before_tool_execute - signs tool:start with tool name and input preview
• after_tool_execute - signs tool:end with tool name and output metadata
• on_tool_execute_error - signs tool:error with tool name and error details

All signing is fail-open. If the Asqav API is unreachable, a warning is logged but the tool call proceeds normally. Your agent pipeline never breaks because of governance.

Configuration

# Use an existing asqav agent by ID
hooks = AsqavHooks(agent_id="ag_abc123")

# Override the API key
hooks = AsqavHooks(api_key="sk_other", agent_name="audit-agent")

License

MIT