Docs / SDKs / CLI
// COMMAND LINE
Agentics CLI
Drive routing configs, prompts, the gateway, and the verifiable ledger from your terminal. Ships as a zero-dependency Node binary and as a Python entry point.
Install
shell
npm install -g @agentics/cli # or: pip install agentics
agentics login --api-key ak_…Command reference
| Command | What it does | Hits |
|---|---|---|
| agentics gateway test | Send a 1-token ping through the gateway with an x-agentics-* trace | /v1/chat/completions |
| agentics config publish [file] | Create + publish a GatewayConfig | /api/routing/configs |
| agentics config validate [file] | Dry-run a config (no publish) | /api/routing/simulate |
| agentics prompt push <file> | Publish a prompt template | /api/prompts |
| agentics log tail [--limit N] | Tail recent gateway receipts (with their trace_id) | /api/sdk/logs |
| agentics proof verify <hash> | 4-step verify: recompute leaf, walk chain, fold Merkle, check anchor | /api/proof/verify |
| agentics proof bundle <hash> | Offline-verifiable evidence bundle | /api/proof/bundle |
| agentics models [--provider P] | List the Model Catalog catalog | /api/model-garden/catalog |
| agentics login / whoami / flags | Auth + account introspection | /api/me … |
Walkthrough
shell
# 1. confirm the gateway is reachable and your key works
agentics gateway test --url https://agentics.you/api/v1 --user alice@acme.com
# 2. validate then publish a routing config
agentics config validate gateway-config.json
agentics config publish gateway-config.json --name default
# 3. push a managed prompt template
agentics prompt push support-greeting.json
# 4. tail the ledger — your trace_id from step 1 appears on the row
agentics log tail --limit 5
# 5. verify a specific receipt end-to-end (exits non-zero if not verified)
agentics proof verify 8ae41ff9…
# 6. browse available models
agentics models --provider anthropic
Flag-gated surfaces degrade cleanly. Advanced verbs (
config, prompt, proof, models, log tail) return a friendly "feature not enabled for this tenant" when their backing module flag is off. Enable trust_gateway first so /v1/* works, then the rest as those modules ship.
Proving the receipt — the differentiator
agentics proof verify runs all four real checks: recompute the leaf, walk prev_hash to genesis, fold the Merkle proof to the batch root, and compare the public-ledger anchor memo to that root. agentics proof bundle exports a self-contained JSON you can verify offline with only a SHA-256 implementation — no Agentics service required.
It exits non-zero on a bad receipt. So
agentics proof verify drops straight into CI — gate a deploy, a release, or an evidence export on a receipt that actually folds.