auth51 — Python client (embed mode)
The in-process enforcement point: it intercepts your agent's egress and gives every governed call a scoped, verifiable intent token — minted at the source, verified at the resource. This is the generalized, MCP-era successor to the original A-JWT client shim, with contextvar-based agent attribution (no call- stack introspection) per DESIGN §7b.
It's the durable, unbypassable path: it sees all egress in-process (native tool calls and MCP calls), and depends only on the HTTP library — not on any agent host's conventions.
Use
import auth51
auth51.configure(
authority_url="https://authority.auth51.com",
client_id="...", client_secret="...",
audiences=["api.internal"], # hosts to govern; everything else passes through
)
with auth51.agent("ReviewBot", checksum=agent_checksum, scope="read:repo"):
httpx.get("https://api.internal/repos/...") # ← stamped with an intent token
Config can also come from env: AUTH51_AUTHORITY_URL, AUTH51_CLIENT_ID,
AUTH51_CLIENT_SECRET, AUTH51_AUDIENCES (comma-sep), AUTH51_FAIL_OPEN.
How it works
- One import installs it (idempotent; a no-op until configured + inside an
agent()context). - A framework adapter (LangChain/CrewAI — next) or the app sets the current agent via a contextvar at the tool-call boundary; the interceptor reads it.
- On governed egress: mint a scoped intent token (Hop A) → attach as a Bearer header → forward. Minting uses stdlib urllib so it never re-enters the patched HTTP client.
- fail-open by default (mint failure → forward unstamped, don't wedge the agent); set
fail_open=Falseto fail closed.
Retained from the original A-JWT client shim
- Startup-sync (
load_agents) — preload registered agents from the authority, index by checksum, detect collisions, and fail-fast on drift when the app declares expected checksums. Boot-time validation: a mis-deployed agent is caught before it runs. - Workflow seams —
with auth51.workflow(id): ...+record_step(...)track an execution; the chain + completed-steps +prev_jtiride into each intent token'sdelegation_context(§4.3 tamper-evident trace). - contextvar attribution + smart caching — kept; call-stack introspection dropped.
Status
- ✅ contextvar agent attribution · httpx sync + async + requests interception · mint + attach · fail-open/closed
- ✅
load_agents()startup-sync (cache + collision + drift validation) · workflow seams (delegation_context +prev_jtichain) - ✅ LangChain adapter (
auth51.adapters.langchain.Auth51CallbackHandler) — sets agent context + records steps at tool boundaries - ⏭️ next: PoP signing (the
cnfbinding) · MCP_metainjection ·aiohttp· local checksum recompute (shared lib) · live e2e against the deployed authority
Release files for auth51 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| auth51-0.1.2.tar.gz | 27.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auth51-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.8 kB
Release files / auth51-0.1.2.tar.gz
| Download URL | auth51-0.1.2.tar.gz |
|---|---|
| Size | 27.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86bbdf9321f18b027abf69b8b0608e4b43c083a2816ca8a82ac8539f498eb92e
|
|
BLAKE2b-256 checksum How to use checksums |
da7146a27917fdcc3acd0cf2858d16729871aebb664b4819530ca59574cb0d37
|
| 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 8, 2026.
Transparency logRelease files / auth51-0.1.2-py3-none-any.whl
| Download URL | auth51-0.1.2-py3-none-any.whl |
|---|---|
| Size | 33.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d7c86780e97754b5b0217a10fbb37f8656a4f89a0e3f5e66435b630a7883efe
|
|
BLAKE2b-256 checksum How to use checksums |
d881d061352e06c7d3663b47bc8a092e3bb719005926d16511a59081e2a6ef9b
|
| 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 8, 2026.
Transparency log