OpenBox LangChain SDK — Python
LangChain-Core adapter for OpenBox governance. Provides callback handlers that emit tool and LLM lifecycle events to OpenBox Core's policy engine, enabling real-time governance, guardrails, HITL approval flows, and base-SDK hook governance (HTTP/DB/File I/O) for LangChain agents.
Installation
pip install openbox-langchain-sdk-python
Quick Start
from langchain.agents import create_agent
from openbox_langchain import create_openbox_langchain_middleware
# 1. Create middleware
middleware = create_openbox_langchain_middleware(
api_url="https://core.openbox.ai",
api_key="obx_live_...",
agent_did="did:aip:...",
agent_private_key="...",
agent_name="MyAgent",
)
# 2. Create agent with middleware
agent = create_agent(
model="openai:gpt-4o",
tools=[...],
middleware=[middleware],
)
# 3. Invoke — governance applied automatically
result = agent.invoke({"messages": [("user", "your query")]})
How It Works
Two-layer governance architecture:
| Layer | Mechanism | Governs |
|---|---|---|
| 1 | LangChain-Core Callbacks | Tool and LLM lifecycle emission via ActivityBridge |
| 2 | Base SDK Hook Governance | HTTP requests, DB queries, file I/O at process boundary |
Core components:
ActivityBridge— Ownership channel for tool and LLM events; prevents duplicate governance evaluationOpenBoxLangChainCoreAsyncCallbackHandler/...SyncCallbackHandler— LangChain-Core callbacks emitting tool and LLM lifecycle events to OpenBox Core- AgentMiddleware (for
create_agent) — Wraps model and tool calls with additional governance context
Configuration
middleware = create_openbox_langchain_middleware(
api_url="https://core.openbox.ai", # OpenBox Core URL
api_key="obx_live_...", # API key (obx_live_* or obx_test_*)
agent_did="did:aip:...", # Required by default; can use OPENBOX_AGENT_DID
agent_private_key="...", # Required by default; can use OPENBOX_AGENT_PRIVATE_KEY
agent_name="MyAgent", # Agent name (from dashboard)
governance_timeout=30.0, # HTTP timeout in seconds
validate=True, # Validate API key on startup
session_id="session-123", # Optional session tracking
tool_type_map={ # Optional tool classification
"search_web": "http",
"query_db": "database",
},
)
Agent Identity and DID Signing
OpenBox issues each registered agent a decentralized identifier (DID) and private key. DID signing is enabled by default for newly registered agents. The OpenBox UI returns both values when the agent is created. Pass them to the middleware so governance events are signed and attributable to that agent.
You can provide them directly:
middleware = create_openbox_langchain_middleware(
api_url="https://core.openbox.ai",
api_key="obx_live_...",
agent_did="did:aip:...",
agent_private_key="...",
)
Or set them through the environment:
export OPENBOX_AGENT_DID="did:aip:..."
export OPENBOX_AGENT_PRIVATE_KEY="..."
If DID signing is explicitly disabled for the agent in OpenBox, these values can be omitted. Otherwise, provide both values together.
Supported Agent Types
create_agent(model, tools, middleware=[...])— recommended- Any LangChain agent builder that accepts
middleware
Verdict Enforcement
5-tier verdict system:
- ALLOW — Request permitted
- CONSTRAIN — Request constrained (e.g., rate limit)
- REQUIRE_APPROVAL — Human approval required (HITL polling)
- BLOCK — Request blocked with error
- HALT — Entire workflow halted (unrecoverable error)
Requirements
- Python 3.11+
- openbox-sdk-python >= 1.0.0
- langchain-core >= 1.3.3
- LangChain >= 1.0.0 (required only for
[agent]extra, which enablescreate_agentmiddleware)
API Reference
LangChain-Core callbacks:
OpenBoxLangChainCoreAsyncCallbackHandler— Async callback handler for tool/LLM lifecycleOpenBoxLangChainCoreSyncCallbackHandler— Sync callback handler for tool/LLM lifecycleActivityBridge— Ownership channel for lifecycle event deduplication
AgentMiddleware (optional):
create_openbox_langchain_middleware()— Creates configured middleware forcreate_agent
See openbox_langchain.__init__.py for full API export list.
License
MIT
Metadata
Release files for openbox-langchain-sdk-python 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 | |
|---|---|---|---|
| openbox_langchain_sdk_python-1.0.0.tar.gz | 307.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openbox_langchain_sdk_python-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 358.3 kB
Release files / openbox_langchain_sdk_python-1.0.0.tar.gz
| Download URL | openbox_langchain_sdk_python-1.0.0.tar.gz |
|---|---|
| Size | 307.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb1f6e0c91048512ffade336dbfbc7f720783af3e639a5f96242750284422e2d
|
|
BLAKE2b-256 checksum How to use checksums |
47991d6d2035187ae070e679deaa7694ebfa06a37aeb3bf0d808778c66a1585e
|
| 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 Jul 6, 2026.
Transparency logRelease files / openbox_langchain_sdk_python-1.0.0-py3-none-any.whl
| Download URL | openbox_langchain_sdk_python-1.0.0-py3-none-any.whl |
|---|---|
| Size | 51.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a84add38c86d932295c903574a7352b159a6016ad337922ec3670a7741ba7a6b
|
|
BLAKE2b-256 checksum How to use checksums |
cc566d86923459c675ec3f8c3bb966342725784d2965d34e8373b891f26b4612
|
| 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 Jul 6, 2026.
Transparency log