Skip to main content

piqrypt-crewai-integration

Standard: AISS v2.0 · Full stack: piqrypt.com

Verifiable AI Agent Memory_Cryptographic audit trail for CrewAI agents.

PyPI Downloads License: MIT PiQrypt

Every agent decision, task execution, and crew result — signed, hash-chained, tamper-proof.

pip install piqrypt-crewai

The problem

CrewAI agents make decisions autonomously. When something goes wrong — or needs to be proven right — your logs are editable. PiQrypt fixes that.


Quickstart

from piqrypt_crewai import AuditedAgent, AuditedCrew, stamp_task

# Drop-in replacement for Agent
researcher = AuditedAgent(
    role="Researcher",
    goal="Find accurate information on AI compliance",
    backstory="Expert in regulatory frameworks",
    identity_file="researcher.json"   # piqrypt identity
)

writer = AuditedAgent(
    role="Writer",
    goal="Write clear compliance reports",
    backstory="Technical writer",
    identity_file="writer.json"
)

# Drop-in replacement for Crew
crew = AuditedCrew(
    agents=[researcher, writer],
    tasks=[research_task, write_task],
    identity_file="crew-coordinator.json"
)

result = crew.kickoff(inputs={"topic": "EU AI Act compliance"})

# Export tamper-proof audit trail
crew.export_audit("eu-ai-act-audit.json")
# $ piqrypt verify eu-ai-act-audit.json

Decorator pattern — minimal change

from piqrypt_crewai import stamp_task

@stamp_task("research", identity_file="my-agent.json")
def research(topic: str) -> str:
    return your_research_logic(topic)

@stamp_task("write_report", identity_file="my-agent.json")
def write_report(research: str) -> str:
    return your_writing_logic(research)

What gets stamped

Event When
agent_initialized Agent creation
task_start Before task execution
task_complete After task execution (with result hash)
crew_kickoff Before crew runs
crew_complete After crew finishes (with result hash)
task_executed When using @stamp_task decorator

All events are Ed25519-signed, SHA-256 hash-chained, stored locally.
No content is stored — only SHA-256 hashes of inputs and outputs.


Verify

piqrypt verify crewai-audit.json
# ✅ Chain integrity verified — 12 events, 0 forks

Scope

Use case AISS profile
Development / PoC AISS-1 (Free, included)
Non-critical production AISS-1 (Free)
Regulated production AISS-2 (Pro — pip install piqrypt[aiss2])

Links


Metadata

Release files for piqrypt-crewai-integration 1.1.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 piqrypt-crewai-integration 1.1.0
File Size Uploaded
piqrypt_crewai_integration-1.1.0.tar.gz 2.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for piqrypt-crewai-integration 1.1.0
File Interpreter ABI Platform
piqrypt_crewai_integration-1.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 5.7 kB

Release files / piqrypt_crewai_integration-1.1.0.tar.gz

Download URL piqrypt_crewai_integration-1.1.0.tar.gz
Size 2.9 kB
Tags Source
SHA-256 checksum
How to use checksums
6cedfd28c08d746b6b85a6dbb37cef05cb5fa7c7c6aad3546bb73bae6e091de6
BLAKE2b-256 checksum
How to use checksums
6dd00b531266c5c813f67122c83eb431a4e9195af757a9c0f93a965554617c4f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Apr 19, 2026.

Transparency log

Release files / piqrypt_crewai_integration-1.1.0-py3-none-any.whl

Download URL piqrypt_crewai_integration-1.1.0-py3-none-any.whl
Size 2.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
73094736ab17617a48febf4c50d6802dffcdd7cc13e2c7c1f49b0c4bb93409e7
BLAKE2b-256 checksum
How to use checksums
83e89519a61eec0e73cde80cd1c3c79c95fef3194b7f8e8398a3e979efa14615
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Apr 19, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.1.0 This release

2 release files

1.0.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