agentmark
Cryptographic provenance for AI-generated code.
agentmark proves that code traveled through a verified autonomous AI pipeline with no direct human write path — and provides a verifiable audit trail for every commit.
Installation
pip install agentmark
# With provider support
pip install agentmark[anthropic]
pip install agentmark[openai]
pip install agentmark[all]
What it does
agentmark attaches a cryptographically verifiable manifest to every AI-generated commit:
{
"version": "1.0",
"provider": "anthropic",
"model": "claude-sonnet-4-20250514",
"request_id": "req_011CZRtQztYq...",
"output_hash": "sha256:a1b2c3d4...",
"challenge_token": "agentmark-3f9a2b1c4d5e6f7a",
"challenge_echo_verified": true,
"pipeline_key": "my-pipeline-v1",
"signature": "TuBWjzVsxEwy33mS..."
}
The manifest proves:
- output_hash — committed code matches raw LLM response byte-for-byte
- challenge_token — the LLM processed this specific task
- request_id — a real API call happened at the declared provider
- signature — a registered pipeline identity signed this commit
Quick start
import agentmark
from agentmark import ChallengeRegistry, PipelineRegistry
# Issue challenge for the task
challenge = ChallengeRegistry().issue("myorg/myrepo#42")
# Call LLM with provenance capture
result = agentmark.call(
provider="anthropic",
model="claude-sonnet-4-20250514",
prompt="Implement a signing function.",
challenge_token=challenge,
)
# Sign the manifest
manifest = agentmark.sign(
result=result,
pipeline_key="my-pipeline-v1",
private_key_bytes=ed25519_private_key_bytes,
)
# Verify (runs in CI)
result = agentmark.verify(manifest, result.raw_bytes)
Security
Core dependency: cryptography >= 46.0.0 (pyca — 82M+ weekly downloads, actively maintained).
agentmark does not depend on LiteLLM or any AI gateway proxy. Provider SDKs are optional extras. We call provider APIs directly.
Links
- SPEC.md — full specification
- API docs
- agentmark.dev
License
Apache 2.0
Metadata
Release files for agentmark 0.1.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 | Provenance | |
|---|---|---|---|---|
| agentmark-0.1.0.tar.gz | 11.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agentmark-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.7 kB
Release files / agentmark-0.1.0.tar.gz
| Download URL | agentmark-0.1.0.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cae170ea7f21a626c689a6ed04d81af9cc47e6dfebf0e85b4e6a319f3238f51b
|
|
BLAKE2b-256 checksum How to use checksums |
78b39eb260748d8ae5b4259ab6999a7e0d5b74263ca3d4a789639a7e68439e72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.0
|
Release files / agentmark-0.1.0-py3-none-any.whl
| Download URL | agentmark-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1915936ec9302f53f5d7698e92ae36df425d369f4199adb1ee447ed8beb23e10
|
|
BLAKE2b-256 checksum How to use checksums |
c10a6d502dee86c19fc779f5a5b0eb5f3a3d49e3848751f86ec34d2fd5c757cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.0
|
Security for agentmark 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.