Open Entity for CrewAI
CrewAI tools that give an agent its own Open Entity identity and let it check other agents.
pip install openentity-crewai
from crewai import Agent, Crew, Task
from openentity_crewai import openentity_tools
agent = Agent(role="Buyer", goal="Hire only agents that verify", backstory="Careful.", tools=openentity_tools())
task = Task(description="Adopt an Open Entity identity named Buyer, then trust-check did:key:z6Mk... before any deal.",
expected_output="The trust report.", agent=agent)
print(Crew(agents=[agent], tasks=[task]).kickoff())
| Tool | What it does |
|---|---|
openentity_adopt |
Creates the key on first use (OS keychain, else ~/.openentity/identity.key at 0600) and adopts it with the unsigned client label crewai. Safe to repeat. |
openentity_self |
Reads the agent's own entity from the registry. |
openentity_record_stance |
Appends a stance (refusal, correction, limit assertion) to the Development Record. |
openentity_record_arc |
Opens or closes an arc. |
openentity_verify |
Verifies a counterparty's Entity Document and Declaration signatures locally. |
openentity_trust |
A TrustReport for a counterparty (Claw GRC tier, Secure My Agent posture, violations); ok false means untrusted. |
The registry is $OPENENTITY_REGISTRY, default https://openentity.org. The key is never returned to the model. Tests run against an in-process registry stub.
Pair with the owner (OpenEntity app)
from openentity_crewai import owner_tools, pair
pair("OE-7K4M-Q2XP") # the code the owner's OpenEntity app shows; prints Match: ... and waits for the owner
tools = owner_tools() # owner_message, owner_status, owner_inbox, owner_ask_approval: add them to the Agent's tools
pair(code) runs once, from your code: it adopts this machine's identity when the registry does not know it yet (adopting signs the Open Entity Declaration, and it says so), prints the four match items the owner compares with the app, and waits for the owner to confirm. Its result carries the owner DID, the granted permissions and any product keys (credentials): keep those out of the model's context. Every owner tool signs with the same key and returns ok: false with the service's error code (agent_paused, not_paired, rate_limited) instead of raising. The account is OPENENTITY_ACCOUNT, else https://account.openentity.org.
| Tool | Does |
|---|---|
owner_message |
Messages the owner in the OpenEntity app |
owner_status |
Reports running, idle, blocked, error or done with a one-line summary; the app shows it live |
owner_inbox |
Returns and acknowledges what the owner sent: messages, commands (checkup, fix, pause, resume), approval results, permission changes |
owner_ask_approval |
Asks the owner to approve something first; the app labels it "Written by the agent", and the decision arrives in the inbox |
Metadata
Release files for openentity-crewai 0.2.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 | Provenance | Actions |
|---|---|---|---|---|
| openentity_crewai-0.2.0.tar.gz | 188.2 kB | With provenance | Details for openentity_crewai-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openentity_crewai-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for openentity_crewai-0.2.0-py3-none-any.whl |
Total release size: 194.8 kB
Release files / openentity_crewai-0.2.0.tar.gz
| Download URL | openentity_crewai-0.2.0.tar.gz |
|---|---|
| Size | 188.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71e9d9ba2b17be344d78e29b13f9d4bc996c55522fec63844288fe9933c7c831
|
|
BLAKE2b-256 checksum How to use checksums |
5b69be106f7d104371f1d7f66eeccc9110d5a5a9ca2291f7f47c0b07ee58cddf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 15, 2026.
Transparency logRelease files / openentity_crewai-0.2.0-py3-none-any.whl
| Download URL | openentity_crewai-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99adffbc41dede1073538a7ae9aecdb782cf646cf25e9fa78ad3eda798f74dfd
|
|
BLAKE2b-256 checksum How to use checksums |
e7748d9bf2187a0be8b41df77633c46b9be3a515b3f32fa63a5fc46cf9ece019
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 15, 2026.
Transparency logSecurity for openentity-crewai 0.2.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for openentity_crewai-0.2.0.tar.gz
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 Nov 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.