Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

amep-protocol (Python)

Verify and produce AMEP™ (Agentic Mandate Evidence Protocol) evidence: signed records proving that what an AI agent actually did stayed within the authority a person delegated.

Specification and conformance suite: https://github.com/stafordtituss/amep

pip install amep-protocol

Verify a packet

amep-protocol verify packet.json --keys keys.json

Each invocation gets an outcome and the deciding invariant. The exit code is 0 for preserved, 1 for violated and 2 for unresolved. --json prints machine-readable results. --state and --state-out carry approval use and risk budgets across a stream of packets.

from amep_protocol import evaluate, verdict

results = evaluate(packet, keys)
print(verdict(results).outcome, verdict(results).invariant)

Produce evidence

from amep_protocol import sdk

issuer = sdk.Key.generate("issuer-1", ["issuer", "approver"])
host = sdk.Key.generate("host-1", ["host"])
observer = sdk.Key.generate("observer-1", ["observer"])

m = issuer.sign(sdk.mandate("m-1", "user:alice",
        sdk.claims(["fs.*"], ["repo:app/*"], "write_local", exp=1767229200, deny_resources=["repo:app/secrets/*"])))
a = host.sign(sdk.interpretation("a-1", "host_shell", "r9"))
i = host.sign(sdk.invocation("i-1", "m-1", "a-1", 1767225610, "fs.write", "repo:app/src/auth.ts", "write_local"))
e = observer.sign(sdk.effect("e-1", "i-1", "hook:host", "L1",
        sdk.effect_body("fs.write", "repo:app/src/auth.ts", "write_local", 1767225611)))

packet = sdk.packet(m, a, i, e)
keys = sdk.keyset(issuer, host, observer)

A key refuses to sign object kinds its roles don't allow, for example a host key signing a mandate.

Keys from the command line

amep-protocol keygen --kid issuer-1 --roles issuer,approver --out issuer-1
amep-protocol sign mandate.json --key issuer-1.key.pem --kid issuer-1 --roles issuer,approver

Conformance

amep-protocol check-suite vectors/

License: Apache 2.0. "AMEP" is a trademark of Staford Titus Selvaraj.

Metadata

Release files for amep-protocol 0.2.0a5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for amep-protocol 0.2.0a5
File Size Uploaded Provenance Actions
amep_protocol-0.2.0a5.tar.gz 21.3 kB With provenance Details for amep_protocol-0.2.0a5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for amep-protocol 0.2.0a5
File Interpreter ABI Platform Actions
amep_protocol-0.2.0a5-py3-none-any.whl Python 3 none any Details for amep_protocol-0.2.0a5-py3-none-any.whl

Total release size: 42.6 kB

Release files / amep_protocol-0.2.0a5.tar.gz

Download URL amep_protocol-0.2.0a5.tar.gz
Size 21.3 kB
Tags Source
SHA-256 checksum
How to use checksums
6ac108a1dc5caeaeaeeb5142f761db1c10e47cc3ea90cd2f85d755b41b42c75f
BLAKE2b-256 checksum
How to use checksums
5b73d378ea1876168f37b3ca89d1b28dda0412fd01a4cbe9520183ae10fd2577
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 17, 2026.

Transparency log

Release files / amep_protocol-0.2.0a5-py3-none-any.whl

Download URL amep_protocol-0.2.0a5-py3-none-any.whl
Size 21.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b3d482f3ea05d629352e37b9ed60ee6b03ec8811387bccb17002e77d53af1a6b
BLAKE2b-256 checksum
How to use checksums
229a83814d03a2723fc7fb92083f8791e2abfe6bd0559b5edf41daaf9f26bf69
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 17, 2026.

Transparency log

Security for amep-protocol 0.2.0a5

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.

Select from 2 files

Attestation for amep_protocol-0.2.0a5.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 17, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page