watchlight-agent-sdk
Build governed AI agents. The Watchlight Agent SDK lets you put a real, fail-closed authorization decision in front of every action your agent takes — and record what happened — with the same code whether you run it on your laptop or across a production fleet.
pip install watchlight-agent-sdk
Import it as watchlight_core.
What it does
Your agent asks "may I do this?" before it acts; Watchlight answers Allow or
Deny by evaluating your policies, and the action only runs if it's permitted.
The SDK gives you:
- Authorization —
authorize_action(action, resource)gates every step, fail-closed. - Preflight — a cheap read-only "would this be allowed?" check.
- Lifecycle — a
RunHandleper agent run: submit a plan, authorize steps, complete or terminate. - Lineage — canonical, value-free execution events for audit and debugging.
- Framework plugins — ready-made integrations for LangGraph, Google ADK, AWS Bedrock, Microsoft Agent Framework, Pydantic AI, and more.
The SDK is glue: it shapes a request, hands it to a Watchlight backend, and projects the answer. Every decision is made by the backend — never in this package — which is why it's open source (Apache-2.0).
Two backends, same code
The SDK talks to a backend through one small interface, so the exact same agent and plugin code runs against either:
| Backend | Runs | |
|---|---|---|
| Developer Edition | InProcessClient |
The compiled engine, in-process — no server, no network |
| Enterprise | ApdpClient |
The governed control plane — signed lineage, drift detection, fleet-wide governance |
Moving from one to the other is a one-line change, never a rewrite.
Quickstart — a governed decision, zero infrastructure
Install the in-process engine alongside the SDK:
pip install watchlight-agent-sdk watchlight-engine
import asyncio
from watchlight_core import InProcessClient
# A Cedar policy: the research agent may read, nothing else.
POLICIES = [
{"name": "reader",
"code": 'permit(principal == Agent::"research-agent", action == Action::"read", resource);'},
]
async def main():
gov = InProcessClient(POLICIES) # real engine decisions, in-process — no network
print((await gov.authorize("research-agent", "read", "dataset"))["decision"]) # Allow
print((await gov.authorize("research-agent", "delete", "dataset"))["decision"]) # Deny
asyncio.run(main())
Allow
Deny
That Deny is the point: the action is refused before it runs — by the same
engine that powers the Watchlight platform, with no database and no network.
Govern a framework agent
Install the plugin for your framework and point it at a backend — your agent code doesn't change:
from watchlight_langgraph import WatchlightLangGraphPlugin # or -adk, -bedrock, -pydantic-ai, …
from watchlight_core import InProcessClient
plugin = WatchlightLangGraphPlugin()
plugin.apdp = InProcessClient(POLICIES) # the one line that differs from production
async with await plugin.start_run("research-agent") as handle:
if not await handle.authorize_action("read", "dataset"):
raise PermissionError("denied by policy")
# ... your agent runs, every action governed ...
Custom agents (any framework)
For an agent not built on a supported framework, the @watchlight decorator
governs any function:
from watchlight_core import InProcessClient, watchlight
gov = InProcessClient(POLICIES)
@watchlight(agent_id="custom-research", client=gov)
async def run_research(query: str) -> str:
...
Optional: OpenTelemetry export
Install the [otlp] extra to export a subset of the lineage stream to your OTel
collector (off by default):
pip install 'watchlight-agent-sdk[otlp]'
Learn more
- Documentation: https://docs.watchlight.ai/de
- Developer Edition (zero-infra quickstart) and Enterprise (the governed control plane): https://watchlight.ai
License
Apache-2.0.
Metadata
Release files for watchlight-agent-sdk 0.7.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 | |
|---|---|---|---|
| watchlight_agent_sdk-0.7.0.tar.gz | 347.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| watchlight_agent_sdk-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 563.4 kB
Release files / watchlight_agent_sdk-0.7.0.tar.gz
| Download URL | watchlight_agent_sdk-0.7.0.tar.gz |
|---|---|
| Size | 347.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b74402fca319d10c5a7b31d40fcc028f43b7129631bd4b967a211b6e178a4a45
|
|
BLAKE2b-256 checksum How to use checksums |
5f3b57fbc44707ecd2251c260bf09f4b795e704ac2e0691955157002b417d9de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / watchlight_agent_sdk-0.7.0-py3-none-any.whl
| Download URL | watchlight_agent_sdk-0.7.0-py3-none-any.whl |
|---|---|
| Size | 215.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7216cfe0a75e3cf6930dc75bb5cc62793e5c723125077769b5783057a51b587c
|
|
BLAKE2b-256 checksum How to use checksums |
043d984e09dabb18492012efdafad0df4716e6b0a8a4ad0a7a99373906423956
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency log