moss-crewai
MOSS signing integration for CrewAI. Unsigned output is broken output.
Installation
pip install moss-crewai
Quick Start: Explicit Signing (Recommended)
Sign task outputs, crew results, and agent outputs:
from crewai import Crew, Agent, Task
from moss_crewai import sign_task_output, sign_crew_result, sign_agent_output
# Run your crew
crew = Crew(agents=[...], tasks=[...])
result = crew.kickoff()
# Sign the crew result
signed = sign_crew_result(result, agent_id="research-crew")
print(f"Signed: {signed.signature[:20]}...")
# Sign individual task outputs
for task_output in result.tasks_output:
signed = sign_task_output(task_output, agent_id="research-crew", task="research")
Enterprise Mode
Set MOSS_API_KEY for automatic policy evaluation:
import os
os.environ["MOSS_API_KEY"] = "your-api-key"
from moss_crewai import sign_crew_result, enterprise_enabled
print(f"Enterprise: {enterprise_enabled()}") # True
result = sign_crew_result(
crew_output,
agent_id="finance-crew",
context={"user_id": "u123", "department": "finance"}
)
if result.blocked:
print(f"Blocked by policy: {result.policy.reason}")
Verification
from moss_crewai import verify_envelope
verify_result = verify_envelope(result.envelope)
if verify_result.valid:
print(f"Signed by: {verify_result.subject}")
All Functions
| Function | Description |
|---|---|
sign_task_output() |
Sign a task's output |
sign_task_output_async() |
Async version |
sign_agent_output() |
Sign an agent's output |
sign_agent_output_async() |
Async version |
sign_crew_result() |
Sign full crew kickoff result |
sign_crew_result_async() |
Async version |
verify_envelope() |
Verify a signed envelope |
Legacy API
The old auto-signing API is still available:
from moss_crewai import enable_moss, moss_wrap
enable_moss("moss:myteam:crewai") # Global auto-signing
agent = moss_wrap(agent, "moss:team:researcher") # Per-agent signing
Enterprise Features
| Feature | Free | Enterprise |
|---|---|---|
| Local signing | ✓ | ✓ |
| Offline verification | ✓ | ✓ |
| Policy evaluation | - | ✓ |
| Evidence retention | - | ✓ |
| Audit exports | - | ✓ |
Links
- moss-sdk - Core MOSS SDK
- mosscomputing.com - Project site
License
This package is licensed under the Business Source License 1.1.
- Free for evaluation, testing, and development
- Free for non-production use
- Production use requires a MOSS subscription
- Converts to Apache 2.0 on January 25, 2030
Metadata
Release files for moss-crewai 1.0.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 | |
|---|---|---|---|
| moss_crewai-1.0.0.tar.gz | 12.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moss_crewai-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.2 kB
Release files / moss_crewai-1.0.0.tar.gz
| Download URL | moss_crewai-1.0.0.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04b3d3ed6ab3484e936ba8ee2c76437c209ef4ff62c3f428e8c8564c53fb7047
|
|
BLAKE2b-256 checksum How to use checksums |
b7ccff6bda225cf16f0db98459550c7b562ae71bd8293a71cc3ea5a937321762
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 25, 2026.
Transparency logRelease files / moss_crewai-1.0.0-py3-none-any.whl
| Download URL | moss_crewai-1.0.0-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
75bb0053bf7f4ffbdb14b48e39e2400bb48a6ed0e513513b4538a1bac1ab139d
|
|
BLAKE2b-256 checksum How to use checksums |
c663110ca9fdb7829a0e845a605657641767f7a493fd8565cbd5ceb462d9636b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 25, 2026.
Transparency log