Agent Action Registry (MVP)
A minimal JSONL log standard + CLI for agent actions. No API costs.
Why this matters
Every agent needs an audit trail. This gives you a portable, append-only action log that works across tools.
Install (local dev)
python -m venv .venv
source .venv/bin/activate
pip install -e .
Quick Start
areg init
areg log --user-id demo --action-type purchase --tool browser --target amazon.co.jp \
--decision require_approval --status pending --reason "over limit" \
--tags payment,high_risk --metadata '{"amount":5000,"currency":"JPY"}'
areg view --limit 5
areg stats
areg validate
Python SDK
from action_registry import log_event
event_id = log_event(
user_id="demo",
action_type="purchase",
tool="browser",
target="amazon.co.jp",
decision="require_approval",
status="pending",
reason="over limit",
tags=["payment", "high_risk"],
metadata={"amount": 5000, "currency": "JPY"},
)
print(event_id)
Node SDK
import { logEvent } from "./sdk/node/index.js";
const id = logEvent({
userId: "demo",
actionType: "purchase",
tool: "browser",
target: "amazon.co.jp",
decision: "require_approval",
status: "pending",
reason: "over limit",
tags: ["payment", "high_risk"],
metadata: { amount: 5000, currency: "JPY" },
});
console.log(id);
Log Viewer
Open web/viewer.html and paste JSONL into the textarea.
Demo Site
Open web/index.html.
GitHub Action
Use .github/actions/areg-upload to upload .areg/actions.jsonl as an artifact.
Spec
See SPEC.md.
Files
action_registry/cli.pyCLI implementationaction_registry/format.pyspec helpersSPEC.mdlog format
Roadmap (for adoption)
- SDKs (Python/Node)
- Web viewer
- GitHub Action to attach logs to PRs
Metadata
Release files for action-registry 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 | |
|---|---|---|---|---|
| action_registry-0.1.0.tar.gz | 5.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| action_registry-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.9 kB
Release files / action_registry-0.1.0.tar.gz
| Download URL | action_registry-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e75d7de60bd59bb50e6484ebf79fe22abc2e89bb9c890ab2b85c8b53eeba292
|
|
BLAKE2b-256 checksum How to use checksums |
8fd012c11014ee2747002c9f95b3379a61a0b938cc628bb2f8dcaa805fddb24e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.16
|
Release files / action_registry-0.1.0-py3-none-any.whl
| Download URL | action_registry-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c003503d163cbba3a2d16a1c0b635a60e4e24ea3ee14898031f7fe1bd4d66adb
|
|
BLAKE2b-256 checksum How to use checksums |
a1a64ca8809a642d07abf19cca321592ec031d3f34d797b2ab9c3ba1c4ede1c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.16
|
Security for action-registry 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.