Developers

CLI AVAILABLE

Identities, permits, intents and proofs — offline.

Commands

• `bengar id create` — an Ed25519 identity and a did:key.
• `bengar permit issue | verify | revoke` — the permit lifecycle.
• `bengar intent create` — state what an agent is trying to achieve.
• `bengar proof verify` — verify a proof of what an agent did.

A whole flow, with nothing running

bengar id create --name acme
bengar id create --name agent

bengar permit issue --issuer acme \
  --audience "$(bengar id show agent --json | jq -r .did)" \
  --can purchase --with 'resource://company/procurement/*' \
  --max-per-tx 500000:TRY --out permit.txt

bengar permit verify permit.txt
bengar permit revoke permit.txt

Exit codes

• `0` — success.
• `1` — a check ran and failed: invalid, expired, revoked, over-attenuated.
• `2` — usage or configuration error.
• `3` — internal error, which is a bug.

The separation matters in a script: `1` is the system working and saying no; `3` is the system being broken.

Limits today

• The keystore is local files. It is a developer tool, not a custody product.

API reference · Errors