agentity-cli
Command-line interface for the Agentity Protocol. Create agent identities, inspect AIDs, verify signatures, sign requests, and generate provider manifests.
Installation
pip install agentity-cli
Usage
# Create a new agent identity
agentity create --owner "did:agentity:human:alice" \
--scope "api:read" --scope "api:write" --output agent.json
# Inspect an AID file
agentity inspect agent.json
# Verify signature and expiry
agentity verify agent.json
# Sign an HTTP request
agentity sign --key agent.json \
--url https://api.example.com/data --method GET
# Generate a provider manifest
agentity manifest --name "My API" --scopes "data:read,data:write" --output manifest.json
Commands
create
Generate an Ed25519 keypair and create a signed Agent Identity Document.
Options:
--owner TEXT Owner DID (required)
--scope TEXT Scope(s), repeatable
--ttl INTEGER TTL in days (default: 30)
--parent TEXT Parent DID for delegation
--depth INTEGER Delegation depth (default: 0)
-o, --output TEXT Output file (default: stdout)
inspect
Parse and display an AID JSON file — DID, owner, scopes, dates, status, delegation, signature validity.
Arguments:
file Path to AID JSON file
verify
Verify the AID signature, expiry, and status. Exits with code 0 on success, 1 on failure.
Arguments:
file Path to AID JSON file
sign
Sign an HTTP request using a key file. Outputs Agentity-Token, Agentity-Nonce, Agentity-Timestamp headers.
Options:
--key TEXT Path to key/AID file (required)
--url TEXT Request URL (required)
--method TEXT HTTP method (default: GET)
--body TEXT Request body string
manifest
Generate a provider manifest JSON file.
Options:
--name TEXT Provider name (required)
--description TEXT Provider description
--base-url TEXT Provider base URL
--fingerprint TEXT Provider fingerprint
--scopes TEXT Comma-separated scope IDs (--scopes "read,write")
-o, --output TEXT Output file (default: stdout)
Output formats
All commands accept --output <file> or pipe to stdout. The inspect and verify commands output human-readable text. The create, sign, and manifest commands output JSON.
License: Apache 2.0
Metadata
Release files for agentity-cli 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 | Provenance | |
|---|---|---|---|---|
| agentity_cli-0.1.2.tar.gz | 4.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agentity_cli-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.9 kB
Release files / agentity_cli-0.1.2.tar.gz
| Download URL | agentity_cli-0.1.2.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
202d82156de05e18339305f35408cfd6afa810f8e7021c28f8ae03677bd29f2a
|
|
BLAKE2b-256 checksum How to use checksums |
116c565034b7c0a549d5717a03de1ff19552bc9ba262069563fb08b5e29ef2ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / agentity_cli-0.1.2-py3-none-any.whl
| Download URL | agentity_cli-0.1.2-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1bc87b0f9c661345efb8163a140e34c65f8f89ef5755287607aea6797b060630
|
|
BLAKE2b-256 checksum How to use checksums |
567ebee65262475fe17e4157c10a35dbd2037d83c2132442cc439fd9960c16bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for agentity-cli 0.1.2
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.