regent-httpsig 0.1.0__tar.gz

regent_httpsig-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,22 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: python -m pip install -e ".[aauth,fastapi]" pytest pytest-asyncio ruff mypy
+      - run: ruff check src tests
+      - run: mypy src
+      - run: pytest -q

regent_httpsig-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,33 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: python -m pip install build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # OIDC trusted publishing — no tokens anywhere
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

regent_httpsig-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.pyc
+.venv/
+dist/
+*.egg-info/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/

regent_httpsig-0.1.0/CHANGELOG.md

@@ -0,0 +1,23 @@
+# Changelog
+
+## 0.1.0
+
+Initial release, extracted from Regent Protocol's production marketplace
+(get4agent.com), where it authenticates self-onboarding AI agents.
+
+- `HttpsigVerifier` — RFC 9421 verification for both agent dialects:
+  - Web Bot Auth (draft -05): sf-dictionary `Signature-Agent` with `;key=`
+    member selection AND the legacy sf-string form OpenAI ships in production;
+    key discovery via `/.well-known/http-message-signatures-directory`.
+  - AAuth (identity-based mode, `[aauth]` extra): `aa-agent+jwt` in
+    `Signature-Key`, issuer JWKS discovery, `cnf.jwk` proof of possession.
+  - SSRF-guarded directory fetching (https-only, public-IP-only, no redirects,
+    size-capped) with bounded per-instance caching.
+- `EgressSigner` + `regent-httpsig keygen` — sign outbound agent traffic
+  (Web Bot Auth), generate keys and ready-to-publish well-known files.
+- FastAPI integration (`[fastapi]` extra): `SignatureDep` (enrichment) and
+  `RequiredSignatureDep` (authentication with a self-explaining 401).
+- Test suite pinned to the official RFC 9421 B.2.6 vector, both Web Bot Auth
+  appendix vectors (A.2.2 re-signed — the draft's printed signature does not
+  verify over its own base; reported), and full sign→verify roundtrips for
+  both dialects.

regent_httpsig-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

regent_httpsig-0.1.0/PKG-INFO

@@ -0,0 +1,176 @@
+Metadata-Version: 2.5
+Name: regent-httpsig
+Version: 0.1.0
+Summary: Verify and sign AI agent HTTP traffic in Python — RFC 9421 HTTP Message Signatures: Web Bot Auth (what OpenAI ships) and AAuth.
+Project-URL: Homepage, https://github.com/regent-protocol/regent-httpsig
+Project-URL: Repository, https://github.com/regent-protocol/regent-httpsig
+Project-URL: Issues, https://github.com/regent-protocol/regent-httpsig/issues
+Author-email: Regent Protocol <info@regentprotocol.org>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: aauth,agent-identity,ai-agents,bot-detection,ed25519,http-message-signatures,rfc9421,web-bot-auth
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Internet :: WWW/HTTP
+Classifier: Topic :: Security :: Cryptography
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: cryptography>=42
+Requires-Dist: http-message-signatures>=2.0.1
+Requires-Dist: httpx>=0.25
+Requires-Dist: typing-extensions>=4.10
+Provides-Extra: aauth
+Requires-Dist: pyjwt>=2.8.0; extra == 'aauth'
+Provides-Extra: fastapi
+Requires-Dist: fastapi>=0.100; extra == 'fastapi'
+Description-Content-Type: text/markdown
+
+# regent-httpsig
+
+**Verify and sign AI agent HTTP traffic in Python — the way OpenAI signs and Cloudflare verifies.**
+RFC 9421 · Web Bot Auth · AAuth
+
+OpenAI's agents cryptographically sign every HTTP request they make. Cloudflare, AWS WAF and
+Google verify those signatures. This library brings both sides of that handshake to Python:
+**verify** signed agents hitting your API, and **sign** your own agent's traffic so bot walls
+recognize it.
+
+```bash
+pip install regent-httpsig
+```
+
+## Verify: know which AI agent is calling — in 5 lines
+
+```python
+from fastapi import FastAPI
+from regent_httpsig import HttpsigVerifier
+from regent_httpsig.fastapi import attach, SignatureDep, VerifiedSignature
+
+app = FastAPI()
+attach(app, HttpsigVerifier())
+
+@app.post("/v1/orders")
+async def create_order(sig: VerifiedSignature | None = SignatureDep):
+    if sig:
+        print(sig.agent)    # "https://chatgpt.com"
+        print(sig.keyid)    # RFC 7638 key thumbprint
+    ...
+```
+
+No FastAPI? The core has no framework dependencies:
+
+```python
+verifier = HttpsigVerifier()
+sig = await verifier.verify(method, url, headers)   # VerifiedSignature | None
+```
+
+Verification is **enrichment by default**: no `Signature` header costs nothing, a bad
+signature yields `None`, and nothing ever raises on untrusted input. Use
+`regent_httpsig.fastapi.RequiredSignatureDep` when a signature must be present — the 401
+tells the agent exactly how to sign.
+
+## Sign: get your agent past bot walls
+
+```python
+from regent_httpsig import EgressSigner
+
+signer = EgressSigner(seed=os.environ["AGENT_KEY_SEED"],
+                      signature_agent="https://myagent.example")
+headers = signer.sign("POST", url, {"content-type": "application/json"})
+resp = httpx.post(url, json=body, headers=headers)
+```
+
+Generate a key and the ready-to-publish `/.well-known/` files in one command:
+
+```bash
+regent-httpsig keygen --agent https://myagent.example --out ./well-known/
+```
+
+Publish the directory at `https://myagent.example/.well-known/http-message-signatures-directory`
+and every Web Bot Auth verifier on the internet can now identify your agent.
+
+## What exactly is verified
+
+| Check | Status |
+|---|---|
+| RFC 9421 Appendix B.2.6 Ed25519 vector (byte-exact) | ✅ in CI |
+| Web Bot Auth draft -05 A.2.2 — sf-dictionary `Signature-Agent` covered with `;key=` | ✅ in CI¹ |
+| Web Bot Auth A.2.3 — legacy sf-string form (**what OpenAI ships in production**) | ✅ in CI |
+| Sign → verify roundtrip (fresh keys, full pipeline) | ✅ in CI |
+| AAuth identity-mode roundtrip (`aa-agent+jwt` + `cnf.jwk` proof of possession) | ✅ in CI |
+| Tampered request / expired signature / wrong directory key rejected | ✅ in CI |
+
+¹ The signature bytes printed in the draft's own A.2.2 example do **not** verify over the
+draft's own signature base (the legacy A.2.3 vector and RFC 9421 B.2.6 both do, so the defect
+is in the example, not the canonicalization). Ed25519 is deterministic, so our test pins the
+vector re-signed with the same RFC test key over the same byte-exact base — reported upstream.
+
+## Both dialects, one verifier
+
+- **Web Bot Auth** (`draft-meunier-web-bot-auth-architecture`): key discovery via
+  `{Signature-Agent}/.well-known/http-message-signatures-directory`. Both wire forms of
+  `Signature-Agent` are accepted — the current sf-dictionary and the legacy bare sf-string
+  OpenAI actually sends.
+- **AAuth** (`draft-hardt-oauth-aauth-protocol`, identity-based mode): the agent carries a
+  JWT `agent_token` in `Signature-Key`; the issuer's JWKS verifies the token, the token's
+  `cnf.jwk` verifies the request signature. Install with `pip install 'regent-httpsig[aauth]'`.
+  For a full-protocol AAuth implementation (both roles, all token types) see
+  [christian-posta/aauth-python-library](https://github.com/christian-posta/aauth-python-library) —
+  this library is the thin relying-party verifier that handles both dialects.
+
+## Security model (what a naive implementation gets wrong)
+
+The verifier fetches key directories from **attacker-nameable origins** — whoever signs a
+request chooses its `Signature-Agent`. regent-httpsig ships with the guard rails on:
+
+- **SSRF protection by default**: https-only, every resolved IP must be public (catches
+  `169.254.169.254`, loopback, private ranges, DNS names mapping to internal services),
+  redirects never followed, responses size-capped.
+- **Bounded caching**: per-instance TTL cache with eviction — a keyid-spam attack can't
+  grow memory; failures are negative-cached so a dead origin can't be used to slow you down.
+- **A valid signature proves key possession — not trustworthiness.** `VerifiedSignature.trusted`
+  reflects only your configured allow-list; deciding *whether to trust* a key is your policy
+  layer's job.
+
+Known sharp edges of the underlying ecosystem, already handled: the upstream
+`http-message-signatures` library cannot resolve RFC 9421 `;key=` dictionary members (we
+provide the component resolver), it looks up header names case-sensitively while ASGI
+frameworks lowercase them (we wrap), and it forgets to declare `typing_extensions` (we
+declare it).
+
+## Configuration
+
+```python
+from regent_httpsig import HttpsigConfig, HttpsigVerifier
+
+verifier = HttpsigVerifier(HttpsigConfig(
+    trusted_agents=frozenset({"https://chatgpt.com", "https://operator.openai.com"}),
+    max_age_hours=25,       # reject signatures created earlier than this
+    cache_ttl=600,          # key-directory cache seconds
+))
+```
+
+Pass your app's shared client to reuse its pool: `HttpsigVerifier(http_client=my_async_client)`.
+
+## Honest limitations
+
+- Web Bot Auth and AAuth are **IETF drafts** (RFC 9421 itself is a final standard). We track
+  the drafts; breaking draft changes land as minor releases while we're 0.x.
+- **Ed25519 only** for now — it's what the agent ecosystem ships.
+- Body coverage (`content-digest`) is verified when covered by the signature, but this
+  library does not require it; decide per-route whether you need it.
+
+## Related projects
+
+[cloudflare/web-bot-auth](https://github.com/cloudflare/web-bot-auth) (TypeScript/Rust) ·
+[christian-posta/aauth-python-library](https://github.com/christian-posta/aauth-python-library)
+(full AAuth protocol) · [pyauth/http-message-signatures](https://github.com/pyauth/http-message-signatures)
+(the RFC 9421 primitive this builds on)
+
+---
+
+Built and battle-tested in production by [Regent Protocol](https://regentprotocol.org) —
+runtime control and identity for AI agents. Apache-2.0.

regent_httpsig-0.1.0/README.md

@@ -0,0 +1,146 @@
+# regent-httpsig
+
+**Verify and sign AI agent HTTP traffic in Python — the way OpenAI signs and Cloudflare verifies.**
+RFC 9421 · Web Bot Auth · AAuth
+
+OpenAI's agents cryptographically sign every HTTP request they make. Cloudflare, AWS WAF and
+Google verify those signatures. This library brings both sides of that handshake to Python:
+**verify** signed agents hitting your API, and **sign** your own agent's traffic so bot walls
+recognize it.
+
+```bash
+pip install regent-httpsig
+```
+
+## Verify: know which AI agent is calling — in 5 lines
+
+```python
+from fastapi import FastAPI
+from regent_httpsig import HttpsigVerifier
+from regent_httpsig.fastapi import attach, SignatureDep, VerifiedSignature
+
+app = FastAPI()
+attach(app, HttpsigVerifier())
+
+@app.post("/v1/orders")
+async def create_order(sig: VerifiedSignature | None = SignatureDep):
+    if sig:
+        print(sig.agent)    # "https://chatgpt.com"
+        print(sig.keyid)    # RFC 7638 key thumbprint
+    ...
+```
+
+No FastAPI? The core has no framework dependencies:
+
+```python
+verifier = HttpsigVerifier()
+sig = await verifier.verify(method, url, headers)   # VerifiedSignature | None
+```
+
+Verification is **enrichment by default**: no `Signature` header costs nothing, a bad
+signature yields `None`, and nothing ever raises on untrusted input. Use
+`regent_httpsig.fastapi.RequiredSignatureDep` when a signature must be present — the 401
+tells the agent exactly how to sign.
+
+## Sign: get your agent past bot walls
+
+```python
+from regent_httpsig import EgressSigner
+
+signer = EgressSigner(seed=os.environ["AGENT_KEY_SEED"],
+                      signature_agent="https://myagent.example")
+headers = signer.sign("POST", url, {"content-type": "application/json"})
+resp = httpx.post(url, json=body, headers=headers)
+```
+
+Generate a key and the ready-to-publish `/.well-known/` files in one command:
+
+```bash
+regent-httpsig keygen --agent https://myagent.example --out ./well-known/
+```
+
+Publish the directory at `https://myagent.example/.well-known/http-message-signatures-directory`
+and every Web Bot Auth verifier on the internet can now identify your agent.
+
+## What exactly is verified
+
+| Check | Status |
+|---|---|
+| RFC 9421 Appendix B.2.6 Ed25519 vector (byte-exact) | ✅ in CI |
+| Web Bot Auth draft -05 A.2.2 — sf-dictionary `Signature-Agent` covered with `;key=` | ✅ in CI¹ |
+| Web Bot Auth A.2.3 — legacy sf-string form (**what OpenAI ships in production**) | ✅ in CI |
+| Sign → verify roundtrip (fresh keys, full pipeline) | ✅ in CI |
+| AAuth identity-mode roundtrip (`aa-agent+jwt` + `cnf.jwk` proof of possession) | ✅ in CI |
+| Tampered request / expired signature / wrong directory key rejected | ✅ in CI |
+
+¹ The signature bytes printed in the draft's own A.2.2 example do **not** verify over the
+draft's own signature base (the legacy A.2.3 vector and RFC 9421 B.2.6 both do, so the defect
+is in the example, not the canonicalization). Ed25519 is deterministic, so our test pins the
+vector re-signed with the same RFC test key over the same byte-exact base — reported upstream.
+
+## Both dialects, one verifier
+
+- **Web Bot Auth** (`draft-meunier-web-bot-auth-architecture`): key discovery via
+  `{Signature-Agent}/.well-known/http-message-signatures-directory`. Both wire forms of
+  `Signature-Agent` are accepted — the current sf-dictionary and the legacy bare sf-string
+  OpenAI actually sends.
+- **AAuth** (`draft-hardt-oauth-aauth-protocol`, identity-based mode): the agent carries a
+  JWT `agent_token` in `Signature-Key`; the issuer's JWKS verifies the token, the token's
+  `cnf.jwk` verifies the request signature. Install with `pip install 'regent-httpsig[aauth]'`.
+  For a full-protocol AAuth implementation (both roles, all token types) see
+  [christian-posta/aauth-python-library](https://github.com/christian-posta/aauth-python-library) —
+  this library is the thin relying-party verifier that handles both dialects.
+
+## Security model (what a naive implementation gets wrong)
+
+The verifier fetches key directories from **attacker-nameable origins** — whoever signs a
+request chooses its `Signature-Agent`. regent-httpsig ships with the guard rails on:
+
+- **SSRF protection by default**: https-only, every resolved IP must be public (catches
+  `169.254.169.254`, loopback, private ranges, DNS names mapping to internal services),
+  redirects never followed, responses size-capped.
+- **Bounded caching**: per-instance TTL cache with eviction — a keyid-spam attack can't
+  grow memory; failures are negative-cached so a dead origin can't be used to slow you down.
+- **A valid signature proves key possession — not trustworthiness.** `VerifiedSignature.trusted`
+  reflects only your configured allow-list; deciding *whether to trust* a key is your policy
+  layer's job.
+
+Known sharp edges of the underlying ecosystem, already handled: the upstream
+`http-message-signatures` library cannot resolve RFC 9421 `;key=` dictionary members (we
+provide the component resolver), it looks up header names case-sensitively while ASGI
+frameworks lowercase them (we wrap), and it forgets to declare `typing_extensions` (we
+declare it).
+
+## Configuration
+
+```python
+from regent_httpsig import HttpsigConfig, HttpsigVerifier
+
+verifier = HttpsigVerifier(HttpsigConfig(
+    trusted_agents=frozenset({"https://chatgpt.com", "https://operator.openai.com"}),
+    max_age_hours=25,       # reject signatures created earlier than this
+    cache_ttl=600,          # key-directory cache seconds
+))
+```
+
+Pass your app's shared client to reuse its pool: `HttpsigVerifier(http_client=my_async_client)`.
+
+## Honest limitations
+
+- Web Bot Auth and AAuth are **IETF drafts** (RFC 9421 itself is a final standard). We track
+  the drafts; breaking draft changes land as minor releases while we're 0.x.
+- **Ed25519 only** for now — it's what the agent ecosystem ships.
+- Body coverage (`content-digest`) is verified when covered by the signature, but this
+  library does not require it; decide per-route whether you need it.
+
+## Related projects
+
+[cloudflare/web-bot-auth](https://github.com/cloudflare/web-bot-auth) (TypeScript/Rust) ·
+[christian-posta/aauth-python-library](https://github.com/christian-posta/aauth-python-library)
+(full AAuth protocol) · [pyauth/http-message-signatures](https://github.com/pyauth/http-message-signatures)
+(the RFC 9421 primitive this builds on)
+
+---
+
+Built and battle-tested in production by [Regent Protocol](https://regentprotocol.org) —
+runtime control and identity for AI agents. Apache-2.0.

regent_httpsig-0.1.0/SECURITY.md

@@ -0,0 +1,22 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+Email **security@regentprotocol.org**. We aim to acknowledge within 72 hours and follow
+coordinated disclosure: please give us up to 90 days before publishing details.
+
+Please include a minimal reproduction. PGP is available on request.
+
+## Scope notes
+
+- The verifier is designed to be safe against untrusted input by construction: it never
+  raises on malformed signatures, fetches attacker-nameable URLs only through an SSRF
+  guard (https-only, public-IP-only, no redirects, size caps), and bounds its caches.
+- A **valid signature proves key possession, not trustworthiness** — reports along the
+  lines of "any agent can sign up" describe the protocol's design, not a vulnerability.
+- Vulnerabilities in the underlying `http-message-signatures` library should be reported
+  upstream; we will ship mitigations where feasible.
+
+## Supported versions
+
+The latest minor release receives security fixes.

regent_httpsig-0.1.0/examples/fastapi_verify.py

@@ -0,0 +1,29 @@
+"""Minimal FastAPI service that knows which AI agent is calling.
+
+Run:  pip install 'regent-httpsig[fastapi]' uvicorn
+      uvicorn examples.fastapi_verify:app
+"""
+
+from fastapi import FastAPI
+
+from regent_httpsig import HttpsigConfig, HttpsigVerifier
+from regent_httpsig.fastapi import RequiredSignatureDep, SignatureDep, VerifiedSignature, attach
+
+app = FastAPI()
+attach(app, HttpsigVerifier(HttpsigConfig(
+    trusted_agents=frozenset({"https://chatgpt.com", "https://operator.openai.com"}),
+)))
+
+
+@app.get("/whoami")
+async def whoami(sig: VerifiedSignature | None = SignatureDep) -> dict:
+    """Enrichment: works for everyone, tells signed agents apart."""
+    if sig is None:
+        return {"agent": None, "note": "unsigned request"}
+    return {"agent": sig.agent, "keyid": sig.keyid, "trusted": sig.trusted}
+
+
+@app.post("/agents-only")
+async def agents_only(sig: VerifiedSignature = RequiredSignatureDep) -> dict:
+    """Authentication: unsigned callers get a 401 explaining how to sign."""
+    return {"welcome": sig.agent}